-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Sep 23, 2003 at 11:21:22AM +0200, Ole Wolf wrote: >I recall that Kyle Hasselbacher (right?) recently said something about >letting email with a spamassassin score of 3 or lower through TMDA >unhindered, and send a confirmation email to anything higher (unless >whitelisted or confirmed, of course). > >How did you do that?
I'm using SpamAssassin version 2.55 and TMDA version 0.82. Here's the end of my .procmailrc: ****** BEGIN ****** # This is all my spam filtering. # If it's not going to a TMDA tagged address, # and it's not already tagged as spam (because it's SO's forwarded spam), # and it's not already been to see TMDA (because it's a confirmed message), # then run it through spamassassin # # Tags removed from list: exp|expires|dated|d| # If it's to a dated address, I want to give it a chance to deliver even if # TMDA considers the address expired. :0fw * !^To: .*kyle-(key|keyword|kw|cnf|confirm|c|snd|src|sender|s)-.*@ * !^X-Spam-Status: Yes * !^X-TMDA- | spamassassin # There's no point in letting TMDA see these now. :0 * ^X-Spam-Status: No $DEFAULT # Run the message through tmda-filter. :0 w | /usr/bin/tmda-filter # Take the exit code from TMDA EXITCODE=$? # TMDA takes care of final delivery DEFAULT=/dev/null ****** END ****** The list of tags used in the spamassassin recipe are taken from my .tmda/config, which I customized without having a good reason. ****** BEGIN ****** # How to identify various tags. First entry is default when generating. TAGS_DATED = [ 'exp', 'expires', 'dated', 'd' ] TAGS_KEYWORD = [ 'key', 'keyword', 'kw' ] TAGS_CONFIRM = [ 'cnf', 'confirm', 'c' ] TAGS_SENDER = [ 'snd', 'src', 'sender', 's' ] ****** END ****** The spam level that's accepted without challenge is configured in SpamAssassin's config as 'required_hits' and defaults to 5. Here are a couple of other bits from .spamassassin/user_prefs: ****** BEGIN ****** # Don't fold the message into an attachment. report_safe 0 use_terse_report 1 ****** END ****** This was because when the message was folded into an attachment, the Return-Path header was stripped. Without that, TMDA wouldn't deliver confirmed or released messages, and I suspect it had a hard time sending challenges, though I don't remember. This is at the end of .tmda/filters/incoming: ****** BEGIN ****** # 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 headers 'X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*' hold headers 'X-Spam-Status: No' ok ****** END ****** Note that the second line shouldn't be used because of procmail. The first line determines the spam level that's considered "too terrible to bother challenging." I 'hold' rather than 'drop' because I'm a pack rat. Let me know if you have questions or problems with this. Hope it helps. - -- Kyle Hasselbacher Indifference will certainly be [EMAIL PROTECTED] the downfall of mankind, but who cares? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/cEGP10sofiqUxIQRAiH7AJwOnF6PrhXEah1SlDbOWY0S1bpHZACgqtE6 FhrcpRjae/06jVXuHZ8oS24= =3Ti1 -----END PGP SIGNATURE----- _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
