Re: offlineimap, mutt and exchange.

[Jon Riddle <list@xxxxxxxxxxxxxxxxx>]

I was responding more to Steve Traylen's original message, though now
that I have reread the post, I think his is different problem than
either of ours.  I was wondering if your Mutt access was through IMAP to
try to isolate the cause.

As John Goerzen pointed out, as of 3.99.2, offlineimap moves messages
from /new to /cur, which is what is changing my messages in Mutt from N
to O (I'm using 4.0.11).  You are correct in that this is a different
problem than yours, and apparently from Steve's as well.  I'll start
another thread with my question.

Jon


> Content-Length: 1719
> 
> Jon,
> 
> Jon Riddle <list@xxxxxxxxxxxxxxxxx> wrote:
> > If it's an Exchange thing, then why am I getting the same thing?  I'm
> > syncing between two BincIMAP servers. 
> 
> I believe that you and I are /not/ seeing the same problem.  As I said
> in an earlier email, I do not have any problems with messages moved
> between directories; those movements all seem correct to me.  What I
> am seeing is strange flags appended to the info portions of Maildir
> messages in the cur directory.  See my original post on this: 
> http://lists.complete.org/offlineimap@xxxxxxxxxxxx/2006/03/msg00000.html.gz
> 
> I just re-read your original mail and it seems like your problem is
> that messages go from N to O, whereas mine is that messages go from
> nothing to O.
>  
> > Andrew, are you using Mutt through your IMAP server, or directly
> > accessing the Maidir?
> 
> Mutt accesses the Maildir directly and does not use IMAP at all.
> 
> > It seems to me that Mutt and offlineimap are doing what they are
> > supposed to do, in that once a message has been seen by a mail reading
> > program, that message is moved to the /cur folder with a ,2: appended to
> > the filename.  I think the option should exist in offlineimap not to
> > move new messages to /cur.  In my situation (and I suspect many
> > others'), I don't want the offlineimap sync to be considered "seen by a
> > mail client" (which is the trigger that moves a message from /new to
> > /cur).  As a workaround, this guy:
> > http://www.rachinsky.de/nicolas/mutt.html
> > has a script (bottom of the page) that marks messages as new again.
> > Obviously not a long-term solution, but maybe a quick fix?
> 
> Are you saying that offlineimap always moves messages from new to cur,
> even without having opened the message in Mutt?
>