Thanks Gordon, unfortunately this is not quite going to work for me. My user database is in LDAP, and the user's home directory, windows profiles, and mail directories are all on different filesystems. The profiles are separate because they tend to grow out of control, the home directory is used here as a backup/storage/scratch pad, and the mail directories (averaging 200Mb each) are split for easy backup.
I think you're looking at the problem with too rigid a view. If I follow you, your users' home directories are in /home and their mailboxes are in /ticoon/mail. The home directory is probably listed in ldap as the homeDirectory attribute, and the maildir as the mailbox attribute.
You can resolve this in a number of ways. First, you could create a symlink named Maildir in each user's home directory to their mail dir. You could then remove the "mailbox" attributes from LDAP or else configure Courier not to look them up. When Courier delivers a message to the user, it will find their home directory in LDAP and use DEFAULTDELIVERY to decide how to deliver the message to the user.
Assuming that /ticoon/mail/DavidA/ is a maildir, another way that you could approach the problem would be to modify your mail fs setup such that /ticoon/mail/DavidA/ were a directory containing a maildir named Maildir. By doing so, you're setting /ticoon/mail/DavidA/ up as a sort of "home dir" for the context of email delivery. As such, it could contain .courier or .mailfilter files in addition to the Maildir directory. After making that change, you'd need to modify authldaprc such that LDAP_HOMEDIR uses the "mailbox" value, and LDAP_MAILDIR is commented out. Now, when Courier attempts delivery, it will get /ticoon/mail/DavidA/ as the home directory for davida, and will use DEFAULTDELIVERY to decide how to deliver the message to the user.
There MUST be a way to invoke spamassassin (and eventually antivirus) during the delivery process. I really cannot understand the rational for restricting maildrop in this manner (user are local, mailbox and home are different ... so I am not "DEFAULT" according to who?).
Courier can be configured to deliver mail to a user in a number of different ways. I'm not sure I'll get the order right, but when the Courier daemon attempts delivery, it first needs to look up how mail will be delivered. It can get this information from the maildir attribute of a user record, if the backend supports it (such as SQL, userdb, and LDAP, but not local system password files), or it may find instructions in a dot-courier file in the user's home directory, or it may use DEFAULTDELIVERY. The first value which contains a delivery instruction will be used.
Therefore, if your user record specifies a mailbox, Courier will not use DEFAULTDELIVERY, because a more specific delivery instruction has been provided. If you want to use DEFAULTDELIVERY, you must not specify instructions in the mailbox attribute or dot-courier files. Either of those override the DEFAULTDELIVERY setting. Instead, you want to provide Courier with information about a home directory that contains a Maildir.
I guess I will have to take another look at procmail, but I am not sure if all the extended mailbox delivery attributes are passed to non-embedded delivery agents?
You won't solve the problem by using a different MDA. Courier would still not invoke it if a mailbox is specified.
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
