On Monday, 04 September 2006 at 16:12, Ben Korvemaker wrote: > Since the upgrade to mutt-1.5.13 (running mutt-1.5.11 before), I'm not > getting new mail reported in mailboxes on courier imap servers. Oddly, > the one UW imap server I do use does report new mail. Attached is a > trace (-d 5) of connections to just one courier imap server, where new > mail does arrive to the spool, but it never reported through a new mail > notification, nor when I hit 'c' followed by <space>, yet is obviously > there when I finally change back to the spool. Also attached is the > output of 'mutt -D' in case there's a configuration change I've missed > that I should be using. Issuing an imap-fetch-mail doesn't seem to help. > > Running on freebsd-6.1 if it matters. Courier IMAP is 4.1.1,1. Running > with the latest mutt from CVS seems to show the same behaviour. I also > tried with dovecot, and get the same behaviour (no new mail reported). > Thunderbird does report new mail. > > Please let me know if any other information would be useful. There are no STATUS lines in this debug log except for the postponed folder. Nor do I see imap_check_subscribed set anywhere, or any mailboxes commands. Thus you won't be told about new mail in any folder but the one that is currently opened. From the log, mutt is offering the server a chance to announce new mail in INBOX (with the NOOP command), but the server never does. I don't see a mutt bug here. You could try activating $imap_idle to see if courier works better with it than NOOP. You could also lower $timeout to get more frequent checks of the current mailbox. I can't see anything here that would suggest that mutt 1.5.11 would do anything differently - perhaps you upgraded your server at the same time you upgraded mutt?
Attachment:
pgpWzSZ2r9vwf.pgp
Description: PGP signature