Repeated alerts on inaccessible imap account



15 years ago
13 years ago


(Reporter: rjellison, Assigned: mscott)


Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2
Build Identifier: version 0.7+ (20040714) as well as version 7.,2

I have multiple email accounts. One IMAP account requires that I first establish
a VPN connection. The account setup is: check new mail on startup, check new
mail every 20 minutes.

If I start Thunderbird without first creating the VPN connection, then as
expected I get a "can not connect" alert. With Version 6 of Thubderbird and with
Version 7.1 of Mozilla, I did not get any further alerts that the connection is
not accessible. With Version 7 and the branch builds for 8, I get an alert every
5 minutes on being "unable to access imap server ...."

I then unchecked the account server options "check new mail on start" and "check
new mail every 20 minutes" and restarted Thunderbird. I don't get the alert on
startup, but I still get an alert every 5 minutes on being unable to access the
imap server.

Reproducible: Always
Steps to Reproduce:
1.Reference to an unaccessable IMAP server
2.Uncheck the check new mail option

Actual Results:  
Repeated alerts that the server is not accessable.

Expected Results:  
No alerts. If the new mail option is checked, then there should be at most one
alert. Unfortunately the work offline option applies to all acounts. It would be
nice to have such a feature on each account.
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.