Closed
Bug 624195
Opened 14 years ago
Closed 14 years ago
messages remaining on hotmail.com server instead of automatically being erased
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: dragon_celeste1, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 (.NET CLR 3.5.30729)
Build Identifier: professionnal (5.1.2600)
when TB downloads messages from hotmail.com server (using webmail extension),
all the mails still remain on the original MS server just like if the account was
set up with the "let the messages on server" and "until I erase them" options,
despite those aren't set up and that's only the "download automatically new messages" which is activated
Reproducible: Always
Steps to Reproduce:
1.open TB and go to the hotmail.com account setup (upon the server parameters) ;
2.set the "check mail on startup", "check new messages every...", "download automatically the new messages" and "empty bin on quit" up ;
3.let "download headers only" and "let messages on the server" unchecked ;
4.verify messages on the hotmail.com account with the according TB button.
Actual Results:
every time the hotmail.com account checks for new mails with its original server,
the same duplicated messages appear again & again in TB...
(because they are never erased by TB and need to be erased directly on the
original MS server)
Expected Results:
the last downloaded messages just stay as they are left in TB by the user and
are not downloaded again as duplicated by TB (because TB just erased them on the
original MS server last time). Only the new upcoming messages (not already
downloaded by TB) will be downloaded next time !
It seems to appear since the 3.1.6 version, but I am not sure (may be 3.1.7).
Comment 1•14 years ago
|
||
Since you are using the webmail extension (and given my knowledge of its implementation), this is a problem with that extension and not with Thunderbird itself.
Please raise the bug with the author of the extension.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•