smtp.att.yahoo.com and SSL

[System Administrator]

Outlook 2003 and 2007. My client uses AT&T for DSL Internet access
and a 3rd party for email. AT&T is constantly advising my client that
they need to switch to using SSL. I have already implemented the
settings per AT&T instructions for SMTP. POP3 remains pointed to 3rd
party server, port 110, and no SSL. Two 2003 users and one 2007 user
now have problems sending email. Only about one of five "send" cycles
completes without an error. The returned error message varies. The
messages stays in the Outbox and eventually does go out. What is
weird is that the 2007 user is set up to receive email from
pop.att.yahoo.com with SSL so as to be able to receive email from AT&T
regarding their account. Test messages sent from this account ALWAYS
send without error! It is only the account with the 3rd party POP3
configuration that has problems sending. The 2003 users also have 3rd
party POP3 and AT&T SMTP configured accounts. Any ideas? All users
are using Norton Internet Security Suite. Is this an Outlook issue?
Norton? AT&T? Thanks! P.S. The 2003 users are using Windows XP
Home SP2; the 2007 user is using Vista Home Premium.

 

[N. Miller]

Outlook 2003 and 2007. My client uses AT&T for DSL Internet access
and a 3rd party for email. AT&T is constantly advising my client that
they need to switch to using SSL. I have already implemented the
settings per AT&T instructions for SMTP. POP3 remains pointed to 3rd
party server, port 110, and no SSL. Two 2003 users and one 2007 user
now have problems sending email. Only about one of five "send" cycles
completes without an error. The returned error message varies. The
messages stays in the Outbox and eventually does go out. What is
weird is that the 2007 user is set up to receive email from
pop.att.yahoo.com with SSL so as to be able to receive email from AT&T
regarding their account. Test messages sent from this account ALWAYS
send without error! It is only the account with the 3rd party POP3
configuration that has problems sending. The 2003 users also have 3rd
party POP3 and AT&T SMTP configured accounts. Any ideas? All users
are using Norton Internet Security Suite. Is this an Outlook issue?
Norton? AT&T? Thanks! P.S. The 2003 users are using Windows XP
Home SP2; the 2007 user is using Vista Home Premium.

Yahoo! has changed the way that their SMTP message submission servers handle
outbound email. You must now match the "From:" email address to the account
login email address: I.e., if the user logs in with
'%User_ID-Foo%@sbcglobal.net', then the "From:" email address in the email
message must also be '%User_ID-Foo%@@sbcglobal.net'. The only exceptions are
email addresses configured through the verification process outlined here:

http://help.yahoo.com/l/us/yahoo/mail/original/manage/sendfrom-07.html

There can only be, at a maximum, 10 verified email addresses, in addition to
the login email address. This is a Yahoo! requirement, not an AT&T
requirement.

Because your client is using a third party email provider, he should use the
third party email SMTP message submission serves, as well. Then your client
will not be constrained by the Yahoo! rules.

 

[System Administrator]

Thank you for the detailed response. I did a Google search on the
issue yesterday and did not find any such information about the issue.

Unfortunately, the 3rd party email provider is incoming only - they do
not offer an SMTP server for use. The office only has four users, so
the link you provided may just work out for them.

However, how about this: Setting the Outlook accout email address to
the primary AT&T account address (the only one configured) and setting
the Outlook "Mail From" entry to their 3rd party email address. Would
that work as well?

Thanks.

 

[Brian Tillman]

Yahoo! has changed the way that their SMTP message submission servers
handle outbound email. You must now match the "From:" email address
to the account login email address: I.e., if the user logs in with
'%User_ID-Foo%@sbcglobal.net', then the "From:" email address in the
email message must also be '%User_ID-Foo%@@sbcglobal.net'. The only
exceptions are email addresses configured through the verification
process outlined here:

http://help.yahoo.com/l/us/yahoo/mail/original/manage/sendfrom-07.html

Um, no. I use nonsense sending addresses all the time through the
SBC-partnered Yahoo (i.e., my home address uses the sbcglobal.net domain).
ALl it requires is proper authentication to the servers. Yahoo doesn't care
at all about the sending address provided you've authenticated properly or,
at least, not for me.

 

[Brian Tillman]

Thank you for the detailed response. I did a Google search on the
issue yesterday and did not find any such information about the issue.

Unfortunately, the 3rd party email provider is incoming only - they do
not offer an SMTP server for use. The office only has four users, so
the link you provided may just work out for them.

However, how about this: Setting the Outlook accout email address to
the primary AT&T account address (the only one configured) and setting
the Outlook "Mail From" entry to their 3rd party email address. Would
that work as well?

If you have AT&T Yahoo and wish your messages to appear to come from, say,
(e-mail address removed), specify that address as the "E-mail Address" value in the
account. In the "User name" and "Password" fields, specify yout AT&T Yahoo
username and password ([email protected] or (e-mail address removed) or whatever
your credentials are). Specify everything else as is correct for the AT&T
Yahoo account (i.e., servers, ports and authentication settings for the
outgoing server).

 

[N. Miller]

Um, no. I use nonsense sending addresses all the time through the
SBC-partnered Yahoo (i.e., my home address uses the sbcglobal.net domain).
ALl it requires is proper authentication to the servers. Yahoo doesn't care
at all about the sending address provided you've authenticated properly or,
at least, not for me.

Been discussed to death in the DSLR forums:

http://www.dslreports.com/forum/remark,19985182?hilite=
http://www.dslreports.com/forum/remark,20299485?hilite=
http://www.dslreports.com/forum/remark,20442678?hilite=
http://www.dslreports.com/forum/remark,19985913?hilite=
http://www.dslreports.com/forum/remark,20274602?hilite=

You must not be using 'smtp.att.yahoo.com'?

| The message could not be sent because the server rejected the sender's e-mail address.
| The sender's e-mail address was '%User_ID%[email protected]'. Subject '[TEST] Doesn't work.',
| Account: 'Nobody',
| Server: 'smtp.att.yahoo.com',
| Protocol: SMTP, Server Response: '553 From: address not verified;
| see http://help.yahoo.com/l/us/yahoo/mail/original/manage/sendfrom-07.html',
| Port: 465,
| Secure(SSL): Yes,
| Server Error: 553,
| Error Number: 0x800CCC78

I can't send using a non-verified email address when logging in as
%User_ID%@pacbell.net' to 'smtp.att.yahoo.com' I get pointed to the link
that I posted.

 

[N. Miller]

On Tue, 6 May 2008 23:17:40 -0700, "N. Miller"

Thank you for the detailed response. I did a Google search on the
issue yesterday and did not find any such information about the issue.

Unfortunately, the 3rd party email provider is incoming only - they do
not offer an SMTP server for use. The office only has four users, so
the link you provided may just work out for them.

However, how about this: Setting the Outlook accout email address to
the primary AT&T account address (the only one configured) and setting
the Outlook "Mail From" entry to their 3rd party email address. Would
that work as well?

That would work, but it isn't as clean. The other option I would suggest is
trying one of the legacy SMTP AUTH servers. Using 'smtpauth.sbcglobal.net'
should work.

 

[System Administrator]

Thanks for the smtpauth.sbcglobal.net suggestion. The next time I'm
at the client I will make the change and see what happens. Guess
AT&T/Yahoo didn't think things through too well when they incorporated
the verified email requirement. Personal users are not greatly
affected, but business users are greatly affected.

 

[System Administrator]

That's how things are configured now, Brian, and the sending errors
are being generated, apparantly due to the need to have the "From"
email address be a verified address within the associated Yahoo
account. It seems like overkill to me to require both
registered/verified "From" addresses and the need to authenticate with
the smtp server in order to access the smtp server for sending.

 

[N. Miller]

Thanks for the smtpauth.sbcglobal.net suggestion. The next time I'm
at the client I will make the change and see what happens. Guess
AT&T/Yahoo didn't think things through too well when they incorporated
the verified email requirement. Personal users are not greatly
affected, but business users are greatly affected.

Yahoo! thought things through very well. They, not AT&T, run
'smtp.att.yahoo.com'. They don't want any but low volume residential
accounts using their servers.

What AT&T now needs to do is re-think their agreement with Yahoo! I would be
all for AT&T pulling the plug on the agreement next time it comes up for
negotiation.

 

[System Administrator]

I agree. Thanks, again, for the smtpauth pointer.