Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Jake Colman <colman@ppllc.com>
Cc: "ding\@gnus.org" <ding@gnus.org>
Subject: Re: nnimap and Exchange 2007
Date: Fri, 28 Mar 2008 10:32:32 -0500	[thread overview]
Message-ID: <86iqz6vp7z.fsf@lifelogs.com> (raw)
In-Reply-To: <48DD2FD744F23640B63C60A81E7679E70DA75BEB@exchange-d01.ppllc.com> (Jake Colman's message of "Fri, 28 Mar 2008 11:18:28 -0400")

On Fri, 28 Mar 2008 11:18:28 -0400 Jake Colman <colman@ppllc.com> wrote: 

JC> I have not updated my gnus from a nightly snapshot since Feb 28 yet
JC> I seem to already have the fix that you say you just committed.  Am
JC> I missing something here?  Now I'm confused!

"cvs status nnimap.el" should say 7.43.  If it does, you're fine.

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?

It will take the new mail from your IMAP mail source and put it into
your "home" Maildir.  The mail will remain on IMAP, so you'll have two
copies of it forever.  You can, instead, delete the originals but I
prefer not to.  Disk space is cheap, resending e-mails is annoying.

Please don't top-quote.

Ted



  reply	other threads:[~2008-03-28 15:32 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 [this message]
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
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=86iqz6vp7z.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=colman@ppllc.com \
    --cc=ding@gnus.org \
    /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).