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.

Given the complexity I am already playing with, I do not really want to dump and reload my LDAP configuration. Even if I am assume that all I have to do is delete the "mailbox" attribute ... it's just with everything else working, do I really want to mess with it.

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?). 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?

From my mail.log
Jan 10 09:57:19 localhost courierd: started,id=0004804F.41E297CE.00002BF8,from=<>,module=local,host=davida!! 11003!512!/home/DavidA!/ticoon/mail/DavidA!,addr=<davida>


looks local to me.


On 7-Jan-05, at 5:48 PM, Gordon Messmer wrote:

David Aspinall wrote:
Ok, so if I understand everything now, maildrop is where I want to do spamassasin filtering (xfilter) so it can modify the message before delivery, however because I am using LDAP and placing messages in a directory other than the $HOME for the user .. maildrop does not execute as expected and my filtering never happens.
How can I get maildrop to behave?

See the message I sent to the list at 10:37:
http://groups-beta.google.com/group/mailing.unix.courier-imap/ browse_thread/thread/d776a53483bc974/3057e492cb307c78? q=messmer+maildrop+DEFAULTDELIVERY+example.com&_done=%2Fgroups%3Fq%3Dme ssmer+maildrop+DEFAULTDELIVERY+example.com%26hl%3Den%26btnG%3DGoogle+Se arch%26&_doneTitle=Back+to+Search&&d#3057e492cb307c78



userdb [EMAIL PROTECTED] set home=/home/virtual/example.com/john \ � � � � � � �mail=/home/virtual/example.com/john \ � � � � � � �uid=999 gid=999

Such a user would not invoke maildrop for delivery. Because the mail
attribute is specified, Courier will deliver mail directly to that
mailbox. This is similar to what would happen if a local user had a
.courier file which specified the same mailbox.

In order to use maildrop, you would want to remove the mail attribute
from that userdb entry. Also, rather than a maildir,
/home/virtual/example.com/john should be a normal directory containing a
maildir named "Maildir". You'd set it up like:


# mkdir /home/virtual/example.com/john
# maildirmake /home/virtual/example.com/john/Maildir
# chown -R 999:999 /home/virtual/example.com/john

Set up this way, DEFAULTDELIVERY will be used.


------------------------------------------------------- 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



------------------------------------------------------- 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

Reply via email to