Even when it connects and says "delivered" I find out that in some
cases the recipients didn't receive our outgoing mail.
Anyone else have troubles like this lately? (more than usual, that
is...)
Dave B.
I haven't seen any complaints of lost outgoing email, but we don't use
that SMTP server much.
The new and improved incantation is:
smtp.att.yahoo.com
with SSL authentication on port 465. The POP3 server has also
changed. See:
<http://www.dslreports.com/faq/5535?r=87>
At this time, the old and the servers are the same, but you might want
to make these changes before AT&T makes them manditory.
--
Jeff Liebermann je...@cruzio.com
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
I've noticed a series of failures in the last two days as well, but
for incoming mail where the connection to the POP server fails, is
never established, or where authentication fails. The problem was
intermittent. It is possible(i.e, conceivable but dependent on what
mail client you use) that your mail client doesn't report failures
when it is polling the server periodically for new mail.
I didn't send enough outgoing mail to notice a problem for that.
SBC is doing very well at delivering spam, however, :-(
--
My real name backwards: nemuaZ lliB
Yes same here. I noticed a problem with mail.sbcglobal.net.
So I tried to upgrade to the new att SMTP server, with compulsory ssl,
and that failed also. I then called up tehir tech support, and he said
the new att smtp servers were not quite up to speed yet, and had be
revert to the old server, but recommended to my surprise that I unchek
authentication!
It's working again now at least...
Amazing. They're the same exact server:
06/09/07 16:05:40 dns smtp.sbcglobal.yahoo.com
Canonical name: smtp.sbc.mail.yahoo4.akadns.net
Aliases:
smtp.sbcglobal.yahoo.com
smtp-sbc.mail.yahoo.com
Addresses:
69.147.64.31
06/09/07 16:06:27 dns smtp.att.yahoo.com
Canonical name: smtp.sbc.mail.yahoo4.akadns.net
Aliases:
smtp.att.yahoo.com
smtp-sbc.mail.yahoo.com
Addresses:
69.147.64.31
The IP I see mapping for mail.sbcglobal.net, which is the one the tech
support recommended I revert to is 207.115.36.24
Different old and very-old servers. I sometimes use:
06/09/07 16:31:49 dns mail.pacbell.net
Canonical name: mail.pacbell.net
Addresses:
207.115.36.24
06/09/07 16:37:02 dns smtp.sbcglobal.net
Canonical name: smtp.prodigy.net
Aliases:
smtp.sbcglobal.net
smtp.pi.sbcglobal.net
Addresses:
207.115.20.26
06/09/07 16:33:34 dns postoffice.pacbell.net
Canonical name: postoffice.pacbell.net
Addresses:
207.115.20.107
These are all the old PBI/Prodigy/SBC managed servers. When SBC
started outsourcing their email to Yahoo, the new servers were
initially:
mail.sbcglobal.yahoo.com
pop.sbcglobal.yahoo.com
When SBC bought AT&T and renamed themselves Ma Bell, it became:
mail.att.yahoo.com
pop.att.yahoo.com
which are currently just new names for the previous sbglobal Yahoo
servers, with the added bonus of SSL authentication in both
directions.
It's interesting that support should recommend the old
mail.pacbell.net server as, unless something has changed, methinks
it's the oldest and flakiest of the bunch.
06/09/07 16:41:08 dns 207.115.36.24
nslookup 207.115.36.24
Canonical name: nb-smtp-vip1.prodigy.net
Addresses:
207.115.36.24
Which gives me
24.36.115.207.in-addr.arpa name = nb-smtp-vip1.prodigy.net
Which then doesn't resolve, ebenn when querying via their
own name server:
Good job.
Makes you miss AOL.
--
Microsoft Windows XP, the official operating system of Al Qaeda