Koozali.org: home of the SME Server

Can not authenicate with ISP's SMTP server

Offline garyb43

  • 3
  • +0/-0
Can not authenicate with ISP's SMTP server
« on: September 07, 2008, 08:39:07 PM »
This particular issue is with 7.3 and the latest revisions via yum update.  I am trying to send email via ISP's server.  I have reviewed bug# 897 and applied that advice.  I am receiving 535 Authentication failure from ISP's server.  I can successfully send mail directly from Thunderbird to the same server on port 465 using the same userid/password that I have entered via the server-manager to e-mail settings.
 
Here is a piece of my smtp-auth-proxy log with debug enabled:

2008-09-07 12:02:57.104746500 Net::SMTP::SSL>>> Net::SMTP::SSL(1.01)
2008-09-07 12:02:57.104756500 Net::SMTP::SSL>>>   IO::Socket::SSL(1.07)
2008-09-07 12:02:57.104761500 Net::SMTP::SSL>>>     IO::Socket::INET(1.27)
2008-09-07 12:02:57.104767500 Net::SMTP::SSL>>>       IO::Socket(1.28)
2008-09-07 12:02:57.104772500 Net::SMTP::SSL>>>         IO::Handle(1.24)
2008-09-07 12:02:57.104777500 Net::SMTP::SSL>>>           Exporter(5.58)
2008-09-07 12:02:57.104782500 Net::SMTP::SSL>>>   Net::Cmd(2.26)
2008-09-07 12:02:57.118666500 Net::SMTP::SSL=GLOB(0x9002228)<<< 220 isp.att.net- Maillennium ESMTP/MULTIBOX/TLS frfwmhc01 #2
2008-09-07 12:02:57.118708500 Net::SMTP::SSL=GLOB(0x9002228)>>> EHLO pylon2.xmlprogress.com
2008-09-07 12:02:57.207714500 Net::SMTP::SSL=GLOB(0x9002228)<<< 250-isp.att.net
2008-09-07 12:02:57.207723500 Net::SMTP::SSL=GLOB(0x9002228)<<< 250-7BIT
2008-09-07 12:02:57.207729500 Net::SMTP::SSL=GLOB(0x9002228)<<< 250-8BITMIME
2008-09-07 12:02:57.207734500 Net::SMTP::SSL=GLOB(0x9002228)<<< 250-AUTH ANONYMOUS CRAM-MD5 LOGIN NTLM PLAIN
2008-09-07 12:02:57.207741500 Net::SMTP::SSL=GLOB(0x9002228)<<< 250-DSN
2008-09-07 12:02:57.207746500 Net::SMTP::SSL=GLOB(0x9002228)<<< 250-HELP
2008-09-07 12:02:57.207751500 Net::SMTP::SSL=GLOB(0x9002228)<<< 250-NOOP
2008-09-07 12:02:57.207812500 Net::SMTP::SSL=GLOB(0x9002228)<<< 250-PIPELINING
2008-09-07 12:02:57.212722500 Net::SMTP::SSL=GLOB(0x9002228)<<< 250-SIZE 26214400
2008-09-07 12:02:57.212732500 Net::SMTP::SSL=GLOB(0x9002228)<<< 250-STARTTLS
2008-09-07 12:02:57.212737500 Net::SMTP::SSL=GLOB(0x9002228)<<< 250-VERS V05.21c++
2008-09-07 12:02:57.212743500 Net::SMTP::SSL=GLOB(0x9002228)<<< 250 XMVP 2
2008-09-07 12:02:57.296280500 Net::SMTP::SSL=GLOB(0x9002228)>>> AUTH CRAM-MD5
2008-09-07 12:02:57.377277500 Net::SMTP::SSL=GLOB(0x9002228)<<< 334 PDMwMzQuMTIyMDgwMzM3NkBpc3AuYXR0Lm5ldD4=
2008-09-07 12:02:57.379530500 Net::SMTP::SSL=GLOB(0x9002228)>>> Z2FyeWI0M0BhdHQubmV0IGYyOGM2NGI0ZDkzOGRjMmIxZTkzZmVhMDIyZGEzMGJj
2008-09-07 12:02:57.464683500 Net::SMTP::SSL=GLOB(0x9002228)<<< 535 Authentication failure
2008-09-07 12:02:57.464693500 SMTP authentication with ISP server failed
2008-09-07 12:02:57.466431500 Net::SMTP::SSL=GLOB(0x9002228)>>> QUIT
2008-09-07 12:02:57.547674500 Net::SMTP::SSL=GLOB(0x9002228)<<< 221 isp.att.net

/\/\/\/\/\/

I have searched the forums and bug tracker.  I did find some old reference to SMEServer does not do CRAM-MD5, but that was in 2006.  What am I overlooking and/or doing wrong?

SMEServer is a great distro.  I have used if for years at multiple sites.  I have always been able to figure things out from the either the docs, the code or consulting the info/advice from the wonderful community at contribs.org. 

But, now I am stuck.  Help most appreciated.  Thanks.
 

Offline pfloor

  • *****
  • 889
  • +1/-0
Re: Can not authenicate with ISP's SMTP server
« Reply #1 on: September 07, 2008, 10:05:46 PM »
Are you sure you have your settings correct?

2008-09-07 12:02:57.207734500 Net::SMTP::SSL=GLOB(0x9002228)<<< 250-AUTH ANONYMOUS CRAM-MD5 LOGIN NTLM PLAIN

This looks wrong, as if you are trying to log in anonymously.  Show the output of:

config show smtp-auth-proxy

and

config show SMTPSmartHost

Note: "*****" out your username and password.
In life, you must either "Push, Pull or Get out of the way!"

Offline garyb43

  • 3
  • +0/-0
Re: Can not authenicate with ISP's SMTP server
« Reply #2 on: September 07, 2008, 10:38:07 PM »
Thanks for your prompt response.

Here is what those settings look like ...

[root@pylon2 log]# config show SMTPSmartHost
SMTPSmartHost=fmailhost.isp.att.net

[root@pylon2 log]# config show smtp-auth-proxy
smtp-auth-proxy=service
   Debug=enabled
   Passwd=*********
   PeerPort=465
   Userid=***************
   status=enabled


Thanks for reviewing it.

Offline pfloor

  • *****
  • 889
  • +1/-0
Re: Can not authenicate with ISP's SMTP server
« Reply #3 on: September 08, 2008, 05:45:12 AM »
2008-09-07 12:02:57.207734500 Net::SMTP::SSL=GLOB(0x9002228)<<< 250-AUTH ANONYMOUS CRAM-MD5 LOGIN NTLM PLAIN

This looks wrong, as if you are trying to log in anonymously.

I'm sorry, I misspoke here.  That is the remote mail server asking SME for your login information/type.  Your server responds back with:

2008-09-07 12:02:57.296280500 Net::SMTP::SSL=GLOB(0x9002228)>>> AUTH CRAM-MD5

It looks like SME supports CRAM-MD5 but for some reason the remote server is rejecting your login.

You should open a bug and report this.



In life, you must either "Push, Pull or Get out of the way!"

Offline cactus

  • *
  • 4,880
  • +3/-0
    • http://www.snetram.nl
Re: Can not authenicate with ISP's SMTP server
« Reply #4 on: September 08, 2008, 10:13:11 AM »
You should open a bug and report this.
After you have done so, please post the url to the bug here for future reference.
Be careful whose advice you buy, but be patient with those who supply it. Advice is a form of nostalgia, dispensing it is a way of fishing the past from the disposal, wiping it off, painting over the ugly parts and recycling it for more than its worth ~ Baz Luhrmann - Everybody's Free (To Wear Sunscreen)

Offline garyb43

  • 3
  • +0/-0
Re: Can not authenicate with ISP's SMTP server
« Reply #5 on: September 09, 2008, 06:05:17 AM »
Bug reported: 09/08/2008.  See:

http://bugs.contribs.org/show_bug.cgi?id=4544

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: Can not authenicate with ISP's SMTP server
« Reply #6 on: October 25, 2008, 04:14:00 AM »
Bug reported: 09/08/2008.  See:

http://bugs.contribs.org/show_bug.cgi?id=4544

The problem is clearly with att.net's mail server. It advertises that it is capable of CRAM::MD5, but it lies. Others have discovered this as well:

http://community.pmail.com/forums/thread/12510.aspx