[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [OT] Sidux. SMTP wizards, help a Postfix noob?



s. keeling a écrit :
> s. keeling <keeling@nucleus.com>:
>>  mouss <mouss@ml.netoyen.net>:
>>>  smtp_generic_maps = hash:/etc/postfix/generic
>>>
>>> == generic:
>>>  keeling@newmil.nucleus.com	keeling@nucleus.com
> 
> More clues?  Again, this is Sidux on AMD64, HP Pavilion dv4.
> 
> Jan 19 18:33:35 newmil postfix/qmgr[12263]: 4EDADBC06: from=<keeling@newmil.nucleus.com>, size=671, nrcpt=1 (queue active)
> Jan 19 18:33:35 newmil postfix/smtp[14928]: warning: SASL authentication failure: No worthy mechs found
> Jan 19 18:33:35 newmil postfix/smtp[14928]: 4EDADBC06: to=<keeling@nucleus.com>, relay=smtp.nucleus.com[66.18.251.14]:25, delay=0.1, delays=0.02/0/0.08/0, dsn=4.7.0, status=deferred (SASL authentication failed; cannot authenticate to server smtp.nucleus.com[66.18.251.14]: no mechanism available)
> 

$ telnet smtp.nucleus.com 25
220 smtp.nucleus.com modusMail ESMTP Receiver
EHLO imlil.netoyen.net
250-nucleus.com
250-SIZE 20971520
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-X-IMS 5 -1
250-DSN
250-VRFY
250-AUTH LOGIN SCRAM-MD5 CRAM-MD5
250-AUTH=LOGIN
250 8BITMIME
quit
221 2.0.0 nucleus.com closing

so smtp.nucleus.com accepted LOGIN, CRAM-MD5 and SCRAM-MD5 (sigh, they
support the non standard "LOGIN" but not the standard "PLAIN"...)

Most probably, your postfix has the default:
smtp_sasl_security_options = noplaintext, noanonymous

which implies that postfix won't use cleartext passwords, thus no LOGIN
(nor PLAIN).

fortunately, "they" seem to accept STARTTLS. so enable TLS in the smtp
client:

smtp_tls_security_level = may

and try again. (plain text is ok under TLS).

if you can't get TLS to work, try

smtp_sasl_security_options = noanonymous

but this is not a very good idea, because your password will be sent in
the clear. (note that you need to have the cyrus-sasl
/usr/lib/sasl2/liblogin.* lib files).


PS. The postfix-users list is a better place for such questions.


Reply to: