said by eak :

change outgoing smtp to: smtpauth.sbcglobal.net port 25, no SSL

After tons of problems, no more

said by eak :

change outgoing smtp to: smtpauth.sbcglobal.net port 25, no SSL

After tons of problems, no more

said by Fixed it :

I wanted to offer another maybe-solution for the people having trouble sending mail. I'm using Mail in OSX and for the past few months have to hit send over and over about ten times before an email will go out, and I think I found the solution this morning. I have AT&T DSL with an sbcglobal.net account, so I made my outgoing server this: plus.smtp.mail.yahoo.com -- and now it works. I hope it works for you, too.

said by d_l :

Have you tried smtpauth.sbcglobal.net, port 25, "secure connection: No", and your email address with domain, e.g. ****@snet.net for user name portion of the user name/password?

said by nwrickert :

You should be able to use smtpauth.sbcglobal.net. You will have to setup smtp authentication in your client. I don't think SSL is supported, but port 25 and port 587 should both work.

said by mebe :

If you have authenticated and you are still getting 553 errors then you most likely did not authenticate at the right mail site - be aware that all of the Yahoo! and white label Yahoo offshoots LOOK exactly the same - the only difference is the URL. At least that was my solution. I started getting these messages almost three months ago. Since then I have been tearing my hair out because the solution that everyone else was using wasn't working for me. I even tried different email clients thinking it was because I was using Mac Eudora.

And no, it was that originally I saw the yahoo.com message explaining what to do...so I went to my YIM (Yahoo!) mail account, signed in with my yahoo email address and password and filled out all the other domains I needed. Problem solved right? No.

Today, I saw a reference to the fact that it's most likely your DSL server that needs to have the authentication. Doh. So, I typed in att.yahoo.com, signed in with my sbcglobal.net email address and going to the mail screen - up pops an entirely DIFFERENT ui that looks exactly the same as my Yahoo! Mail interface but it says - ATT Yahoo! on the banner. And no emails in that account. Authenticated and problem solved.

said by robinth :

BUT, if the "from" address is not in the ATT domain hierarchy (ameritech, sbcglobal, etc.) the message is sent normally.

said by dvldog11 :

That worked after hours of work.

Instead of smtp.att.yahoo.com

Change it to: smtp.mail.yahoo.com

Keep port 465 and SSl.

Worked like a charm first time.

said by dvldog11 :

That worked after hours of work.

Instead of smtp.att.yahoo.com

Change it to: smtp.mail.yahoo.com

Keep port 465 and SSl.

Worked like a charm first time.

fewwwwwwwwwwwwwwwww Thanks guys!!!

said by robinth :

BUT, if the "from" address is not in the ATT domain hierarchy (ameritech, sbcglobal, etc.) the message is sent normally.

If a non-matching ATT Yahoo "from" address hits the ATT Yahoo SMTP server, it is bounced with the error message that was posted. BUT, if the "from" address is not in the ATT domain hierarchy (ameritech, sbcglobal, etc.) the message is sent normally.

said by lev :

Yesterday, the smtp.att.yahoo.com servers began enforcing that the authenticated SMTP sender must match the PRECISE sub-account account that you're trying to send with.

said by MagMan :

Ok folks success I finally have mine working again per the instructions.So you can call me stupid I deserve it.I was messing with everything but what I should have been messing with.Go ahead slap me upside the head.

Thanks Lev for all your help and you to Radio Doc sorry if I was a little testy at times but it was becoming very frustrating.

said by nwrickert :

Glad you got it working.

said by lev :

Look Magman, there are two issues at hand.

First is the fact that AT&T/Yahoo's implemented this. I don't think we're going to be able to change that, at least in the short term.

Second... it's working as they intended, and you're using a mail client for which they don't provide technical support. So opening support tickets is just a waste of your time.

People here, including myself, have told you how to fix it. As far as AT&T would be concerned, the problem is on your end... and technically, they're right. If you want things to work in the forseeable future, you'll either need to figure out how to do this yourself, find someone nearby willing to come over and do it for you, or follow my suggestion of putting VNC on your computer and letting someone who knows how to fix it log on and do so.

This is a 2 minute fix. The e-mail address for each account must be used to authenticate outbound mail for that account.

I know you're frustrated, and whether or not AT&T/Yahoo should have done this (for the record, they shouldn't) we're trying to fix YOUR problem here. Don't get sidetracked.

said by rjfortyfive :

So you are saying that you can not authenticate other multiple non sbc accounts with only one sbc account? You can not enter the same email address and password to SMTP authenticate multiple non sbc account anymore? in case I was not clear. If that is the case what kind of BS is this?

said by lev :

Thunderbird will try to use a single SMTP server for all your mail. If you're authenticating SMTP for account1@sbcglobal.net with account2@sbcglobal.net, it won't work anymore.

said by nwrickert :

I use webmail, so not affected.

However, when configuring thunderbird (the account settings), there should be an "advanced" button where you can specify multiple SMTP server definitions. Then you can select which applies to a particular account.

said by lev :

Thunderbird will try to use a single SMTP server for all your mail. If you're authenticating SMTP for account1@sbcglobal.net with account2@sbcglobal.net, it won't work anymore.

said by lev :

After a couple of calls with my ex-girlfriend and this morning, I can tell you the solution.

Yesterday, the smtp.att.yahoo.com servers began enforcing that the authenticated SMTP sender must match the PRECISE sub-account account that you're trying to send with.

This is the probable final result of »Strange SMTP problems. rearing its head.