Hey Justin:
Thanks for your answer! I'm curious about something else, though: does
your procmail recipe say (in words) "Take whatever has 5 stars OR more and
pipe it to /dev/null?" I'm wondering about that last part with the *.*.
And what is the difference between your ".*\(\*\*\*\*\*.*)" and
"\*\*\*\*\*.*" examples?
Thanks -- I really have no experience with syntax of this nature so
anybody's help would be much appreciated.
On Thu, 17 Oct 2002 [EMAIL PROTECTED] wrote:
> I'm using this on a test box at the moment.
>
> SPAM_DIR=/var/mail/spool/quarantine/spam
> LOGFILE=/tmp/spam.log
> :0c
> {
> :0:
> * ^X-Spam-Score: \*\*\*\*\*.*
> $SPAM_DIR
> }
>
> The checks a copy of each message and dumps it into $SPAM_DIR if it
> matches >= 5. In the end I'll make this >= 10. This allows me to archive
> what I believe to be spam for subsequent reporting or pattern matching.
> Since I'm working with a copy of the message, delivery procedes like
> normal. The user never knows I'm doing this.
>
> If you want to just take all matches and null them
>
> :0h
> * ^X-Spam-Score: \*\*\*\*\*.*
> /dev/null
>
> Oh wait, I just realized I'm matching my header line, not what you're
> likely to have. My X-Spam-Score line is different. It allows filtering
> to work in LookOut and other braindead MUAs. I print the stars
> immediately after X-Spam-Score: . I imagine you can rig SA to do the same
> though. If not, you'll have to get someone to assist you with the
> specific regex to match either the stars or the numeric value.
>
> * ^X-Spam-Score: .*\(\*\*\*\*\*.*)
>
> might work for default SA rules. LookOut apparently can't search for a
> header called X-Spam-Score and then check to see if it was a value (or a
> string within it ) of X. The only way I've found to make a header match
> work is to do a header search for a literal "X-Spam-Score: ******". That
> seems to work fine.
<snip>
>
> On Thu, 17 Oct 2002, Kenneth Chen wrote:
>
> > I'm curious about something -- can you actually create a recipe in
> > procmail to filter emails with X-Spam-Status at 20 or more to send emails
> > directly to /dev/null?
> >
> > If so, what would the recipe be?
> >
> > And what exactly is the difference between 'probably-spam' and
> > 'definitely-spam' thresholds?
> >
> > Thanks,
> > Kenneth
>
-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
