From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ssmtp & at&t woes
Date: Wed, 3 Dec 2008 18:28:46 +0000 [thread overview]
Message-ID: <200812031829.21112.michaelkintzios@gmail.com> (raw)
In-Reply-To: <e6b926b90812011434n3cf6bd68yb8b819b62fcbf822@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]
On Monday 01 December 2008, 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
> root=xxx@att.net
> mailhub=smtp.att.yahoo.com:465
> AuthUser=xxx
> AuthPass=yyy
> rewriteDomain=att.net
> FromLineOverride=YES
> UseTLS=YES
>
> and my revaliases file looks like
>
> root=xxx@att.net:smtp.att.yahoo.com:465
>
> The result of the command mail -v -s test xxx@att.net 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 xxx@att.net 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
Have a go at adding:
UseSTARTTLS=YES
and remove:
UseTLS=YES
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-03 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 22:34 [gentoo-user] ssmtp & at&t woes John Blinka
2008-12-03 18:28 ` Mick [this message]
2008-12-04 12:11 ` John Blinka
[not found] <bEpAX-5D6-3@gated-at.bofh.it>
2008-12-04 20:33 ` ms
2008-12-04 22:03 ` Håkon Alstadheim
2008-12-05 3:12 ` John Blinka
2008-12-05 12:36 ` Stroller
2008-12-05 12:59 ` John Blinka
2008-12-04 22:26 ` John Blinka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200812031829.21112.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox