John Blinka wrote:
I recently switched to at&t from another isp. At that other isp,
my ssmtp setup worked perfectly. With at&t, a similar ssmtp setup
(modified appropriately to point to at&t's smtp server) does not
work at all.
AT&T told me to use the server smtp.att.yahoo.com and port
465. So my ssmtp.conf file looks like:
Debug=YES
[EMAIL PROTECTED]
mailhub=smtp.att.yahoo.com:465
AuthUser=xxx
AuthPass=yyy
rewriteDomain=att.net
FromLineOverride=YES
UseTLS=YES
and my revaliases file looks like
[EMAIL PROTECTED]:smtp.att.yahoo.com:465
The result of the command mail -v -s test [EMAIL PROTECTED] is:
[<-] 220 smtp122.sbc.mail.sp1.yahoo.com ESMTP
[->] EHLO tobey
[<-] 250 8BITMIME
[->] AUTH LOGIN
[<-] 334 VXNlcm5hbWU6
[->] am9obi5ibGlua2E=
[<-] 334 UGFzc3dvcmQ6
[<-] 535 authorization failed (#5.7.0)
send-mail: Authorization failed (535 authorization failed (#5.7.0))
Can't send mail: sendmail process failed with error code 1
I read somewhere that some people can't get at&t's port 465 to work
with ssmtp and that they have used port 587 successfully. Not so
for me. Using port 587 (replacing 465 by 587 in ssmtp.conf and revaliases),
the result of mail -v -s test [EMAIL PROTECTED] is:
SSL_connect: Success
send-mail: Cannot open smtp.att.yahoo.com:587
Can't send mail: sendmail process failed with error code 1
I have no problem at all sending mail to my att.net account from
various gmail accounts I use, so I know that my password and
username combination functions.
I can telnet to smtp.att.yahoo.com at either port 465 or 587 and get
a response, so nothing is blocking either port.
Any insights or suggestions?
John Blinka
Hi John,
I suppose you use a wrong username. According to
http://helpme.att.net/article.php?item=287 you have to use the full mail
address. Otherwise check your password for correctness.
Another problem might be the line in your revaliases file. The separator
between the columns is a colon not equals (right after the 'root'). If
you don't send mail to other people from your root account you do not
need that line anyway.
ms
