Jay Lee <mailto:jl...@pbu.edu> wrote on Wednesday, September 28, 2005
5:48 PM:
Dan Horne wrote:
if ( $SIZE < 26144 )
{
exception {
xfilter "/usr/bin/spamassassin
--prefspath=$HOME/$DEFAULT/.spamassassin/user_prefs " }
}
You also really, really want to be using spamc here and have the
spamd daemon running. It makes a *huge* difference in performance.
If you call the spamassassin binary each time, the first 100 emails
in 10 minutes will bring your shiny new mail server to it's knees...
**NOTE: Resending this to list as original went to Jay Lee's address
instead of the list. **
I can call spamc from maildrop? That shows you how much I have been
able to glean from the maildrop doco. I don't necessarily need to have
spamassassin called from maildrop (we're also using amavisd-new for
virus scanning), but we host multiple domains and want each user to have
its own spam settings and bayes and autowhitelist db's. Calling
spamassassin from maildrop was the best way I could figure to do that.
How would I call spamc? Running spamd is not a problem, I already have
that set up I just have to set it to startup automatically.
Is there a better way to do this that would allow me 1)per-user settings
and 2)the ability to turn spam filtering on and off per address or
domain from the db?
Thanks for your suggestions.
8 messages in net.sourceforge.lists.courier-maildropRE: [maildropl] How to get extra info...
