-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello!
Alan Milligan wrote:
You are doing some quite interesting stuff there with IMAP.
Thanks :-)
I'm a little confused about your SpamAssassin setup though. Your
maildroprc doesn't actually show the spamassassin/spamc call which is
the interesting bit for me.
That's done in ~/.courier. The whole setup is nothing without the actual call of spamc and maildrop. To allow my users to choose what they want, I just give them a script that writes "|spamc|maildrop" into ~/.courier. Simple and really easy to script -- and most flexible for the advanced users to play with.
I'm also interested to know if you are using authdaemond or simply authuserdb - but of course SpamAssassin doesn't know about either of these.
Oh I get it now ...
You are doing your spamchecking at point of local delivery - at this point, authdaemond has been referenced as the subsequent action of your maildroprc not having fully disposed the message, and the correct $HOME thus set.
This implicit binding is the obvious benefit of this process - however it requires a .courier in each virtual mail account. I'd prefer to use an xfilter command from within the global maildroprc to mitigate this - however $HOME is ignored by spamc/spamd :(
Is there any way to do this?
Cheers, Alan
------------------------------------------------------- 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
