I'm trying to make Cyrus IMAP work with Pam for authentication. I'm doing this because I'm trying to simplify things for account management for my client. Unfortunately, it's not going well. I have read the fine manual and I've searched the fine Web as well as the archives of this mailing list but I have yet to find an answer that works.
I'm using the latest imap and sasl2 as of last Thursday. my current IMAP configuration file looks like: configdirectory: /var/spool/imap-config partition-default: /var/spool/imap admins: root cyrus srvtab:/var/spool/imap-config/srvtab allowplaintext: yes sasl_pwcheck_method: saslauthd I've used pam and shadow in addition to saslauthd but so far it keeps going back to its own little database and telling me to go away. Now, I'm getting to the point where I'm thinking I'm really barking up the wrong tree. My suspicion is that I should just train my customer to use a a separate user database for mailbox accounts from his password file entries. This shouldn't be a problem because the box is a sealed box (more or less). One of the problems is ease of management. He has no problem using a shell for bulk processes but really wants to fall back on to a web based interface for account management. Are there any such tools like a plug-in for webmin? My second major question is on how to make Cyrus play nice with Spamassassin. Normally I just use procmail as my local delivery agent and use a global rules set to tag and filter spam. How does one do that with Cyrus requiring an lmtp interface? many thanks in advance ---eric