Fixing SMTP errors from Yahoo!/AT&T/SBCGlobal DSL

This is really, really annoying. My parents have internet service provided via DSL from the convoluted company that is/was Yahoo!/AT&T/SBCGlobal. In the past, if I wanted to send email from my mail client while I was at home, I had to change my SMTP server to match AT&T's supported server and use my parents' account for password authentication. This is annoying enough. But recently, Yahoo!/AT&T/SBCGlobal has started requiring sender email registration to send e-mail from their already-locked down SMTP server (!). I returned home tonight and tried to send e-mail (after changing the SMTP server). threw an error, saying that my sender e-mail address wasn't accepted. Luckily, Adam Nash had written a post about this issue just a couple of weeks ago, linking to Yahoo's help page that tells you what you have to do, so I logged into my parents' Yahoo!/SBCGlobal mail account to add and verify my sender email addresses. This is the only way I can send mail via SMTP from my parents' place. Luckily, my parents don't use the email address that came with their DSL, so we can effectively use it just to manage a list of authenticated sender addresses for our home connection.

But let's say you have frequent visitors, all of whom use SMTP to send email from their laptops. In order to allow them to send mail via SMTP, you'd have to:

  1. give them your Yahoo!/AT&T account information for authentication
  2. add and verify their sender email addresses to your Yahoo! Mail account


I recommend boycotting DSL service from Yahoo/AT&T until they stop being so stupid. In fact, I had to order new DSL service yesterday, and this issue was the reason that I didn't even consider AT&T for my service.

Incidentally, I use a SMTP server on port 2525 that was set up for me by AustinDev, and AT&T DSL seems to let it through. has proxy servers that respond to any port, but for some reason, their server doesn't respond to 2525 when I try it from Too bad!

*UPDATE* - Chris says:

> Go here:

> From the drop down "*Abuse Type:" select "**Opt out port 25"

That looks promising!