From: Jake Colman <colman@ppllc.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: "ding\@gnus.org" <ding@gnus.org>
Subject: Re: nnimap and Exchange 2007
Date: Fri, 28 Mar 2008 13:29:10 -0400 [thread overview]
Message-ID: <76abkilpuh.fsf@dev-d01.ppllc.com> (raw)
In-Reply-To: <86iqz6vp7z.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 28 Mar 2008 11:32:32 -0400")
>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
JC> How do I use this suggested setup of your's? What will it do for me
JC> exactly? I currently use nnimap-split rules to split my email into
JC> folders on the IMAP server. If I do what you suggested as a
JC> workaround, what will change and how do I work with it?
TZ> It will take the new mail from your IMAP mail source and put it into
TZ> your "home" Maildir. The mail will remain on IMAP, so you'll have two
TZ> copies of it forever. You can, instead, delete the originals but I
TZ> prefer not to. Disk space is cheap, resending e-mails is annoying.
Ted,
Using your alternate setup, would the IMAP mail be split appropriately
into my "home" Maildir? I guess I'm still confused as to how I would
convert from broken IMAP to a more uable alternative.
Even with the patch, IMAP access is very slow and many actions result in
a warning such as:
(6) (error/warning) Error in process filter: (error Internal error, tag
201 status BAD code nil text The specified message set is invalid.)
...Jake
--
Jake Colman
Director of Software Development
Principia Partners LLC
101 West Elm Street
Suite 620
Conshohocken, PA 19428
+1 (610) 755-9786
www.principiapartners.com
next prev parent reply other threads:[~2008-03-28 17:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 12:27 Jake Colman
2008-03-28 14:48 ` Ted Zlatanov
2008-03-28 15:18 ` Jake Colman
2008-03-28 15:32 ` Ted Zlatanov
2008-03-28 15:40 ` Jake Colman
2008-03-28 15:56 ` Ted Zlatanov
2008-03-28 16:56 ` Jake Colman
2008-04-01 14:13 ` Simon Josefsson
2008-03-28 17:29 ` Jake Colman [this message]
2008-03-28 17:47 ` Ted Zlatanov
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=76abkilpuh.fsf@dev-d01.ppllc.com \
--to=colman@ppllc.com \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.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;
as well as URLs for NNTP newsgroup(s).