On Sun, Sep 22, 2002 at 11:29:41PM +0200, Andy McKell, FOCUS Internet
wrote:
I disagree that it's impossible if you don't attempt to build
something too
complicated - look at what's irritating your users and seek to kill
that first.
The question wasn't really specific about whether users wanted a general
tool to manipulate their own .procmailrc or whether they wanted to apply
individual functions in the form of procmail recipes. If the latter,
then your approach is certainly the best. If the former, then it's
obviously not.
They login (to identify which directory to use) then input to a form the
specific phrases they want to exclude e.g. "adult website", "low-cost
mortgages". Perl inserts the *(^|[^0-9a-z])$item([^0-9a-z]|\$) etc. before
writing to the user's own procmailrc.
If you want some additional recipe inclusion suggestions, I've got a
bunch at http://www.it.ca/software/procmail-spamtrap . Especially fun
is the stuff to recognize invalid hotmail/yahoo/AOL messages. Lots of
spam comes in as direct delivery with a free mail provider as a spoofed
source address.
It's running fine under test and am adding online recovery from a 30-day
archive, so there's minimal intervention needed.
How are you implementing the 30-day archive? In particular, how are you
aging the messages? I've been trying to figure out a safe way to do
that, and so far I've been insatisfied with my results.
Incidentally, a local big ISP here is now using spam assassin (or
similar)
A big ISP? In Luxembourg? ;-)
--
Paul Chvostek
<paul(_at_)it(_dot_)ca>
Operations / Abuse / Whatever +1 416 598-0000
it.canada - hosting and development http://www.it.ca/
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail