182487 - fetching pop mail retries always after a failed pop account access

Status: RESOLVED EXPIRED

(MailNews Core :: Networking: POP, defect)

Description

[Andreas Zickner]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126

Some providers set up the pop accounts that you are only allowed to check for
mail every minute. In case you are trying to check the mailwithin the interval
you get the error message like '... pass does not succed within x minutes ...'.
previous mail versions (release <= 1.1) marked the password invalid and you hat
to type it again. 1.2 seem to retry within a modal dialog, which fails again.
Workarround: 
1) use Alt-F4 as long the dialog and the mail window is closed (sideeffect is
that the whole suite may be closed)
2) kill mozilla :-(

Reproducible: Always

Steps to Reproduce:
1. get mail from a pop3 account which allows only one acces within one interval
2. do it again before the time limit exceeds
3.

Actual Results:  
you are not able to access the mail window any more. Other windows may also be
blocked 'somehow' (not quite sure but I got mozilla once in a state nothing was
working any more ...)

Expected Results:  
no automatic retry after the error window was shown to the user once. let the
user decide to retry.

tried with 1.2b and 1.2 on windoze32, linux default skin and pinball skin -> all
the same

(sorry for a private comment:  great software!!!!!!)

Comment 1

[John Stracke]

This bug causes extra problems in an environment with a "three strikes" policy.

I'm using Mozilla to talk to Exchange via IMAP.  The company uses Active
Directory to unify all our passwords, and I just had to change mine.  When I
went to get my mail, I found that Mozilla failed to authenticate (not
surprising), but then, when I clicked "OK" on the authenticate-failed dialog, it
retried 2-3 times more...and our Active Directory is set up to freeze any
account that gets 3 consecutive failures.  I am now locked out of all servers on
our internal network, because Mozilla retried a password that it was told was no
good.

This is Mozilla 1.3; it didn't do this in 1.1.  (I don't know about 1.2, because
I couldn't use it; I kept hitting the bug with ATI Rage cards.) A very nasty
surprise.

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.