#3287: imap recent not honoured ---------------------+------------------------------------------------------ Reporter: prlw1 | Owner: brendan Type: defect | Status: closed Priority: major | Milestone: 1.6 Component: IMAP | Version: 1.5.20 Resolution: fixed | Keywords: recent status noop exists ---------------------+------------------------------------------------------ Changes (by me):
* status: new => closed * resolution: => fixed Old description: > eg: > > {{{ > 4> a0006 NOOP^M > 4< * 223258 EXISTS > Handling EXISTS > cmd_handle_untagged: New mail in INBOX - 223258 messages total. > 4< * 205 RECENT > 4< a0006 OK Completed > IMAP queue drained > }}} > > but mutt says New:4 > which are the 4 messages which arrived while mutt was running i.e., not > including the 205 which arrived since mutt had last viewed the inbox. > > I am not using the header cache, and this is against a cyrus imap server. > Using today's (1st July) mercurial source. New description: eg: {{{ 4> a0006 NOOP^M 4< * 223258 EXISTS Handling EXISTS cmd_handle_untagged: New mail in INBOX - 223258 messages total. 4< * 205 RECENT 4< a0006 OK Completed IMAP queue drained }}} but mutt says New:4 which are the 4 messages which arrived while mutt was running i.e., not including the 205 which arrived since mutt had last viewed the inbox. I am not using the header cache, and this is against a cyrus imap server. Using today's (1st July) mercurial source. -- Comment: I believe this bug has been fixed by [a51df78218e8] in which the $mail_check_recent option controls whether or not we use UNSEEN or RECENT to report the number of new messages in the mailbox. -- Ticket URL: <http://dev.mutt.org/trac/ticket/3287#comment:3> Mutt <http://www.mutt.org/> The Mutt mail user agent