Closed
Bug 573985
Opened 14 years ago
Closed 14 years ago
New mail remains as new for multiple folders
Categories
(Thunderbird :: General, enhancement)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 693204
People
(Reporter: matthew.krummert, Unassigned)
References
(Blocks 1 open bug)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.70 Safari/533.4 Build Identifier: 3.0.5 When a new piece of mail is recieved, it is displayed as new for each folder (usually inbox and all mail), however if you look at the piece of mail from the inbox, it should also display as being read from the all mail, mail box. Reproducible: Always Steps to Reproduce: 1.Recieve mail 2.Open the mail from inbox / spam and notice that the mail is still displayed as not read from all mail 3. Actual Results: You have to open same email from multiple locations Expected Results: You should only have to open an email from one location Second email of similar issue to follow
Comment 1•14 years ago
|
||
Gmail IMAP? If a mail in Inbox is marked Read(\Seen flag is stired), it's automatically propagated to copy of the mail in [Gmail]/All Mail sooner or later at IMAP server. However, the \Seen flag for mail in [Gmail]/All Mail is not automatically passed to IMAP mail client(==Thunderbird). Flag status change of a mail at server is checked upon IMAP folder open byt Thunderbird. If you don't want to see Unread status of mails in [Gmail]/All Mail, stop automatic mail check of [Gmail]/All Mail. There is no need to check [Gmail]/All Mail contents always, because [Gmail]/All Mail is move target folder of "Archive" at Gmail Web interface.
Reporter | ||
Comment 2•14 years ago
|
||
thank you for the quitck reply and I apologize for I do not think that I explained my point clear enough. The issue is that for one piece of mail the message is being displayed in the "All Mail" folder as well as the "Inbox" which means that the user has to click twice to label an item as being "Read". If I understand things correctly, you are putting a timer in Thunderbird to check to see if there is mail ever X minutes, thus it is possible but not likely that you will have part of a piece of mail come in on two periods. Since we are now going to recieve both messages at once the majority of times, what if you did a test of all new mail to see if there is one in the all mail folder that is also in another folder such as the inbox before displaying it to the user? Also, this issue shows up in two locations in the application where the first is in the popup for two notifications of the same piece of mail, and in the second is where you have to touch two pieces of mail in order to show that the email has been read.
Comment 3•14 years ago
|
||
Please read at least read and understand RFC of IMAP before asking questions. Here is B.M.O. Not supprot forum.
> http://tools.ietf.org/html/rfc3501
Mail client(==Tb) has to act based on IMAP RFC. Even if a mail cilent can do additional actions for user's convenience, such actions must base on IMAP RFC.
Updated•14 years ago
|
Blocks: tb-gmailWIP
Comment 4•14 years ago
|
||
Matthew Krummert, please read and understand all bugs listed in Dependency tree for meta bug 402793 with "Show Resolved" before asking questions and suggesting some changes of Tb.
Comment 5•14 years ago
|
||
IDLE in Gmail IMAP(and some other IMAP servers) does not send unsolicited responses for flag changes to IMAP client, but Tb expects unsolicited responses for flag changes from IMAP server. Closing as dup of bug 512745.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Comment 6•11 years ago
|
||
"IDLE does not send unsolicited responses for flag changes" is not Gmail IMAP only issue. Issue of "Tb is not torelant with 'IDLE does not send unsolicited responses for flag changes'" is not Gmail IMAP only issue. Because bug 693204 was processed after analysis of many bugs, that bug is crispy than other bugs. So, duping this bug to bug 693204. If duping is wrong, re-open this bug, please.
You need to log in
before you can comment on or make changes to this bug.
Description
•