Re: [courier-users] maildrop and authlib communication
Brought to you by:
mrsam
From: Sam V. <mr...@co...> - 2008-12-29 03:15:56
|
Juan Miscaro writes: > 2008/12/28 Sam Varshavchik <mr...@co...>: >> Juan Miscaro writes: >> >>> I am using maildrop 2.0.4 (which uses authlib by default) on OpenBSD >>> 4.4. Now I have the following maildroprc file: >>> >>> ---------------- >>> logfile "/var/log/maildrop" >>> >>> /^Delivered-To:\s*.+/ >>> RECIPIENT=getaddr ${MATCH} >>> >>> USER="" >>> DOMAIN="" >>> if ( ${RECIPIENT} =~ /(.*)@([^@].*)/ ) >>> { >>> USER=${MATCH1} >>> DOMAIN=${MATCH2} >>> } >>> else >>> { >>> #no domain part >>> USER=${RECIPIENT} >>> } >>> >>> MAILDIR="/var/spool/virtual_mailboxes/$DOMAIN/$USER/Maildir" >>> >>> if (/^X-Spam-Status: Yes/) >>> { >>> to $MAILDIR/.Spam/ >>> } >>> ---------------- >>> >>> Now since maildrop is already informed about where the mail goes (via >>> authlib) should it not be possible to have a simpler rc file by not >>> having to build up the mailbox/maildir destination? >> >> Only if the courier-authlib configuration explicitly returns the location of >> the account's mailbox. > > Thanks Sam for your response but I need more details! > > How can I make the courier-authlib configuration explicitly return the > location of > the account's mailbox? That depends on the authentication module you're using. Not all of them do. This is supported by userdb, ldap, mysql, and postgres. Each one's configuration file that defines an attribute/field where the account's default mailbox. If not specified (the permanent default for all other modules), it defaults to $HOME/Maildir. |