[KLUG Members] SASL

[Robert G. Brown]

>>I'm working on specifying a project that will entail users sending e-mail
>>to a server in another domain for distribution. I've read about SASL on
>>the sendmail.org site, and came to a page:
>>http://www.sendmail.org/~ca/email/mel/SASL_ClientRef.html
>>That lists SASL-compliant clients. When I go to those sites, I see little
>>or no mention of SASL support.
>What?  You want documentation? Ppfffffffhhhht.
Yes, sure. I also want World Peace, a yacht,a nd lots of tax-free income,
enough to finance a lot of research, a decent sized harem, and my own
really GOOD baseball team.

But I'm realistic about these things; they ain't happening, at least not all
of them, and not soon....

Actually, what I was looking for was some vague acknowledgment from the
MUA vendor[s] that this was the cleint end of SASL, and perhaps some way
of finding out just what the download and installation procedure was.

>Most clients list specific things like CRAM-MD5, etc.... under SMTP
>Authentication,  which means "I'd probably be happy with a MDA using 
>SASL on the backend".  For the most part the client doesn't much care
>how the MDA authenticates the SMTP stream,  so long as the mechanism is
>supported.
Well, the the MUA doesn't care, why should I? :)
My main job is to configure the MDA, and pass on the feasibility of dealing
with possible MUA's.

>>I did find this page:
>>http://www.eudora.com/techsupport/kb/1981hq.html
>>That talks about "SMTP Authentication" and it sounds VERY much like the
>>same thing. Is it?
>
>lnx01688:~ $ldd /usr/lib/sendmail
>        libdb-3.2.so => /lib/libdb-3.2.so (0x4002b000)
>        libresolv.so.2 => /lib/libresolv.so.2 (0x400d2000)
>        libcrypt.so.1 => /lib/libcrypt.so.1 (0x400e4000)
>        libnsl.so.1 => /lib/libnsl.so.1 (0x40111000)
>        libldap.so.2 => /usr/lib/libldap.so.2 (0x40128000)
>        liblber.so.2 => /usr/lib/liblber.so.2 (0x40152000)
>>>>>>>  libsasl.so.7 => /usr/lib/libsasl.so.7 (0x4015c000)  <<<<<<<<
>        libgdbm.so.2 => /usr/lib/libgdbm.so.2 (0x40167000)
>        libc.so.6 => /lib/libc.so.6 (0x4016e000)
>        libkrb5.so.3 => /usr/kerberos/lib/libkrb5.so.3 (0x402a4000)
>        libk5crypto.so.3 => /usr/kerberos/lib/libk5crypto.so.3 (0x402fc000)
>        libcom_err.so.3 => /usr/kerberos/lib/libcom_err.so.3 (0x4030e000)
>        libssl.so.2 => /lib/libssl.so.2 (0x40311000)
>        libcrypto.so.2 => /lib/libcrypto.so.2 (0x4033e000)
>        libdl.so.2 => /lib/libdl.so.2 (0x40401000)
>        libpam.so.0 => /lib/libpam.so.0 (0x40405000)
>        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
>It can be,  SMTP authentication methods are determined by the MDA which often
>can use SASL, a flat file, sometimes PAM (hence the linkage to libpam.so.0).
That's fine. I've come to understand that SASL itself is more of a framework 
than a specific authentication method.

							Regards,
							---> RGB <---