568775 - Get mail button does not sync imap emails properly any more in multi-PC environment

Status: RESOLVED DUPLICATE of bug 693204

(MailNews Core :: Networking: IMAP, defect)

Description

[plop]

User-Agent:       Mozilla/5.0 (X11; DHP; Linux x86_64; en-US; rv:1.9.2.3) Gecko/20100505 Gentoo Firefox/3.6.3
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; fy-NL; rv:1.8.1.23) Gecko/20100130 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.5.0

When pressing the get mail button in an Imap Inbox, TB3 only downloads messages; it does not upload changes done recently.

Reproducible: Always

Steps to Reproduce:
1. configure Imap (gmail) with an Inbox folder
2. receive a message
3. read the message
4. mark the message read, and apply a tag
5. click Get mail
6. visit the webmail page (Gmail or Gmail/A), quickly (just after TB did the pretented sync): the mail is still new
7. click Get Mail in an other TB3 configured on the same Inbox: the message *may* still marked new, and has no flag (depending on mood of TB3).
Actual Results:  
New mark, and tags are sync only on shutdown.

Expected Results:  
Like in previous versions 2 and 1.

This is a regression bug compared to TB2 and TB1. I used the *quick* sync feature a lot in 2005, to exchange data between computers (using imap as data storage is slow and underefficient, but in some case, is really easier than anything else, and quick to configure). A bit less now. But this is clearly a regression.

When I mark a mail read in TB3, Gkrellm can rapidly understand I have no more unread mail, but some other Imap clients may need up to 1h before marking the mail read. Or only when I close TB3. Other way to see it:
- as soon as you receive an email, read it at once
- if you leave TB3 open, other Imap clients will warn about new mail within a few minutes.
- if you read mail and close TB3 at once, other clients that did not notify within 10s after closing TB3 will just show mail as read when they find the "(not so) new" mail on server.

Comment 1

[Wayne Mery (:wsmwk)]

Do you still see this issue when using version 5 or 6 (due out in a week)?
- If you no longer see the problem, please set status to RESOLVED, and set resolution to WORKSFORME. (or perhaps INVALID, if you determined the problem is not Thunderbird)
- If you still see the problem, please provide updated details, and any additional steps needed to reproduce the problem.

Comment 2

[plop]

I could hardly upgrade to version 5 or 6 ... Gentoo stable only offers me 3.1.10 and unstable is just ~3.3_alpha3-r2 ... are we jumping 3 majors in just a few months ?

Yes I still have the bug in 3.1.10 .

But by the way to tell things, I believe you are not trying to fix the issue; just wait for the day it will desapear byitself, or the day I stop reading emails so that you can clean up Bugzilla from bugs which don't ennoy enough people to be considered important.

But, it's not a normal bug; it's a *regression* bug. It was working fine in TB 1.5 .

I guess what you call 5 or 6, whatever it is, is again a complete rewrite, with even more bugs than 3 had ... If you are talking about a new major, then, I never want it.

Comment 3

[Wayne Mery (:wsmwk)]

(In reply to plop from comment #2)
> I could hardly upgrade to version 5 or 6 ... Gentoo stable only offers me
> 3.1.10 and unstable is just ~3.3_alpha3-r2 ... are we jumping 3 majors in
> just a few months ?
> 
> Yes I still have the bug in 3.1.10 .
> 
> But by the way to tell things, I believe you are not trying to fix the
> issue; just wait for the day it will desapear byitself, or the day I stop
> reading emails so that you can clean up Bugzilla from bugs which don't ennoy
> enough people to be considered important.

Frankly, I can't reproduce it.  And no one else has confirmed it. If you rather I leave so you can argue with someone else who might try to help you I can do that too.

 
> But, it's not a normal bug; it's a *regression* bug. It was working fine in
> TB 1.5 .
> 
> I guess what you call 5 or 6, whatever it is, is again a complete rewrite,
No, it is not. You're pulling assumptions out of thin air

That said, this may be a duplicate.

Comment 4

[Richard van den Berg]

I have a similar (if not the same) issue with Thunderbird 9.0.1. I have imap set up on several OS X systems and an iPhone and iPad. After I read and delete some mail on the iPhone or iPad the mails still show up in my Inbox in Thunderbird. After restarting Thunderbird those mails are gone.

Comment 5

[Ludovic Hirlimann [:Usul]]

can we get a imap log ? see https://wiki.mozilla.org/MailNews:Logging

Comment 6

[WADA:World Anti-bad-Duping Agency]

(In reply to plop from comment #0)
> 4. mark the message read, and apply a tag
> 5. click Get mail
> 6. visit the webmail page (Gmail or Gmail/A), quickly (just after TB did the
> pretented sync): the mail is still new

At Gmail(Web interface), which do you call by your "the mail"?
(a) A Conversation of multiple mails in Gmail(a thread of mails in Gmail) is still new.
(b) A mail in a conversation of multiple mails in Gmail is still new.
(c) A Conversation of single mail only (a thread of a mail in Gmail) is still new.
(d) A single/independent mail is still new. (Gmail's Mail Setting/General/Conversation View:, Off)
See bug 478996.

> 7. click Get Mail in an other TB3 configured on the same Inbox: the message
> *may* still marked new, and has no flag (depending on mood of TB3).

Other Tb instance which is already running? Or newly started Tb?
If former, are you talking about phenomenon of bug 693204 and/or bug 512745?

Comment 7

[WADA:World Anti-bad-Duping Agency]

> 6. visit the webmail page (Gmail or Gmail/A), (snip) the mail is still new

Because Gmail IMAP, this part is user's misunderstanding/confusion. So INVALID.

> 7. click Get Mail in an other TB3 configured on the same Inbox: the message
> *may* still marked new, and has no flag (depending on mood of TB3).

This part is same phenomenon as bug 693204. Closing this bug as dup of bug 693204 which doesn't involve user's misunderstanding/confusion.

Bug opener, please reopen this bug if duping is wrong.

Comment 8

[plop]

Tagging the old report as dup of the new one is the best way to make devs think the bug is recent (and irrelevant).

Yes, an other TB3 profile on the same host.

But bug can also be reproduced with any other Imap client, like my mobile phone: just after reading an email on Gmail, I can sync my phone, and it will show mail as read; but clicking GetMail on TB3 will now ... untill TB restart. This is making comment 6 irrelevant.