On Jan 14, 2013, at 5:09 PM, Patrick Ben Koetter <[email protected]> wrote:
>> >> Is there a rational explanation or do I just put it down to a ghost in the >> machine? > > I am confused too, because I had it first hand from Alexey Melnikov, who is > one of the main developers of Cyrus SASL, and he told me all saslauthd can > handle are plaintext mechanisms aka PLAIN and LOGIN. Greetings Ill try to shed a little light. postfix uses saslauthd to speak to your authentication mechanism . After the TLS encrypted session, the information sent via sasl needs to plain or login. It's as if you were typing in the password, instead sasl is doing it for you, so you do not enter the encrypted password, it's need to be something readable to be passed on to your system. Basically " don't double encrypt ". the mail client and postfix will encrypt the session. the info passed in between should be plain or login. hope this helps. -j
