#3771: Spurious "New mail" with IMAP
---------------------+---------------------
Reporter: bacam | Owner: brendan
Type: defect | Status: closed
Priority: minor | Milestone:
Component: IMAP | Version:
Resolution: fixed | Keywords:
---------------------+---------------------
Changes (by Kevin McCarthy <kevin@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"4dc1831fd6d71a69cb1178938e04bec716a3a514"
6718:4dc1831fd6d7]:
{{{
#!CommitTicketReference repository=""
revision="4dc1831fd6d71a69cb1178938e04bec716a3a514"
Don't overwrite imap_status->uidnext with a lower value. (closes #3771)
imap_read_headers() updates the idata and imap_status uidnext after
reading through all the new headers.
The idata is updated properly (only if its uidnext is below maxuid+1),
but the imap_status was always being set to maxuid.
This causes a problem with new mail checking if the most recent
messages are deleted. Then the uidnext will be greater than maxuid+1
in the mailbox, and if there are any other unread messages it will
*always* report new mail even if $mail_check_recent is set.
}}}
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3771#comment:2>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
