Closed Bug 274360 Opened 20 years ago Closed 19 years ago

Get All New Messages function does not consistently check all e-mail accounts

Categories

(Thunderbird :: General, defect)

x86
All
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: carl, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

After one of our mail servers crashed it resulted in connection timeout errors
and username/password errors in Thunderbird for the e-mail accounts that were
hosted on that server while it was offline and after it went back online but
before the accounts were restored.  

Following the restoration of the server and it's accounts the "Get All New
Messages" option of the Get Mail button fails to consistently check those
accounts.  Sometimes it checks them and sometimes it doesn't, but there doesn't
appear to be any identifiable pattern in either case that would indicate why it
fails to consistently check these accounts.

We have several Linux and Windows desktops in our office and the problem is the
same for Thunderbird on all of these computers for the same e-mail accounts
where the server crashed and resulted in connection timeout and
username/password errors.  Prior to the server crash we were not experiencing
this problem with any of our e-mail accounts.  Following the server crash we
have been experiencing the same problem with the same e-mail accounts on all of
the computers where Thunderbird is installed regardless of OS.

The mail server that crashed is running Redhat Linux ES 2.1 with Plesk 7.5
Reloaded installed as the server manager and Qmail as the mail server software.
 This server was restored to its previous state with the same software and
configuration following the crash.  In addition, we have another mail server
with identical software and configuration and we have no problems with
Thunderbird regarding the e-mail accounts on that server.

Reproducible: Sometimes
Steps to Reproduce:
1.Shut down a server that had active e-mail accounts checked by Thunderbird and
then check e-mail using the Get All New Messages option
2.Restart the server with the e-mail account passwords disabled, check mail
again, then re-enable the accounts
3.Check mail again using the Get All New Messages option

Actual Results:  
Using the Get All New Messages option, Thunderbird fails to consistently check
the e-mail accounts that previously experienced connection timeout and
username/password error messages.

Expected Results:  
The Get All New Messages option of the Get Mail button should consistently check
all e-mail accounts every time it is selected.
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.