I agree that Perl-based filtering is far nicer than procmail's horrid recipes, which is why I wrote my own
Perl filter, parp
(Please note that I am currently making some small changes to the filtering API which will significantly simplify it.)
I am obviously horribly biased, but while Mail::Audit is a pretty decent quick hack, there are a number of things I dislike about its approach, and a number of advantages that parp has over it (daemon/queue mode, folder filtering mode, more powerful OO-based design, automatic regression testing, dynamic learning of trusted addresses, and lots more). I am also intending to provide support for Spam::Assassin in the near future (although I'm still not convinced that SpamAssassin's statistical approach is as flexible in principle as parp's
builtin spam-detection heuristics).
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||