Closed
Bug 438680
Opened 16 years ago
Closed 14 years ago
Get Mail fails after mail server is restarted
Categories
(MailNews Core :: Networking: POP, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: marc, Unassigned)
Details
(Keywords: qawanted)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14 Build Identifier: version 2.0.0.14 (20080421) Since I run my own mail server I am probably one of a few to notice this but it could affect others and lead to frustrations.... If my mail server is down, and I try to connect to it with "Get Mail" Thunderbird will properly report the failure. However, if I subsequently restart the mail server, there seems to be some sort of state information that Thunderbird remembers and it will continue to fail to connect an retrieve email. The only way to get around this is to also restart Thunderbird. This strongly indicated that the "Get Mail" process is not properly reinitialized and is "remembering" the state of the mail server in an invalid persistent sense. Reproducible: Always Steps to Reproduce: 1.Shut down mail server 2.Try to connect to it and retrieve email from it. Thunderbird fails as to be expected. 3.Restart mail server 4. Again try to connect to it and retrieve email from it. Thunderbird continues to fail which is no longer the expected behavior. Actual Results: Thunderbird continues to report a mail server problem even after the mail server problem has been resolved. A restart of Thunderbird is necessary to get a valid reconnection to the mail server. Expected Results: Should not have to restart Thunderbird. It should automatically attempt a "clean" reconnection when the "Get Mail" process is initiated, or at the least automatically retry starting from a "clean" point if a failure is detected and the user reattempts to connect.
Comment 1•16 years ago
|
||
POP or IMAP?
Reporter | ||
Comment 2•16 years ago
|
||
POP
Comment 3•16 years ago
|
||
Moving to Core -> Networking: POP, although I suspect that this problem may be shared among all protocols, in which case MailNews: Networking would be better.
Component: General → Networking: POP
Keywords: qawanted
Product: Thunderbird → Core
QA Contact: general → networking.pop
Comment 4•16 years ago
|
||
Marc, can you attach a pop log file? SET NSPR_LOG_MODULES=nsHostResolver:5,nsSocketTransport:5,pop3:5 setenv NSPR_LOG_MODULES=nsHostResolver:5,nsSocketTransport:5,pop3:5 set NSPR_LOG_FILE=c:\zip\tbirdlog.txt start "C:\Program Files\Mozilla Thunderbird\thunderbird.exe"
Reporter | ||
Comment 5•16 years ago
|
||
Hmmmm been a little while since I reported this bug and I have since gotten Thunderbird updated to version 2.0.0.18. I attempted to recreate this bug and it now works as I expect, i.e. if I stop my mail server, attempt to get mail via Thunderbird it reports that it cannot. I then restart my mail server and Thunderbird did fetch the mail so I suspect this bug has been fixed? Anywise I also attempted to generate a pop log file as Wayne had suggested, on a Windows Vista machine. The setenv command does not work under Vista, but the set commands did work, or at least did not report any errors. However when I executed the start command, it simply popped up another Windows command shell window and did not actually launch Thunderbird. I am not all that familiar with Windows scripts so I dunno what was expected or what the problem was if any. I also noted that the zip directory did not get created with the target file of tbirdlog.txt....
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Comment 6•14 years ago
|
||
WFM per comment #5. Marc feel free to reopen it if this issue reappear.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•