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).
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|