Closed
Bug 782356
Opened 12 years ago
Closed 9 years ago
changing pop mail server name/address causes all mail to be redownloaded
Categories
(MailNews Core :: Networking: POP, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 843506
People
(Reporter: jberkus, Unassigned)
Details
Today I had reason to change the server address of an old mailserver on which I have 40K messages stored, from mail.whatever.tld to imap.whatever.tld. This caused Thunderbird to redownload 100% of the mail headers in this account, back to the Beginning of Time. This is clearly pathological behavior.
Steps to reproduce:
1. Have an IMAP mailserver with many stored messages.
2. Change the DNS name of the mailserver.
3. Change the mailserver name in Thunderbird.
4. Thunderbird will redownload 100% of the message headers.
What should happen instead:
4. Thunderbird should redownload only new message headers, unless prompted by the user.
I have seen this too. I think it is caused because the file popstate.dat (holding list of downloaded messages) contains the name of the old server and when new mail checking is done, the server name does not match so the file is discarded.
Component: General → Networking: POP
Product: Thunderbird → MailNews Core
Comment 2•12 years ago
|
||
(In reply to :aceman from comment #1)
> I think it is caused because the file popstate.dat
> (holding list of downloaded messages) contains the name of the old server
> and when new mail checking is done, the server name does not match so the
> file is discarded.
Joe, NoOp, thoughts?
Summary: Any change to mailserver parameters causes all mail to be redownloaded → Any change to pop mailserver parameters causes all mail to be redownloaded
Comment 3•9 years ago
|
||
this seems to me the same as bug 843506.
(took some serious digging to find it)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Summary: Any change to pop mailserver parameters causes all mail to be redownloaded → changing pop mail server name/address causes all mail to be redownloaded
You need to log in
before you can comment on or make changes to this bug.
Description
•