In this case, I would try to set DEFAULTDELIVERY="|spamc|maildrop" and omit the "xfilter spamc" in maildroprc. I cannot imagine that it hurts to call spamc in all cases (besides of performance).
As far as I can see, maildrop passes the $HOME of the unix user running maildrop to spamc, while courier itself passes the $HOME of the virtual user...
Can anyone confirm or deny my conclusion?
spamc passes the username to spamd, which then looks up the user's home directory. I don't think that moving spamc into place as courier's delivery agent is going to help, as HOME will not be used. I don't think that HOME is ever used by SpamAssassin. It's mentioned once in the code, but I'm not sure how it'd be triggered.
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
