John Rudd writes:
There's also the fact that AFS cannot have a file hardlinked from different directories.
On the courier pages, it says that Courier wont work with AFS, but only mentions this in the context of the FIFO required for the mail queue's.
Is this the only restriction on using Courier with AFS? If I keep the
Also, there is no native Kerberos support, that's required by AFS.
I'm also curious if courier has SASL support, and if anyone has tried
SASL CRAM-MD5 and CRAM-SHA1 is implemented.
Related to that, sort of, is "if I use LDAP for the user information, can I still use PAM for the user authentication?" If I have to use LDAP authentication if I store the user info in LDAP, does it work via the LDAP bind (which can be made to work with kerberos), or does it work via storing a password string (encrypted or not) in the directory (this latter option being very bad ... enough so that I wouldn't use courier with LDAP if that's the only way to use LDAP with courier).Both. The latter is required for SASL CRAM-MD5 and SHA-1, since the laws of mathematics in this universe require access to the plaintext password, in order to calculate the HMAC keys.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
