198753 - Mozilla ignores EXPUNGEs caused by other clients

Status: RESOLVED EXPIRED

(MailNews Core :: Networking: IMAP, defect)

Description

[Timo Sirainen]

User-Agent:       Mozilla/5.0 Galeon/1.2.8 (X11; Linux i686; U;) Gecko/20030311 Debian/1.2.8-3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030319 Debian/1.3-3

If another IMAP client deletes messages and server notifies mozilla about it
with EXPUNGE messages, mozilla just ignores it and keeps asking them from server
when they're tried to be opened. No error message is shown that the message is
already deleted.

Also I somehow managed to get it begin trying to download one message
infinitely. Even after restart it wouldn't believe the message was already deleted:

4 UID fetch 607 (UID RFC822.SIZE BODY[]<0.10240>)
4 OK Fetch completed.
5 UID fetch 607 (UID RFC822.SIZE BODY[]<10240.10240>)
5 OK Fetch completed.
6 UID fetch 607 (UID RFC822.SIZE BODY[]<20480.4938>)
6 OK Fetch completed.
7 UID fetch 607 (UID RFC822.SIZE BODY[])
7 OK Fetch completed.
8 UID fetch 607 (UID RFC822.SIZE BODY[])
8 OK Fetch completed.
9 UID fetch 607 (UID RFC822.SIZE BODY[])
9 OK Fetch completed.
..etc..


Reproducible: Always

Steps to Reproduce:

Comment 1

[Timo Sirainen]

The infinite loop happens for all mails larger than 10kB. For smaller mozilla
tries to fetch them only once (which is still one too much).

Comment 2

[David :Bienvenu]

we don't ignore expunge responses, but perhaps we're not handling them
correctly, or communicating them from the imap backend to the db.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.