Closed
Bug 233363
Opened 21 years ago
Closed 21 years ago
Error on send with SBC mailservers
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 232860
People
(Reporter: jon.roland, Assigned: sspitzer)
Details
User-Agent:
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113
My ISP is SBC, with whom I have a DSL account. Until about Jan. 15 I encountered
no difficulty in using Mozilla mail with any of their mail servers, however,
beginning about that date, first intermittently, and since Feb. 2 constantly,
when I send a message I get the error message:
The message could not be sent because connecting to SMTP server
mail.sbcglobal.net failed. The server may be unavailable or is refusing
SMTP connections. Please verify that your SMTP server is correct and try
again, or else contact your network administrator.
In most, but not all, cases the message does indeed get out successfully, but
the error prevents the message from being saved into the Sent folder, so I have
to first save it to the Drafts folder, then move it into the Sent folder.
I have complained about the problem to SBC Tech Support, who challenged me to
test a send using MS Outlook, which, besides the Mac email client, is the onlh
client they support. No error using Outlook.
I also experimented using other mail servers of theirs, and machines and Mozilla
under Linux, but get the same error. Error-free sends only seem to work now with
Outlook. :(
I further experimented using different ports. Using port 25 the send is nearly
always successful, but using port 110 only successful about 60% of the sends.
The behavior suggests there may be a timeout problem, and a race to send before
the timeout occurs.
While it might seem that is is the ISP's problem, the fact that it works with
Outlook suggests we may need to address it from the Mozilla side, since SBC is a
major ISP.
Has anyone else experienced this problem? I am in Austin, Texas.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1•21 years ago
|
||
Already fixed, please use a current trunk-nightly.
*** This bug has been marked as a duplicate of 232860 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•