robinth
join:2003-01-09
Chicago, IL
| reply to lev
Re: (Problem) Sending Mail
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. There are some interesting little oddities in the way this has been implemented. 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.
Perhaps they will catch on to this eventually. I use a personal domain email address as a from, and I haven't had any problem so far, but will apparently have to make some adjustments if the ATT SMTP servers are further restricted. |
|
nwrickert
sand groper
Premium,MVM
join:2004-09-04
Geneva, IL
 ·AT&T U-Verse
 ·AT&T Midwest
| 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. This disparity is likely intentional.
I am guessing that the aim is to extend their use of Domain Keys header signatures, to authenticate senders. They had been previously doing this for yahoo senders, and these changes will allow them to do it for sbcglobal, etc, senders. They can't authenticate foreign domains over which they have no control, so they don't bother to try and instead omit the domain keys signature in that case.
--
AT&T dsl; Westell 327w modem/router; SuSE 10.1; firefox 2.0.0.12 |
|
Somarius
join:2008-03-19
| Error 553
Recently Yahoo found a Security Hole on their servers
Message says:
*******************************************************************************************
The message could not be sent because the server rejected the sender's e-mail address. The sender's e-mail address was ***********. Subject 'letter', Account: 'pop.att.yahoo.com', Server: 'smtp.att.yahoo.com', Protocol: SMTP, Server Response: '553 From: address not verified
»help.yahoo.com/l/us/yahoo/edit/a···dex.html,
Port: 25, Secure(SSL): No, Server Error: 553, Error Number: 0x800CCC78
*******************************************************************************************
How To Fix this?..
You need to verify your email address to be able to send out mails, and yahoo is no using port 25 is using port 465 through a SSL connection.. so if u have an ATT account.. your outgoing should be smtp.att.yahoo.com
ok, now you need to sign in on webmail, go to "Mail Options", Then go to Account, Click on "add or edit an account", then click on "Add",
and you'll have:
*Step 1: Enter Account Name
Please enter a name for this account. This name will only be used for display purposes.
Just type "Test", you need it just to send the verification mail, Continue
*Step 2: Enter Email Address
Name: just type your name here --------------
Email: ***type an alternate email to be able to receive the verification code,***---
Continue.
*Step 3 Setup Mail Server
You need to SKIP this step
*last step will send the verification email
ok, now sign in on your alternate email open yahoo message
, copy the verification code, lick on yahoo link, paste and verify, that basically it, worked for me.
Hopefully will work for y'all
like i said its a Yahoo security hole, not AT&T Issue, sad thing is , there is no ETR, as far as i know, yahoo is working on it. im gonna try and digg for a ETR.
If this doesn't work contact yahoo 1-408-349-1472
its either Free or fee Based
Good luck |
|
myrddin97
join:2004-09-28
Edwardsville, IL
| reply to MagMan
Re: (Problem) Sending Mail... and the solution
A couple of our clients have been having similar issues sending mail since last week. Today, we were able to get the following information from ATT as a backup until the normal smtp.att.yahoo.com port 465 SSL connection works again. Sorry if it's already been posted, but I wasn't able to find this in my earlier searches.
Outgoing server: smtpauth.sbcglobal.net
Outgoing server port: 25 does not require SSL secured connection
Outgoing server requires authentication
Log on using *@sbcglobal.net (*@att.net) with password |
|
RadioDoc
58ef2c0
Premium,ExMod 2000-03
join:2000-05-11
·AT&T Midwest
| reply to robinth
Re: (Problem) Sending Mail
said by robinth :BUT, if the "from" address is not in the ATT domain hierarchy (ameritech, sbcglobal, etc.) the message is sent normally. That has not been my experience. All email sent from my domain via ATTYahoo! servers (smtp.att.yahoo.com) was rejected. I have to use my webhost's SMTP to send business email.
--
Toolmaster of La Grange. |
|
JTBidder
@pacbell.net | reply to Somarius
Thank you. Your steps for setting up alternate email addresses through the yahoo mail site did the trick. I can send emails again!!! |
|
WaukMan
Premium
join:2004-01-01
Waukesha, WI
·AT&T Midwest
| reply to Somarius
I too have been hit by this (or I should say my wife was). I ran through the steps and it did seem to resolve the problem. Not sure how exactly but it seems clear that the yahoo smtp server is not only validating the username and password used to login to the smtp server but it wants the from address to be a 'valid' address for the account. Seems overkill to me. |
|
jsinaiko
Premium
join:2001-04-25
Chicago, IL
·AT&T Midwest
| Didn't you hear the recording while on hold for 45 minutes?
IT'S FOR YOUR PROTECTION! So quit yer yapping or Ma Bell will show up at your house with a nuke to protect you even more!
Seriously, overkill seems an appropriate way to put it. but I also suspect that the implementation was botched too. Why didn't they send out an email to everyone? Why is the verification area of the webmail options interface so deep in the system and hard to find?
It's all well and good to try and tighten up the network, but it often helps if one bothers to inform the end users. 
--
Illegitimati non carborundum
|
|
chidmf
join:2003-12-05
Chicago, IL
| reply to lev
Re: (Problem) Sending Mail... and the solution
I've DONE the verifications of email addresses and ...
IT DOES NOT SOLVE THE PROBLEM.
SMTP has been degrading over the last month or so - it was working fine, usually, and failing (with the same message others are posting about) only once in a while. Nothing a little 'retry later' wouldn't fix.
TODAY-- NOTHING! I have not been able to send anything using SMTP settings that were working fine a few days ago.
WTF? |
|
Steve McGarrett
@sbcglobal.net
| reply to MagMan
Easy solution: replace att with mail in server name, thus:
smtp.mail.yahoo.com
Don't change anything else. Works fine with port 465, swbell.net, sbcglobal.net, att.com, etc. accounts.
AT&T uses akamai to load balance smtp.att.yahoo.com. Some physical machines started having this problem last week, others were OK. By this morning, all machines seemed to have this problem. By this evening, some machines have had the problem fixed, others not. Meantime, smtp.mail.yahoo.com has worked fine all day.
And, no, AT&T doesn't do anything for *OUR* protection, it is for AT&T's protection^H^H^H^H^H^H^Hfit.
Aloha,
McGarrett |
|
MagMan
Life is simpler when you tell the truth.
Premium
join:2003-10-01
Westlake, OH
·AT&T Midwest
·AT&T Midwest
| reply to MagMan
This is all bull crap from the get go!!!!!
I have e-mails showing up now in my in box that are old already read and deleted WTF is up that?
--
"The truth is incontrovertible, malice may attack it, ignorance may deride it, but in the end; there it is." |
|
wptski
join:2001-01-20
Warren, MI | reply to Steve McGarrett
With that change I couldn't even send mail to myself! |
|
dvldog11
@sbcglobal.net |  reply to Steve McGarrett
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!!! |
|
johnz
@ameritech.net | I also was having problems the last few days. Even tonight it didn't work. Changed "att" to "mail" and it went right through. Thanks everyone
John |
|
OldEE
Premium
join:2002-08-25
Westerville, OH
| reply to dvldog11
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!!!
Ditto. Phew, that was easy! 
Chuck |
|
parnass
join:2008-04-07
Oswego, IL
1 edit |  reply to dvldog11
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.
That trick worked for me all last week, but it stopped working this morning. Perhaps Yahoo/AT&T updated the smtp.mail.yahoo.com server last night.
(I tried to post earlier, but my account was marked inactive so I had to reregister which took a little extra time.) |
|
wrc2376
join:2000-12-28
Hinsdale, IL
| I have read this post several times and thought I had my 553 problem fixed. However, that does not seem to be the case. I use my own domain email and have smtp set for smtp.att.yahoo.com. The only way I can get it to work is by changing smtp to smtp.mail.yahoo.com. My question is have I missed something because I have added and verified the domain account but still get the 553 error unless I use the alternate smtp setting? Being the account is verified shouldn't I be able to use smtp.att.yahoo.com? |
|
mebe
@sbcglobal.net
| 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.
So, make sure that you're logging in to the right mail account to authenticate. It needs to be the account your DSL runs off of not your YIM or other accounts. It's very easy to miss...I'm an IT person who has been all over the web trying to figure it out. Very happy to see it leave after 2 1/2 months! Fascinating how poor the instructions are at solving this issue that affects so many people. |
|
dvldog11
@sbcglobal.net
| reply to parnass
Same here... This worked for a week and now I'm back to getting the 553 error. AT&T/Yahoo sucks I've determined. I tried the tricks listed through yahoo webmail, but I already have an account setup and it won't let me send a verification out.
I'm wondering if I should delete the account and re-add it.
Anyone else find a work around? |
|
Joony
join:2001-12-08
Skokie, IL
| reply to MagMan
After having some frustrating non working SMTP server issues, I finally came here to look up what was wrong.
All I did was change my sbcglobal SMTP server to the new attyahoo one, and logged into account management and added both my gmail and school mail, changed the port from Apple Mail, and wala, I could send mail again!
Woooo. |
|
