SMTP Auth fails with Postfix - no worthy mechs found
Dear list,
I've recently installed Suse 9.0, and I accepted the default MTA, postfix.
Only problem is that my smtp server won't auth with it - says a suitable
mechanism isn't found. I telnetted to my smtp server and found that PLAIN
is the only auth mechanism supported. I used yast to set up the outgoing
mail, and I enabled SMTP auth using their dialogs. I attach a tail of my
/var/log/mail file.
Any advice is appreciated.
Mike
Mar 23 21:31:28 linux postfix/cleanup[2318]: 5D986BA00: message-id=
The Wednesday 2004-03-24 at 06:54 -0500, mchardin wrote:
I've recently installed Suse 9.0, and I accepted the default MTA, postfix. Only problem is that my smtp server won't auth with it - says a suitable mechanism isn't found. I telnetted to my smtp server and found that PLAIN is the only auth mechanism supported.
I'm unsure if it applies to this case, but plain is the only method suse programs don't use (not supported), like imapd - unless you use an encripted transport. Otherwise, you have to configure /etc/postfix/sasl_passwd: foo.com username:password Also, in /etc/postfix/main.cf you have to enable client side sasl: smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd See /usr/share/doc/packages/postfix/README_FILES/SASL_README
I used yast to set up the outgoing mail, and I enabled SMTP auth using their dialogs. I attach a tail of my /var/log/mail file.
Any advice is appreciated.
Mike Mar 23 21:31:28 linux postfix/cleanup[2318]: 5D986BA00: message-id=
Mar 23 21:31:28 linux postfix/qmgr[2294]: 5D986BA00: from= , size=573, nrcpt=1 (queue active) Mar 23 21:31:28 linux postfix/qmgr[2294]: 5D986BA00: to= , relay=none, delay=1, status=deferred (deferred transport) Mar 23 21:32:22 linux postfix/sendmail[2325]: fatal: -qv is not implemented Mar 23 21:32:28 linux postfix/qmgr[2294]: 5D986BA00: from= , size=573, nrcpt=1 (queue active) Mar 23 21:32:28 linux postfix/qmgr[2294]: 817C3B431: from= , size=572, nrcpt=1 (queue active) Mar 23 21:32:28 linux postfix/smtp[2327]: warning: SASL authentication failure: No worthy mechs found Mar 23 21:32:28 linux postfix/smtp[2328]: warning: SASL authentication failure: No worthy mechs found Mar 23 21:32:28 linux postfix/smtp[2327]: 5D986BA00: to= , relay=smtp.mchardin.org[216.27.95.50], delay=61, status=deferred (Authentication failed: cannot SASL authenticate to server smtp.mchardin.org[216.27.95.50]: no mechanism available) Mar 23 21:32:28 linux postfix/smtp[2328]: 817C3B431: to= , relay=smtp.mchardin.org[216.27.95.50], delay=91168, status=deferred (Authentication failed: cannot SASL authenticate to server smtp.mchardin.org[216.27.95.50]: no mechanism available)
I guess you are a survivor - I was cr14 ;-) Knowing how "paranoic" is Lucent with security I'm surprised they only accept plain auth - but even so, a server should not request authorization for an address in his domain. That is, if you are trying to send email to an outside address through a server, that's relay, and needs authorization or direct rejection. But not if you are sending to an address in that domain, they should not. An idea: Add this to your /etc/postfix/main.cf file debug_peer_list = lucent.com And you will obtain more info about connections to them. You can increase verbosity changing the default: debug_peer_level = 2 -- Cheers, Carlos Robinson
participants (2)
-
Carlos E. R.
-
mchardin