Brendan Cully wrote: > > > > I've realised I didn't have to put you through that, because the > > answer was in the first transcript: Communigate doesn't appear to > > support custom flags (there's no '*' in PERMANENTFLAGS), so mutt isn't > > trying to set the Old flag. > > > > This changed for you because mutt stopped relying on the Recent flag > > to distinguish between new and old messages (the flag is very > > unreliable in many contexts). I think we could fix this case in mutt > > if you have hcache enabled by storing the Old flag in the header > > cache. > > https://dev.mutt.org/trac/ticket/3554
Brendan, Thank you for the analysis and for opening the bug report. If "storing the Old flag in the header cache" means that mutt will store some flags on the localhost, I am not interested in this solution. I access my IMAP mailboxes both from home and from work, there would be a mess. However, the workaround which was available in mutt-1.4.2.3_4 (be it the Recent flag or something else) worked perfectly for me. I wish I could have it back. Thanks again. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru
