-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, September 20 at 09:51 PM, quoth Chris G: >Ah, sorry, I'm confused - I was confusing authentication with >encryption. My server requires my name and password but the >connection isn't encrypted.
Ohhhh, I get it. In that case, I know exactly why mutt requires SASL: because that's the library it uses to transform your username and password into a form that an SMTP server will accept, whether that be base64-encoding it, or whatever. SASL isn't a connection-encryption library (that would be something like gnutls or openssl), it's an authentication encoding library. SASL stands for "Simple Authentication and Security Layer." Thus, mutt doesn't have to implement LOGIN, PLAIN, SKEY, CRAM-MD5, or whatever else, but can rely on the SASL library to handle such details. A more complete explanation of the SASL concept is here: http://en.wikipedia.org/wiki/Simple_Authentication_and_Security_Layer ~Kyle - -- All men by nature desire to know. -- Aristotle -----BEGIN PGP SIGNATURE----- Comment: Thank you for using encryption! iD8DBQFG8ub/BkIOoMqOI14RAnFxAJ9YFEuvYShpUF0uuR+A53LS/gfb5QCfXypg AG3rVfQmJR9HPiuMpjWDBi4= =3NW3 -----END PGP SIGNATURE-----
