From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1L7HLm-0002Ko-Sm for garchives@archives.gentoo.org; Mon, 01 Dec 2008 22:34:43 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D60E2E0290; Mon, 1 Dec 2008 22:34:40 +0000 (UTC) Received: from yw-out-1718.google.com (yw-out-1718.google.com [74.125.46.152]) by pigeon.gentoo.org (Postfix) with ESMTP id AC12EE039F for ; Mon, 1 Dec 2008 22:34:40 +0000 (UTC) Received: by yw-out-1718.google.com with SMTP id 5so1171873ywm.46 for ; Mon, 01 Dec 2008 14:34:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=Bq4raw/PK5ZdQYSJFO1J2QiWwm3+80jCmbLmN/uNKgE=; b=aZ8OW77TtW+gO+sY6Xz9SJS9yBRMPgkJPXZ69g/PaH2W+/wUwkg3lRNjoP4lCVdbsk yNOkVzP916+VDOB4TyM7+pMcPrxt6YpWPFa+rV7qvge8y1qYid460lJZnawPcrWZvfVX zzs8I8lFD6EEdcC5ElufYTlrfOJ6tlOyBcFaw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=aFQnNHRA5YtTJwO7K0NssJseEq+OzOz7ORzSpzzgpahtFGzMo5MXfzS6Wmap1BeuH9 fCp18y7bjt1ENbCQC4ozEpOwU70PCnaBhtHqZW+vdVenOwZns+oWf9U8+d2sH9GEbeiL WnUIZosV0Vwg5aEBmB8kxZuDSFNslxUi4LMh0= Received: by 10.151.144.15 with SMTP id w15mr22638151ybn.6.1228170879413; Mon, 01 Dec 2008 14:34:39 -0800 (PST) Received: by 10.151.49.19 with HTTP; Mon, 1 Dec 2008 14:34:39 -0800 (PST) Message-ID: Date: Mon, 1 Dec 2008 17:34:39 -0500 From: "John Blinka" To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] ssmtp & at&t woes Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_84307_21426086.1228170879381" X-Archives-Salt: 3901c0cd-b555-4979-8169-674d1c9c6665 X-Archives-Hash: 3cfa0900393a07d2c853fd1cd4c34e06 ------=_Part_84307_21426086.1228170879381 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 ------=_Part_84307_21426086.1228170879381 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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
------=_Part_84307_21426086.1228170879381--