bogofilter setup in multi-user

[Tom Anderson]

From: ".rp" <printer at moveupdate.com>
> Next we check the subject for certain words that we know we want no part
of
>
> :0H
> *  ^Subject:.*(p0rn| pr0n| HGH |ha1f| curn |GB2312)|\
>   ^Subject:.*(paris hilton|p4ris|par1s|p4r1s )|\
>   ^Subject:.*(iagra |@gra|1agra|lagra|Cialis)|\
> /dev/null

This is dangerous... what if you have legitimate emails that talk about
these topics... like emails in this list?

> #no legit mail should have "|" in its subject
> :0H
> * ^Subject:.*(\|)
> /var/spool/mail/junkbox

Why not?  I don't see anything in the RFC banning it.  Do you often receive
spams with a pipe in the subject?  This seems odd to me.

> :0H:
> * ^Subject:.*(â|í|Ò|Æ|¶|¯|º|Í|Á|ª|Í|¨|È|«|¿|ª|Í|¨|Ë|ë|ä|ö|ü|ï|é|¡|ã|ò)
> /dev/null

Again, dangerous.

> Then we go through and see if it is for someone with special needs in
their filtering
> #if for Rick -  do a special run for them

Why not specify these rules in each users own procmailrc file and specify
their bogofilter settings in their bogofilter.cf file?  Managing this in a
single large file could be burdensome with a much larger set of users.

It seems like you could just eliminate most of these procmail rules and rely
solely on bogofilter instead.  Bogofilter should handle most of the obvious
spam terms like "pr0n" and whatnot, and then you wouldn't have to maintain
your own ad hoc list which will likely go out of date very quickly.

Tom