From: dom.lobue@gmail.com (Dominic LoBue)
Subject: [sup-talk] Need help with OfflineIMAP integration and Iconv errors
Date: Mon, 1 Jun 2009 18:54:58 -0700 [thread overview]
Message-ID: <93de24940906011854m70b8511cv139d0c7a830fc914@mail.gmail.com> (raw)
Hello,
Let me start off by saying that I am incredibly impressed with sup.
I'm really looking forward to being able to replace Outlook with Sup,
but I'm running into some problems that are preventing a complete
transition.
The first problem I'm having is when ferret is parsing through my
emails to build its indicies I get numerous "warning: error
(Iconv::IllegalSequence) decoding message body from X" errors, This
prevents a lot of my email from showing up at all. Iconv has this
problem from attempting to convert from Windows-1252, UTF-8, and
iso-8859-1. While I doubt its the cause of the problem, I am
downloading my email from the Exchange 2003 server at work via
OfflineIMAP.
The other major problem I'm running into is I can't figure out how to
get Sup and OfflineIMAP talking together correctly so that labels and
Seen flags are uploaded back to the Exchange server. I read that there
were no plans to support uploading meta-data back to IMAP servers, so
I was hoping that OfflineIMAP would sidestep the problem entirely. I
searched the archives but I didn't find any examples of working
configs. If anyone can point me to a working example I'd greatly
appreciate it.
I've tried both the latest official release and the latest revision
uploaded to github as of 20 minutes ago.
Any help would be greatly appreciated!
Dominic LoBue
next reply other threads:[~2009-06-02 1:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 1:54 Dominic LoBue [this message]
2009-06-04 3:05 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=93de24940906011854m70b8511cv139d0c7a830fc914@mail.gmail.com \
--to=dom.lobue@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox