Email has had to evolve over the years. What worked 5 years ago
may not work today. AT&T/Yahoo has been shifting over to newer
servers that require SSL and high-numbered ports (465/995).
They are not alone. Comcast has gradually been dropping all support
for port 25 SMTP. These changes in email standards are being
mandated by the newer RFCs and the ever increasing onslaught of
spammers and phishers.
I suggested a test with OE only for the purpose of trying to narrow
down where the problem is, server-side or client-side. Until you
know for sure, you'd be stabbing in the dark.
Incidentally, I come from the sbcglobal.net side of AT&T's house,
and am very familiar with the recent changes.
Gary VanderMolen, MS-MVP (Mail)
--------------------------------------------------
I can certainly appreciate your focus. But, perhaps, somehow you are not seeing the grief many of us "new2ATT.net" folks now see
now that ATT seems to use Yahoo as their "mail service provider."
Yes, I do understand a trial of OE. It is part of XP. I fully expect it to work perfectly; just because it is a MS product. No
different than using some flavor of Outlook which ATT fully supports and has told me to use. I suppose that since I only spend
~$1020/yr for ATT's 2-wire CU services for phone and dsl, I do not have much of a voice. Fair call.
Additionally, after some 7 hours on the Mozilla/ThunderBird forums (thanks Neil!), I find that this recent ATT change of "mail
service provider" has caused the same troubles with users of PACBELL.net, SBCglobal.net, and, now with BellSouth.net (me). The
consensus within the TBird community is that ATT has REQUIRED new POP and SMTP settings that for some reason ATT servers do not
play nice with (yet?). Like the SSL business. I have some workarounds. For the most part, I am now working. All I need to fix
now is sending attachments outbound. This could be my ESET A/V, and, I know how to test this; but, I still have more study to
do.
