200133 - Upgrade to moz 1.3 set 'check for mail every x' on for account which had had it off

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Account Configuration, defect)

Description

[Judd Rogers]

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

My IS team thought I was running some sort of weak DoS attack on the
exchange server! :-)

I have several mail accounts. The main one points to a linux box where I use
fetchmail to drag mail down from the exchange server.

I also have an account for the exchange server itself.

That second account did not have the 'check for new mail every x' flag on. The
first account does have this flag on. Since the exchange account does not poll
the server I don't tend to keep its password up to date.

I upgraded to 1.3.

A couple of days later the IS team is asking me what program is repeatedly
trying to log on to the exchange server and failing. Fetchmail is ok. Very
strange. But wait, mozilla knows about the exchange server - could that be it?
Sure enough, the exchange account now has the 'check' flag on.

So, two problems. 1) the upgrade turned the 'check' flag on. 2) Moz does not ask
you for a new password if it can't log on to a mail server (is there a current
bug for this? There was an old one)

Reproducible: Always

Steps to Reproduce:





This is going to make Mozilla unpopular with IS departments.
No one likes programs wacking on a server for no reason.

Comment 1

[Travis Chase]

Reporter is this still a problem for you?

Comment 2

[Judd Rogers]

No, the problem has not manifested itself again. 
 
It would be sufficient to add tests to Mozilla to ensure this problem never 
happens again. 

Comment 3

[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 4

[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.