 Rocky67Pencil Neck GeekPremium
join:2005-01-13
Orange, CA | [Availability] Mail Server Down FYI: smtpauth.sbcglobal.net (207.115.36.25) is currently down.
--
"The Internet? Is that still around?" - Homer |
|
 LanikLab-nikPremium,ExMod 2002-03
join:2001-06-25
Bay Area | Works for me:
telnet smtpauth.sbcglobal.net 25
Trying 207.115.36.25...
Connected to smtpauth.sbcglobal.net (207.115.36.25).
Escape character is '^]'.
220 nlpi042.sbcis.sbc.com ESMTP Sendmail 8.13.8 smtpauth/dk/8.13.8; Thu, 26 Oct 2006 17:35:32 -0500
--
"If it ain't broke don't fix it."
Computer Consulting for the Next Generation. |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
 ·SONIC.NET
·Pacific Bell - SBC
2 edits | 
net' failed. |
said by Lanik:Works for me: The screen shot only tells part of the story. Job MO000003 had been failing consistently since before 1300. Mercury queues email, and retries on connection failures at the rate of one attempt every 30 minutes. I had seen several failures when I was checking on job MO00000D. I tried restarting the server, but still got a failure, so I changed the client from accessing 'smtpauth.sbcglobal.net' to accessing 'smtp.pacbell.yahoo.com'.
Addendum:
I forgot to include the client connection log:
E 20061026 143034 fff61331 Error connecting to smtpauth.sbcglobal.net.
E 20061026 150125 fff61331 Error connecting to smtpauth.sbcglobal.net.
E 20061026 153216 fff61331 Error connecting to smtpauth.sbcglobal.net.
E 20061026 160306 fff61331 Error connecting to smtpauth.sbcglobal.net.
E 20061026 163327 fff61331 Error connecting to smtpauth.sbcglobal.net.
E 20061026 170417 fff61331 Error connecting to smtpauth.sbcglobal.net.
E 20061026 173508 fff61331 Error connecting to smtpauth.sbcglobal.net.
E 20061026 180530 fff61331 Error connecting to smtpauth.sbcglobal.net.
E 20061026 181316 fff22099 Error connecting to smtpauth.sbcglobal.net.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
Rocky67Pencil Neck GeekPremium
join:2005-01-13
Orange, CA Reviews:
·AT&T Yahoo
| I finally changed my client to access smtp.pacbell.yahoo.com, also. I changed to smtpauth.sbcglobal.net a year or so ago because of a similar problem I was having with the pacbell.yahoo server.
Right now, I'm still unable to access smtpauth.sbcglobal.net.
--
"The Internet? Is that still around?" - Homer |
|
jonrkcPremium
join:2003-05-19
Kansas City, MO
1 edit | Does anybody in the old Southwestern Bell area (includes Missouri, where I am) know of a different smtp server that I could use? Unable to access smtpauth.sbcglobal.net with TWO out of THREE email clients. For whatever reason, (Novell) Evolution is able to get through.
I changed to smtpauth.sbcglobal.net when I couldn't access smtp.sbcglobal.net maybe two years ago (not sure). I wouldn't have known what to do except for probing around here in the dslreports forums.
Looks like a similar problem now, but it's strange that one client (which I prefer not to use) is able to get through.
UPDATE AND SOLUTION: I changed the port for smtpauth from 587 to 25 and now it works. I had changed from 25 (after begging to get it unblocked, which SBC promptly did) to 587 after supposedly SBC stopped using port 25. I learned the magic number 587 here at dslreports, without which apparently I could not operate my computer, or at least email.
Now it looks like 587 is out of business, and 25, back in.
Another problem, in case this might help somebody, is that different email clients approach "security" differently. Thunderbird had said "Use TSL [encryption] if available" and so I checked TSL in KMail. Well, it ISN'T available. Thunderbird's failsafe approach made that a non-problem; KMail was an either/or.
To recap, with port 587 changed back again to port 25, and no encryption in place, I am able to use all three clients (though I normally only use one, like anybody who doesn't want to go completely crazy). |
|
|
|
Reviews:
 ·Charter
| reply to Rocky67
I too noticed smtpauth.sbcglobal.net:587 is not working.
I changed to smtp.**bell.yahoo.com and kept using port 587 and that works. So I'll still be able to send mail when on the road using another ISP (unless ISP's start blocking outgoing traffic on port 587), but I won't be able to hide some of my login headers anymore. 
--
Check out my website: www.renowirelessinfo.com |
|
Rocky67Pencil Neck GeekPremium
join:2005-01-13
Orange, CA Reviews:
·AT&T Yahoo
| reply to jonrkc
Good thinking, jonrkc. I didn't know that smtpauth.sbcglobal.net would work on anything but port 587. Thanks for the post.
Brian Grif_n - I didn't know that smtp.pacbell.yahoo.com could use anything but port 25, either. Thanks to you, too.
--
"The Internet? Is that still around?" - Homer |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| reply to jonrkc
said by jonrkc:To recap, with port 587 changed back again to port 25, and no encryption in place, I am able to use all three clients (though I normally only use one, like anybody who doesn't want to go completely crazy). Port 25 has always worked. Port 587 was an additional port, which will usually work when connecting from another network which blocks port 25.
RFC 2476 defines port 587 for "Message Submission", and should always be available as an alternate to port 25. Somebody at AT&T has screwed up.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| reply to Rocky67
said by Rocky67:Brian Grif_n - I didn't know that smtp.pacbell.yahoo.com could use anything but port 25, either. Thanks to you, too. Yahoo! has been adding port 587 access to all their servers. Recently, smtp.mail.yahoo.co.jp was added to the list of Yahoo! mail servers with port 587 access.
It is going to be necessary to use ports other than port 25 for SMTP server access as more ISPs start blocking port 25 outbound to off-network SMTP servers.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
jonrkcPremium
join:2003-05-19
Kansas City, MO
1 edit | What I don't understand is that, about two years ago--maybe a little more--SBC announced by email that most users would find port 25 blocked, but that if they requested it to be unblocked, SBC would do so. I did, and they unblocked it for me. Meantime I found out about using port 587 here in the forums, so I started using that (and telling friends to!). That worked up till yesterday. Now I'm back to port 25, and I don't understand why the change, and why it was not announced (at least by email).
What happens if AT&T blocks port 25 again? |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| said by jonrkc:What happens if AT&T blocks port 25 again? AT&T is still blocking outbound port 25 to off network SMTP servers. I have set up two recent installs, and worked with an older account; none of them have outbound port 25 access, except to AT&T SMTP servers. Those subs don't require off network SMTP access, though.
Also, 'smtpauth.sbcglobal.net', and 'smtp.*.yahoo.com' (where the '*' substitutes for your local AT&T email domain) have always been accessible through port 25.
Port 587 comes into play under RFC 2476, and is supposed to be the "Message Submission" port. Yahoo! has been adding port 587 access; they didn't always have it.
For AT&T to remove port 587 access to 'smtpauth.sbcglobal.net' is a step backward. Surely it is an error, and somebody needs to fix it.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| Just an update. Port 587 access to 'smtpauth.sbcglobal.net' is back. Apparently, they were moving equipment locations, and overlooked firewall permissions for port 587 during the reconfiguration.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
| Thanks for the update. |
|
Rocky67Pencil Neck GeekPremium
join:2005-01-13
Orange, CA | reply to NormanS
Thanks. |
|
