197156 - After inactivity and online/offline/online can't retrieve new POP messages

Status: RESOLVED DUPLICATE of bug 192040

(MailNews Core :: Networking: POP, defect)

Description

[Eric Stern]

User-Agent:       Mozilla/5.0 (compatible; MSIE 5.5; X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210

I start up Mozilla 1.3b, get messages from two different POP accounts.  I go
offline and leave the program inactive for a while (overnight).  Then I go back
online and hit the "get msgs" button. There is no apparent network activity, no
spinner indication that the program is trying to do anything and no notification
that it thinks there are or are not any new messages.  I know that I have
messages by sending a message to one of the POP mailboxes from Yahoo mail.  I
can display any existing message in any mail account so the program is not
"hung".  CPU usage is normal.  This didn't happen in 1.3a.

Reproducible: Always

Steps to Reproduce:
1. Start up Mozilla 1.3b.
2. Bring up Mail.
3. Get new messages.
4. Spinner shows network activity
5. Bring down ppp connection.  Leave Mozilla running.
6. Leave program idle for several hours?
7. Bring up ppp connection to ISP
8. Send a mail message to POP account from Yahoo mail or from own system.
9. Try to get new messages with "Get Msgs" button in Mail application.


Actual Results:  
No network activity.  No spinners showing program activity.  No messages that
there is or is not any new mail.

Expected Results:  
Mozilla should have retrieved new messages.

Modern theme.  Mozilla 1.3b.  Three POP accounts, two of which are active.  The
same behavior occurs with both active POP accounts.  Debian Linux 3.0.  Libc6
2.2.5-11.  This didn't happen in mozilla 1.3a.

Comment 1

[Eric Stern]

I just tried this with the newly released 1.3.  I still had the same problem.
I started up mozilla and checked mail, then went offline at 17:20.  At 18:58 I
went back online.  I was unable to get any new mail to download.

Comment 2

[Eric Stern]

The weird user-agent string is because I have set the general.useragent.override
preference in user.js because the online banking site that I use has JS code
that explicitly checks the useragent for a "supported" version.

Comment 3

[Scott Morgan]

I get this problem on 1.3 also but the throbber/spinner is active when I come to
it. Seems to be related to Bug #197655

Comment 4

[R.K.Aa.]

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