Hello.
I'm getting `warning:xsasl_cyrus_server_get_mechanism_list: no
applicable SASL mechanisms' (/var/log/mail.log) and `fatal: no SASL
authentication mechanisms' (/var/log/mail.err) in Debian Squeeze.
Installed:
postfix: 2.7.1-1+squeeze1
libsasl2-2: 2.1.23.dfsg1-7
libsasl2-modules: 2.1.23.dfs
> Consider reading Postfix documentation.
> The error message is described there.
I haven't found it. Could you paste it?
> While the Postfix documentation Dr. Venema referred to has the necessary
> clues, you can find Debian-specific ones in the full Debian bug record
> and those clues may be mo
> The problem is a mis-match between smtpd_sasl_security_options
> (e.g., noplaintext) and the available server mechanisms (e.g.,
> plaintext only).
I've configured UNIX-domain socket communication, enabled SASL
authentication and authorization(0), but I'm still getting `fatal: no
SASL authenticat
> and for the above to /work/ dovecot needs to offer a non-plaintext
> mechanism, such as CRAM-MD5.
> I would strongly suggest removing the "noplaintext" keyword during
> testing.
Can it be used on a regular basis (i.e., not just for testing)? Will it be
better to enable a non-plaintext mechanism
> I would strongly suggest removing the "noplaintext" keyword during
> testing.
Thank you. It worked.
> There is no best, there is only what fits your needs. I expect it's
> common to specify
> smtpd_sasl_security_options = noanonymous
> smtpd_sasl_tls_security_options = noanonymous
> and then
