User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 Every now and then, my mail server receives a very strange empty email. Im using a pop3 account. When you click the "get mail" button, Thunderbird displays receiving message 1 of 10 and waits forever. Thunderbird does not totaly hang when trying to receive the messages, you can still receive messages on other mailboxes and write messages. When you click the "get mail" button again, a dialog box appears saying "This folder is being processed. Please wait until processing is complete to get messages." I am using version 0.7.2 (20040707) Reproducible: Always Steps to Reproduce: 1.Put the msg is in the mailbox on the mail server 2.Click the "Get mail" button Actual Results: Thunderbird should be stuck on "receiving message 1 of blah" forever Expected Results: received the msg This is the raw email: Return-Path: <vwqcyyneriyfep@krovatka.net> Delivered-To: michael@lateralfood.com Received: (qmail 32285 invoked by alias); 31 Jul 2004 12:26:47 -0000 Delivered-To: info@lateralfood.com Received: (qmail 32225 invoked from network); 31 Jul 2004 12:26:46 -0000 Received: from 65.162.63.71.quickclick.ctc.net (65.162.63.71) by headcracker.lateralfood.com with SMTP; 31 Jul 2004 12:26:46 -0000 X-Message-Info: R[1

(In reply to comment #0) > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 > Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 > > Every now and then, my mail server receives a very strange empty email. Im using > a pop3 account. When you click the "get mail" button, Thunderbird displays > receiving message 1 of 10 and waits forever. Thunderbird does not totaly hang > when trying to receive the messages, you can still receive messages on other > mailboxes and write messages. When you click the "get mail" button again, a > dialog box appears saying "This folder is being processed. Please wait until > processing is complete to get messages." > > I am using version 0.7.2 (20040707) > > > Reproducible: Always > Steps to Reproduce: > 1.Put the msg is in the mailbox on the mail server > 2.Click the "Get mail" button > > Actual Results: > Thunderbird should be stuck on "receiving message 1 of blah" forever > > Expected Results: > received the msg > > This is the raw email: > > Return-Path: <vwqcyyneriyfep@krovatka.net> > Delivered-To: michael@lateralfood.com > Received: (qmail 32285 invoked by alias); 31 Jul 2004 12:26:47 -0000 > Delivered-To: info@lateralfood.com > Received: (qmail 32225 invoked from network); 31 Jul 2004 12:26:46 -0000 > Received: from 65.162.63.71.quickclick.ctc.net (65.162.63.71) > by headcracker.lateralfood.com with SMTP; 31 Jul 2004 12:26:46 -0000 > X-Message-Info: R[1 I have only experienced this problem on win2k. It does not occure on linux and im not sure if it does on XP. i have upgraded to thunderbird 0.7.3 and the problem still exists

I would like to report that I have the same problem, using the latest Release Candidate on Windows 2K. I have not tried the Linux version of Thunderbird. I also noted that bug 222115 seems somewhat similar. I also have "leave on server" turned on, but I am going to try turning it off when I see this happening again.

Similar situation is under analysis in Bug 228649. Russell Aronson(reporter of this bug) and Evan Jones, get protocol log, in order to know whether your problem is same or not. For protocol log, see http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#pop Please note that log file is overlayed on restart. Log file should be back-uped after shutdown.

thunderbird log file 0[2343e8]: mail.pop3_response_timeout=45 0[2343e8]: Entering NET_ProcessPop3 18 0[2343e8]: POP3: Entering state: 1 0[2343e8]: POP3: Entering state: 2 0[2343e8]: POP3: Entering state: 4 0[2343e8]: RECV: +OK Hello there. 0[2343e8]: POP3: Entering state: 29 0[2343e8]: SEND: AUTH 0[2343e8]: Entering NET_ProcessPop3 23 0[2343e8]: POP3: Entering state: 3 0[2343e8]: RECV: -ERR Invalid command. 0[2343e8]: POP3: Entering state: 30 0[2343e8]: POP3: Entering state: 31 0[2343e8]: SEND: CAPA 0[2343e8]: Entering NET_ProcessPop3 27 0[2343e8]: POP3: Entering state: 3 0[2343e8]: RECV: +OK Here's what I can do: 0[2343e8]: POP3: Entering state: 32 0[2343e8]: Entering NET_ProcessPop3 6 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: STLS 0[2343e8]: POP3: Entering state: 32 0[2343e8]: Entering NET_ProcessPop3 5 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: TOP 0[2343e8]: POP3: Entering state: 32 0[2343e8]: Entering NET_ProcessPop3 6 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: USER 0[2343e8]: POP3: Entering state: 32 0[2343e8]: Entering NET_ProcessPop3 16 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: LOGIN-DELAY 10 0[2343e8]: POP3: Entering state: 32 0[2343e8]: Entering NET_ProcessPop3 12 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: PIPELINING 0[2343e8]: POP3: Entering state: 32 0[2343e8]: Entering NET_ProcessPop3 6 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: UIDL 0[2343e8]: POP3: Entering state: 32 0[2343e8]: Entering NET_ProcessPop3 36 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: IMPLEMENTATION Courier Mail Server 0[2343e8]: POP3: Entering state: 32 0[2343e8]: Entering NET_ProcessPop3 3 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: . 0[2343e8]: POP3: Entering state: 33 0[2343e8]: POP3: Entering state: 5 0[2343e8]: SEND: USER michael 0[2343e8]: Entering NET_ProcessPop3 24 0[2343e8]: POP3: Entering state: 3 0[2343e8]: RECV: +OK Password required. 0[2343e8]: POP3: Entering state: 34 0[2343e8]: POP3: Entering state: 6 0[2343e8]: Logging suppressed for this command (it probably contained authentication information) 0[2343e8]: Entering NET_ProcessPop3 16 0[2343e8]: POP3: Entering state: 3 0[2343e8]: RECV: +OK logged in. 0[2343e8]: POP3: Entering state: 34 0[2343e8]: POP3: Entering state: 7 0[2343e8]: SEND: STAT 0[2343e8]: Entering NET_ProcessPop3 11 0[2343e8]: POP3: Entering state: 3 0[2343e8]: RECV: +OK 1 419 0[2343e8]: POP3: Entering state: 8 0[2343e8]: POP3: Entering state: 9 0[2343e8]: SEND: LIST 0[2343e8]: Entering NET_ProcessPop3 55 0[2343e8]: POP3: Entering state: 3 0[2343e8]: RECV: +OK POP3 clients that break here, they violate STD53. 0[2343e8]: POP3: Entering state: 10 0[2343e8]: Entering NET_ProcessPop3 7 0[2343e8]: POP3: Entering state: 10 0[2343e8]: RECV: 1 419 0[2343e8]: POP3: Entering state: 10 0[2343e8]: Entering NET_ProcessPop3 3 0[2343e8]: POP3: Entering state: 10 0[2343e8]: RECV: . 0[2343e8]: POP3: Entering state: 11 0[2343e8]: SEND: UIDL 0[2343e8]: Entering NET_ProcessPop3 5 0[2343e8]: POP3: Entering state: 3 0[2343e8]: RECV: +OK 0[2343e8]: POP3: Entering state: 12 0[2343e8]: Entering NET_ProcessPop3 22 0[2343e8]: POP3: Entering state: 12 0[2343e8]: RECV: 1 UID3943-1089270930 0[2343e8]: POP3: Entering state: 12 0[2343e8]: Entering NET_ProcessPop3 3 0[2343e8]: POP3: Entering state: 12 0[2343e8]: RECV: . 0[2343e8]: POP3: Entering state: 15 0[2343e8]: POP3: Entering state: 18 0[2343e8]: SEND: RETR 1 0[2343e8]: Entering NET_ProcessPop3 24 0[2343e8]: POP3: Entering state: 3 0[2343e8]: RECV: +OK 419 octets follow. 0[2343e8]: POP3: Entering state: 19 0[2343e8]: Opening message stream: MSG_IncorporateBegin 0[2343e8]: Done opening message stream! 0[2343e8]: RECV: (null) 0[2343e8]: mail.pop3_response_timeout=45 0[2343e8]: Entering NET_ProcessPop3 18 0[2343e8]: POP3: Entering state: 1 0[2343e8]: POP3: Entering state: 2 0[2343e8]: POP3: Entering state: 4 0[2343e8]: RECV: +OK Hello there. 0[2343e8]: POP3: Entering state: 31 0[2343e8]: SEND: CAPA 0[2343e8]: Entering NET_ProcessPop3 117 0[2343e8]: POP3: Entering state: 3 0[2343e8]: RECV: +OK Here's what I can do: 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: STLS 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: TOP 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: USER 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: LOGIN-DELAY 10 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: PIPELINING 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: UIDL 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: IMPLEMENTATION Courier Mail Server 0[2343e8]: POP3: Entering state: 32 0[2343e8]: RECV: . 0[2343e8]: POP3: Entering state: 33 0[2343e8]: POP3: Entering state: 5 0[2343e8]: SEND: USER michael 0[2343e8]: Entering NET_ProcessPop3 24 0[2343e8]: POP3: Entering state: 3 0[2343e8]: RECV: +OK Password required. 0[2343e8]: POP3: Entering state: 34 0[2343e8]: POP3: Entering state: 6 0[2343e8]: Logging suppressed for this command (it probably contained authentication information) 0[2343e8]: Entering NET_ProcessPop3 16 0[2343e8]: POP3: Entering state: 3 0[2343e8]: RECV: +OK logged in. 0[2343e8]: POP3: Entering state: 34 0[2343e8]: POP3: Entering state: 7 0[2343e8]: SEND: STAT 0[2343e8]: Entering NET_ProcessPop3 11 0[2343e8]: POP3: Entering state: 3 0[2343e8]: RECV: +OK 1 419 0[2343e8]: POP3: Entering state: 8 0[2343e8]: POP3: Entering state: 24 0[2343e8]: POP3: Entering state: 25

Your log around RETR >(snip) > 0[2343e8]: SEND: LIST >(snip) 0[2343e8]: RECV: 1 419 >(snip) > 0[2343e8]: SEND: UIDL >(snip) > 0[2343e8]: RECV: 1 UID3943-1089270930 >(snip) > 0[2343e8]: SEND: RETR 1 > > 0[2343e8]: Entering NET_ProcessPop3 24 > 0[2343e8]: POP3: Entering state: 3 > 0[2343e8]: RECV: +OK 419 octets follow. > 0[2343e8]: POP3: Entering state: 19 > 0[2343e8]: Opening message stream: MSG_IncorporateBegin > 0[2343e8]: Done opening message stream! > 0[2343e8]: RECV: (null) > 0[2343e8]: mail.pop3_response_timeout=45 Server says "419 octets", but sends only "(null)", then client waits for following data. Looks like same problem as Bug 228649. Waiting for analysis by developer.

yes, that's the anti-virus software intercepting the pop3 stream and basically generating incorrect protocol. *** This bug has been marked as a duplicate of 228649 ***

(In reply to comment #6) > yes, that's the anti-virus software intercepting the pop3 stream and basically > generating incorrect protocol. "anti-virus software" at client side? Or Serverside? Russell Aronson, do you use mail scaning function of anti-virus software? If yes, what is your anti-virus software?

Sorry, I missed Bug 228649 Comment #42. Bug 228649 was Norton Antivirus case, fault of client anti-virus software.

(In reply to comment #6) > yes, that's the anti-virus software intercepting the pop3 stream and basically > generating incorrect protocol. I'd be carefull. Not for every message retrieve-problem with "RECV: (null)" the AV is to blame. I know we had enough AV caused ones in the past and AFAIK no Mozilla/TB caused of this type. But until a reporter confirmed he's using an AV and it works with it off, I wouldn't dupe it.

(In reply to comment #7) > "anti-virus software" at client side? Or Serverside? > > Russell Aronson, do you use mail scaning function of anti-virus software? > If yes, what is your anti-virus software? > yes, i use client side anti-virus software, Norton Auto Protect. The problem is with the message though. i have access to a qmail mail server and if i put the raw message in the que, it has the problem. It does not matter if norton is activated or not. i have no server side anti-virus tools.

Re-open according to Comment #10. This bug is not caused by client side anti-virus software, seems to be by server side sofotware instead.

(In reply to comment #10) > i use client side anti-virus software, Norton Auto Protect. > The problem is with the message though. > i have access to a qmail mail server and if i put the raw message in the que, > it has the problem. > It does not matter if norton is activated or not. (Q1) Have you disabled "mail scaning function" of Norton Auto Protect? "mail scaning function" is different form usual virus protection. Communication between client and server is changed by Norton as follows. (1) Initial set up Mozilla <-> POP3 server (2) Norton changes to next configuration (or by you when manual configuration) Mozilla <-> Local proxy by Norton <-> POP3 server This is done by changing mail server definition of Mozilla. (Mail sever is changed to localhost or 127.0.0.1 usually) See your account settings of Mozilla - Server Setting. Have you changed back it to (1) from (2)?

(In reply to comment #12) > (Q1) Have you disabled "mail scaning function" of Norton Auto Protect? > "mail scaning function" is different form usual virus protection. > Communication between client and server is changed by Norton as follows. > (1) Initial set up > Mozilla <-> POP3 server > (2) Norton changes to next configuration > (or by you when manual configuration) > Mozilla <-> Local proxy by Norton <-> POP3 server > This is done by changing mail server definition of Mozilla. > (Mail sever is changed to localhost or 127.0.0.1 usually) > See your account settings of Mozilla - Server Setting. > Have you changed back it to (1) from (2)? i use Norton Auto Protect, not a norton proxy. thunderbird is contacting the mail server directly. it does not matter if i enable or disable the auto protect function.

Russell Aronson, do you use "Virus check service for mail" of your provider? According to Comment #13, this problem is proved that mail server problem, lie on data length. Chirstian and David, what should we do in this case?

(In reply to comment #14) > Russell Aronson, do you use "Virus check service for mail" of your provider? > > According to Comment #13, this problem is proved that mail server problem, lie > on data length. > Chirstian and David, what should we do in this case? > im running a qmail server with no filtering. Maybe my ISP filters trafic coming through port 25? either way, thunderbird should be able to deal with this sort of problem msg.

(In reply to comment #15) > im running a qmail server with no filtering. Maybe my ISP filters trafic coming > through port 25? What is your configuration? - Mozilla(client)<->QMAIL(your private server)<->POP3(ISP) ? If yes, fault of QMAIL server, usually.

(In reply to comment #16) > What is your configuration? > - Mozilla(client)<->QMAIL(your private server)<->POP3(ISP) ? > If yes, fault of QMAIL server, usually. Mozilla(client)<->POP3 QMAIL(your private server) mail does not get forwarded to my server from my ISP's mail server. is that what u ment?? my ISP is just an internet connection. i suspect that they filter traffic on port 25 but im not sure...

(In reply to comment #17) > mail does not get forwarded to my server from my ISP's mail server. is that what > u ment?? my ISP is just an internet connection. i suspect that they filter > traffic on port 25 but im not sure... Your configuration : Mozilla<->POP3(QMAIL,private server)<->(Access Point of ISP)<->External Network If yes, aparantly fault of your private POP3 server(QMAIL server). Even if "Header only mail" is a result of ISP's filtering, the "Header only mail" is written in QMAIL's mail data base by QMAIL himself. Then correct length of the mail have to be notified to Mozilla by QMAIL, your private mail server. (1) Check you QMAIL configuration/settings. (2) Check who cuts the mail, QMAIL, your ISP, other mail server between mail sender's SMTP server and your QMAIL server(servers written in Recived: headers, if Received: headers are not altered by someone else.), or other anti-virus software on computer where QMAIL runs. Anyway, I think this bug should be closed as INVALID.

(In reply to comment #18) > Your configuration : > Mozilla<->POP3(QMAIL,private server)<->(Access Point of ISP)<->External Network > If yes, aparantly fault of your private POP3 server(QMAIL server). > Even if "Header only mail" is a result of ISP's filtering, the "Header only > mail" is written in QMAIL's mail data base by QMAIL himself. > Then correct length of the mail have to be notified to Mozilla by QMAIL, your > private mail server. > (1) Check you QMAIL configuration/settings. > (2) Check who cuts the mail, QMAIL, your ISP, other mail server between mail > sender's SMTP server and your QMAIL server(servers written in Recived: headers, > if Received: headers are not altered by someone else.), or other anti-virus > software on computer where QMAIL runs. > > Anyway, I think this bug should be closed as INVALID. i can see that this is a mail server problem. i still have access to the mail server but i do not use it for mail any more (recently de-commissioned) the whole thing about this bug is that it only occurs on thunderbird, not other mail clients like outlook or web based clients like squirrelmail... its a problem with the server, i agree, but the client should be able to deal with it.

(In reply to comment #19) > the whole thing about this bug is that it only occurs on thunderbird, not other > mail clients like outlook or web based clients like squirrelmail... its a > problem with the server, i agree, but the client should be able to deal with it. Sorry for late response. After your bug, some bugs for similar situation were opened ; (1) Bug 253886 (this bug) Timeout due to anti-virus software at mail server side(probably) (2) Bug 270014 Timeout due to real server busy (many mails on server, or large mails) (3) Bug 273369 Timeout due to delay when virus-check by client side anti-virus software for very large mail (4) Bug 274429 Probably same case as yours. In analysis of Bug 270014, developer taugth me that the timeout detection is a new feature. I think that this is mainly to avoid "forever wait" in your case(or Bug 274429 's case), and it works well - no "forever wait" even when your case after the feature. ( Though, I also think there is no difference for users when your case, ) ( since nothing will happen and the mail will never be downloaded. ) I agree with you on "the client should be able to deal with it", as I wrote in Bug 270014 Comment #9. The timeout shoud be notified to user. But I think your initial problem of "This folder is being processed" due to "forever wait" has been already resolved by the new timeout feature. Your new problem after comment #4(not forever wait, but mail download fail) is new problem after the new timeout feature, and is different from your initial problem. So I think there is 2 ways ; (1) Keep this bug REOPEND, and continue to request new something by this bug. (2) Close this bug as "WORKSFORME", (for initial problem, can be FIXED although bug no. is not apparent), then open new enhancement request bug for timeout notification, based on your log in comment #4 and other bugs. I recommend you (2), because it is common issue among this bug, bug 270014 and bug 273369.

Third way (This is the best among three?). (3) Close as DUP of Bug 228649 again, then open enhancement request bug.

(In reply to comment #21) > Third way (This is the best among three?). > (3) Close as DUP of Bug 228649 again, then open enhancement request bug. > im happy to mark it as a DUP of 228649, the problem is essentially the same, the problem mail is on the server though so its not client AV software. i don't think ill need to open an enhancement request bug if there r already people dealing with this issue. thanks for keeping at it *** This bug has been marked as a duplicate of 228649 ***

(In reply to comment #22) > i don't think ill need to open an enhancement request bug > if there r already people dealing with this issue. I've opened Bug 277071 today, since no one requested it in last year.