IMAP inbox "read" messages reported as "new", non-stop alert/notify



Mail Window Front End
13 years ago
13 years ago


(Reporter: Bob Wheatley, Assigned: Scott MacGregor)


Firefox Tracking Flags

(Not tracked)



(1 attachment)



13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

IMAP "Read" messages in inbox are reported as "new" non-stop.  You get a new
message, read it, and leave it in the inbox.  The next time TB checks mail
server for new mail it will alert / notify and report the "read" message as "new".

Reproducible: Always

Steps to Reproduce:
1.Receive and read email (leave in inbox)
2.Minimize client
3.Upon next "check for new mail" the read message will be alert / notified as new.

Actual Results:  
If you leave ANY mail in the inbox, new mail alerts happen everytime client
checks server for new mail.

Expected Results:  
"read" mail should not be reported as "new", only "new" mail should be reported
as "new".  TB bug Mozilla Mail doesn't do this.

Comment 1

13 years ago
this is not the case normally, so it's likely something in your setup. Here's
how to get an imap protocol log. Replace "protocol" in the instructions with
IMAP. Once you have a log, you can e-mail it to me, or attach it here.
Created attachment 183517 [details]
imap protocol log

1. When i read the mails in the imap server, it always start with a "you have 1
new message", even if there is none in the server.

2. When there is really new mail, it downloads it ok, but what seams to me is
that the /read flags aren't beign sent correctly to imap, not are they beign
cached if working offline. From the reading of other bugs (232967, 270598,
218123, and others).

3. The download of the messages aren't downloading the bodies of the messages
unless i've checked the "offline" flag in the folders.

4. There is no context option to mark the message for "downloading" nor there
is a menu option or toolbar button for that effect. Which means that if the
"offline" option isn't selected, it is impossible to read the imap mail.

5. When reading the mail, after a timer, it marks the mail read. The message is
still selected, but, when the "refresh" is made, the message turns to unread
status, keeps the selected status (but without focus), but the timer to mark it
read again isn't fired. Giving the status to that message, doesn't start the
timer. One has to change the current message to another, to be able to use the
timer to mark it read.

If needed i can test this and other bugs against the latest nightly build,
because i really need the imap functionality working well, because i don't want
to use the alternative...

btw. I used thunderbird version 1.0+ (20050513).
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.