245769 - When mail.imap.use_status_for_biff is set, Mozilla does not notice any new mail

Status: RESOLVED FIXED

(MailNews Core :: Networking: IMAP, defect)

Description

[Aleksey Nogin]

When I set mail.imap.use_status_for_biff to true, Mozilla almost stops noticing
new mail. In notices new mail in a very small subset of folders (different ones
in different cases), but new mail in most folders goes unnoticed until I
explicitly go to that folder. On startup, however, Mozilla does notice all new
mail properly.  And when mail.imap.use_status_for_biff is unset, everything
works fine.

This is a two-months-old regression (this started happening right after bug
239196 was fixed - see also bug 239196 comment #23).

Comment 1

[Aleksey Nogin]

*** Bug 245767 has been marked as a duplicate of this bug. ***

Comment 2

[David :Bienvenu]

have you tried a new 1.8 trunk build? (I'm assuming you're using a 1.8 trunk
build...)

*** This bug has been marked as a duplicate of 245044 ***

Comment 3

[Aleksey Nogin]

I am using BuildID 2004060417 (e.g. the one I've built right after bug 245044
was fixed). I do not see any "reverting" of counters, or anything else being
wrong - I just see that some folders just act as if there were no biff at all -
e.g. the counters that are shown are the ones that used to be correct, they are
just never updated (and the folder is not marked as having new messages) when
new messages arrive.

Comment 4

[David :Bienvenu]

ok, sorry, could you attach or e-mail me a protocol log annotated with which
folders are working and which aren't? thx.

http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap

Comment 5

[David :Bienvenu]

Attachment: possible fix

Aleksey, do you want to try this patch and see if it fixes the problem for you?
The idea is that if we're in the selected state in some of your folders, STATUS
may not work on them, so we need to do a NOOP and then fetch new headers, if
any...

Comment 6

[David :Bienvenu]

Comment on attachment 150230 [details] [diff] [review]
possible fix

Iain has been running with this patch and it seems to be working fine...

Comment 7

[Aleksey Nogin]

Comment on attachment 150230 [details] [diff] [review]
possible fix

I am trying out BuildID 2004060722 with this patch. So far, things are mostly
working.

Here is one issue I see:
- If an _existing_ message in a folder that used to be marked read is marked
unread (by a different IMAP client), Mozilla does not notice it (without
mail.imap.use_status_for_biff it does). And afterwars even explicitly selecting
that folder leaves Mozilla confused (never happened with
mail.imap.use_status_for_biff unset) - it would still show the message as read!

I will keep testing and will let you know if I see more issues.

Comment 8

[David :Bienvenu]

fix checked in. Aleksey, an imap protocol log for the problem you describe would
be extremely helpful - how and when the server notifies changes a connection of
state changes made from another connection is up to the server, so I'd have to
see how your server handles this to begin to know what's going wrong.

Comment 9

[Scott MacGregor]

the 2004-06-07 patch has been fixed on the aviary 1.0 branch

Comment 10

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

bienvenu, if this is fixed for TB/SM, perhaps it can be resolved... or is this now SM-only?

Comment 11

[David :Bienvenu]

I think this should be marked fixed and new bugs open for any remaining issues. The main bug is fixed.