Confirmed that this bug is fixed in dovecot if using the CVS version 
(not the 0.99..x versions).

The version (as the bug title says) is 0.99.10.4.

Since I reported this I've upgraded to 0.99.10.6 with little effect.



I'm connecting to the server through SSL.

Mailboxes are in mbox format.



Can't find your post on the IMP mailing list, I'm afraid.

I can confirm that funny things can happen with dovecot and CVS HEAD 
IMP concerning the new/recent mail flags.  This is, AFAIK, a bug in 
dovecot which is tickled by IMP, and not a bug in IMP, though I've not 
debugged the situation completely (and hence could be wrong about it). 
  The ticket is fairly useless though without info like dovecot 
version and mail store format (mbox or maildir).

See my posting to the IMP mailing list about this for slightly more info.

Change state to stalled, as no developer currently runs Dovecot and 
all other IMAP servers are working fine. You might also want to try to 
ask on the IMP mailing list to see if there are any Dovecot users.

This is NOT a bogus bug!  Can someone please take the effort to read 
this, rather than sweep it under the rug?

Nope - I'm afraid there's nothing clever going on.  The IMAP server is 
local, so I just communicate direct - no proxies involved.



In other news, I notice this ticket still has states of "bogus" and 
"resolved", despite the fact it's a valid ticket, and so does not show 
up on the standard searches.  Could someone please set the status 
flags so that this is listed as a valid ticket please?

Are you using up-imapproxy?  It appears as if up-imapproxy and dovecot 
don't get along well due to locking issues in dovecot, so once I 
disabled imapproxy I got dovecot and IMP HEAD to work together just 
fine.

Hello Chuck,



Thanks for your prompt reply.



It is interesting that this is something that someone using POP would 
see, but as you can see the configuration is only using IMAP (that's 
the only server defined in the file).



I don't understand why you say this must be a configuration issue - 
this is exactly the same server, with the same parameters, that the 
stable version of IMP (3.2.3) uses with no problems.  Is there 
something in that configuration I sent earlier that you see as 
incorrect?  I could well be missing something fundamental.



Thank you,

Nick

That may be, but the behavior you describe is exactly what someone 
using POP would see. Anyways, this is a configuration issue on your 
install, not a code issue.

Actually, I /am/ using IMAP.



$servers['imap'] = array(

     'name' => 'tastycake.net IMAPS Server',

     'server' => 'kalimdor.tastycake.net',

     'protocol' => 'imap/ssl/novalidate-cert',

     'port' => 993,

     'folders' => '',

     'namespace' => '',

     'maildomain' => 'tastycake.net',

     'smtphost' => 'localhost',

     'realm' => 'tastycake.net',

     'preferred' => ''

);



Looks like IMAP to me.

Use IMAP, not POP.

When browsing a mailbox using the CVS/Alpha drops, all messages are 
shown as unread, whether read or not.  Other flags (replied, important 
etc) are shown as usual, but in addition to the "unseen" style rather 
than "seen".



Not sure if this is a problem with dovecot or IMP, but current stable 
release of IMP (3.2.3) interprets the seen/unseen status correctly, so 
I would be inclined to believe it's a bug introduced with the new code.