348771 - after running for some time, TB is unable to get new messages (no error)

Status: RESOLVED DUPLICATE of bug 165832

(Thunderbird :: General, defect)

Description

[Oleg Ostrozhansky]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6
Build Identifier: Thunderbird version 1.5.0.5 (20060719)

Using one POP3 account, downloading new messages on start-up and then every 3 minutes, into Global Inbox (Local Folders).

After awhile (can be several minutes after staring TB, or several days), TB stops downloading new messages.  Clicking on the "Get new messages" button, or F5, or File->Get new messages (either All or for the account), all do NOTHING.  No "connecting to server" message in the status bar, and Tcpview shows no outgoing connection.  Restarting TB, it gets new messages, and works for awhile,  until the problem happens again.

Reproducible: Always

Steps to Reproduce:
1. Start TB
2. Wait for problem to happen

Actual Results:  
Any action that's supposed to download new messages gets ignored.

Expected Results:  
Download new messages, or report "no new messages" in the status bar

Windows XP, Thunderbird 1.5.0.5 (20060719)

Used to work properly.  No changes to accounts or setup recently.  Started happening around the time TB has upgraded to 1.5.0.5 (automatically).  Tried disabling AV & Firewall (MCAfee), and starting TB without extensions -- all didn't make any difference.

The account is configured to leave messages on server for 90 days.  Password is not stored -- I enter it every time I start TB.  Sending mail is not affected (works even when receiving new mail doesn't).  The problem happens regardless of whether there is a new message on the server (sometimes there isn't, sometimes there is).  No filters at all.

Enabled POP3 log.  Seems that everything's normal until the problem starts happening, when nothing is written to the log any more:


08/15/06 12:40:57 0[274658]: POP3: Entering state: 15
08/15/06 12:40:57 0[274658]: POP3: Entering state: 15
08/15/06 12:40:57 0[274658]: POP3: Entering state: 15
08/15/06 12:40:57 0[274658]: POP3: Entering state: 15
08/15/06 12:40:57 0[274658]: POP3: Entering state: 15
08/15/06 12:40:57 0[274658]: POP3: Entering state: 15
08/15/06 12:40:57 0[274658]: POP3: Entering state: 15
08/15/06 12:40:57 0[274658]: POP3: Entering state: 15
08/15/06 12:40:57 0[274658]: POP3: Entering state: 22
08/15/06 12:40:57 0[274658]: SEND: QUIT
08/15/06 12:40:57 0[274658]: Entering NET_ProcessPop3 6
08/15/06 12:40:57 0[274658]: POP3: Entering state: 3
08/15/06 12:40:57 0[274658]: RECV: +OK 
08/15/06 12:40:57 0[274658]: POP3: Entering state: 43
08/15/06 12:40:57 0[274658]: POP3: Entering state: 23
08/15/06 12:40:58 0[274658]: POP3: Entering state: 25
08/15/06 12:43:57 0[274658]: Entering NET_ProcessPop3 29
08/15/06 12:43:57 0[274658]: POP3: Entering state: 1
08/15/06 12:43:57 0[274658]: POP3: Entering state: 2
08/15/06 12:43:57 0[274658]: POP3: Entering state: 4
08/15/06 12:43:57 0[274658]: RECV: +OK <27687.1155663834@mail>
08/15/06 12:43:57 0[274658]: POP3: Entering state: 31
08/15/06 12:43:57 0[274658]: SEND: CAPA
08/15/06 12:43:57 0[274658]: Entering NET_ProcessPop3 26
08/15/06 12:43:57 0[274658]: POP3: Entering state: 3
08/15/06 12:43:57 0[274658]: RECV: -ERR authorization first
08/15/06 12:43:57 0[274658]: POP3: Entering state: 32
08/15/06 12:43:57 0[274658]: POP3: Entering state: 33
08/15/06 12:43:57 0[274658]: POP3: Entering state: 5
08/15/06 12:43:57 0[274658]: SEND: USER XXXX
08/15/06 12:43:57 0[274658]: Entering NET_ProcessPop3 6
08/15/06 12:43:57 0[274658]: POP3: Entering state: 3
08/15/06 12:43:57 0[274658]: RECV: +OK 
08/15/06 12:43:57 0[274658]: POP3: Entering state: 34
08/15/06 12:43:57 0[274658]: POP3: Entering state: 6
<etc, same as 3 min ago>
08/15/06 12:43:58 0[274658]: POP3: Entering state: 15
08/15/06 12:43:58 0[274658]: POP3: Entering state: 15
08/15/06 12:43:58 0[274658]: POP3: Entering state: 15
08/15/06 12:43:58 0[274658]: POP3: Entering state: 15
08/15/06 12:43:58 0[274658]: POP3: Entering state: 15
08/15/06 12:43:58 0[274658]: POP3: Entering state: 15
08/15/06 12:43:58 0[274658]: POP3: Entering state: 15
08/15/06 12:43:58 0[274658]: POP3: Entering state: 22
08/15/06 12:43:58 0[274658]: SEND: QUIT
08/15/06 12:43:58 0[274658]: Entering NET_ProcessPop3 6
08/15/06 12:43:58 0[274658]: POP3: Entering state: 3
08/15/06 12:43:58 0[274658]: RECV: +OK 
08/15/06 12:43:58 0[274658]: POP3: Entering state: 43
08/15/06 12:43:58 0[274658]: POP3: Entering state: 23
08/15/06 12:43:58 0[274658]: POP3: Entering state: 25
<nothing more after this>
Even though it's been a lot more than 3 minutes since 12:43, and
I've clicked on "Get new messages" numerous times.

(time added to the log file with "tail -f | awk" (Cygwin))

Comment 1

[jwq]

This would appear to be a duplicate of Bug 245811.

Reporter (Oleg): Please check Bug 245811 and mark this bug as a duplicate of Bug 245811 if you agree that they are the same. Placing a comment in Bug 245811 that you see the bug in version 1.5.0.5 (20060719) would also be helpful.

Comment 2

[Oleg Ostrozhansky]

(In reply to comment #1)
> This would appear to be a duplicate of Bug 245811.

Ok, the symptoms are the same, but my setup is completely different than what's reported in that bug:
- My profile is not on a network drive,
- I am checking for new messages periodically

I'll make this one a dupe.  For now I've tried removing Inbox.msf and compacting Inbox, as suggested in Bug 245811.  Once I know if it made a difference, I'll follow-up there.  (My Inbox was ~20MB, after compacting it's ~1MB, ~80 messages).

Comment 3

[Oleg Ostrozhansky]

*** This bug has been marked as a duplicate of 245811 ***

Comment 4

[Oleg Ostrozhansky]

Bug 165832 is a much better one to dupe to.  It has exact description of this problem (comments #7, #10), and references many other related bugs.

Note that I've added an attachment to Bug 245811 showing states of the threads, which might be helpful to someone working on this problem.


*** This bug has been marked as a duplicate of 165832 ***

Comment 5

[Wayne Mery (:wsmwk)]

Oleg, if you still see this problem, please reopen the bug - because Bug 165832 is not something that will fix anything, it's a meta bug