208527 - Mozilla trashes one of the user accounts, can't authenticate any more

Status: RESOLVED EXPIRED

(MailNews Core :: Networking: POP, defect)

Description

[resigned]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312

First, I had the problem described in a previous bug (still trying to find it to
get a ref number) whereby if mozilla fetches mail whilst the network connection
is down / redialling, it hangs for ages (about 3 minutes or more) with the busy
symbol in top right - note, pressing the stop button has no effect, and until it
timesout, you CANNOT collect mail on whichever accounts were being checked. This
is obviously a bug).

Second bug that occurred was the one where - in the above situation - if you
close mozilla mail, with a browser open somewhere, then reopen it, the busy
symbol shows idle (NOT busy), but you cannot check any accounts for mail. Since
I cannot find a ref for this bug either ATM, suffice it to say that this happens
EVERY TIME you take these actions in this situation.

Now, for the new bug. I closed down all the mozilla windows, and started mozilla
again. I think moz was largely swapped to disk, because there was a lot of disk
activity, AND when I restarted moz I got the dialgo asking me to choose users
(which otherwise only occurs if moz has crashed and left the lock file hanging
around). So, I quit that, waited a minute, tried again. By this time the disk
access had stopped, and it appeared moz had COMPLETELY shutdown, and moz
restarted fine, without the "select profile" dialog.

However, when I went to check messages on my primary account, I got the error
message saying PASS failed, server message: "Bad Authentication". This now
happens every time, and I cannot get rid of it! My other accounts (all of which
are on the same server, and all of which are identical config, except that they
have different usernames and passwords) all work fine.

Reproducible: Always

Steps to Reproduce:
1.read the details
2.
3.

Actual Results:  
read the details

Expected Results:  
read the details

Comment 1

[resigned]

Update: After 3 restarts, the problem has gone away.

I'm guessing therefore that the problem was partly with the mailserver (I've
asked the ISP to comment, but they probably won't).

Perhaps Mozilla did something that got the mailserver upset about that one
account for a short while? (I'm just guessing here, I'm afraid).

THe ISP who's mailserver it was is www.hostway-uk.com, and it's one of their
linux servers.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.