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?
On 12/6/2012 4:54 AM, jug...@lavabit.com wrote:
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)?
Yes,
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 after
On 12/6/2012 9:54 PM, jug...@lavabit.com wrote:
common to specify
smtpd_sasl_security_options = noanonymous
smtpd_sasl_tls_security_options = noanonymous
and then after verifying that SASL works, adding
smtpd_tls_auth_only = yes
Does it mean that my session will be encrypted using TLS,
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
jug...@lavabit.com:
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
Am 05.12.2012 22:02, schrieb jug...@lavabit.com:
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
On Dec 5, 2012, at 2:02 PM, jug...@lavabit.com wrote:
Will it solve the problem if I switch to Dovecot SASL?
I've been using the Dovecot SASL option for several years on Debian Lenny and
Squeeze, largely because figuring out Cyrus looked like too much work, and it
was simple and quick to set
jug...@lavabit.com:
Consider reading Postfix documentation.
The error message is described there.
I haven't found it. Could you paste it?
Well there is at least one section that covers not found or
missing authentication mechanisms.
The problem is a mis-match between
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
On 12/5/2012 7:23 PM, jug...@lavabit.com wrote:
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),
11 matches
Mail list logo
