Closed Bug 233672 Opened 21 years ago Closed 19 years ago

Errors while sending and receiving mail requires reboot to fix

Categories

(MailNews Core :: Networking, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: mis, Assigned: sspitzer)

References

Details

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

On a semi-regular basis two (out of 15) Mozilla 1.6 installations (On W2KSP4)
become unable to send or receive mail. The problem seems to appear most often
when the Mozilla program is left running idle for any length of time beyond 30
minutes.

After that time, when the users attempt to retrieve email, they receive the
following error:

"Could Not Connect to Server mail.companyname.com; The Connection Was Refused."

When trying to send mail, they receive this error:

"Sending of Message Failed. The Message Could Not Be Sent Because Connecting to
the SMTP Server mail.companyname.com failed. The server may be unavailable or is
refusing SMTP connections. Please verify that your SMTP server setting is
correct and try again, or else contact your network administrator."

Because this is not happening with the other 13 Mozilla installations (nor the
Lookout or Eudora installations either) on the LAN using the same gateway, I'm
not inclined to believe this is a problem with the email contactor's server.

The computers still have network connectivity, and I can successfully ping local
systems and the email server, and the computers in question can download web pages.

The error messages occur irregardless of the account/server being downloaded.
One of my users downloads from 4 different servers and once these errors are
received, it lockes him out of all four.

Restarting Mozilla doesn't clear up the problem. The only fix that I have been
able to find is to reboot the computer.

I have tried reinstalling Mozilla, and the problem persists.

Reproducible: Sometimes
Steps to Reproduce:
1. Leave the system idle with Mozilla running for more than 30 minutes
2. Try to send email.

Note: This occurs only on 2 of 15 Mozilla deployments on my LAN. There are 13
other computers that I can't duplicate this problem on at all.




Systems with this problem are running Windows 2000 Professional Service Pack 4.
One of the affected users has local administrative rights, the other does not.
Both systems are members of a Windows 2000 Domain.
Both installations of Mozilla are using the "Modern" Theme
*** Bug 233722 has been marked as a duplicate of this bug. ***
Flags: blocking1.8a+
Severity: normal → major
only drivers can set (+) blocking flags.  you can request (?) them.
Flags: blocking1.8a+
Product: MailNews → Core
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
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.