You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Geoff Soper <ge...@alphaworks.co.uk> on 2004/07/17 13:36:36 UTC
.procmailrc problem
Can anyone suggest why this .procmailrc rule:
<snip>
# Spam
:0:
* ^X-Spam-Flag: YES
* ^TO_*.my_address@my_domain
* !^X-Loop: my_loop_address@my_domain
| (formail -r -I"Precedence: junk" \
-A"From: do_not_reply@my_domain" \
-A"X-Loop: my_loop_address@my_domain" ; \
cat /home/username/auto_responders/geoff_spam) | $SENDMAIL -t
<snip>
lets quite a few messages through such as one containing these headers:
<snip>
To: my_address@my_domain
Subject: *****SPAM***** ORIGINAL MICR0S0FT, AD0BE, N0RTON, COREL DRAW CD
FROM $15 women couvert
Date: Fri, 16 Jul 2004 22:39:13 -0700
Message-Id: <ee...@auxiliumaugitic>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on
server.domain.co.uk
X-Spam-Status: Yes, hits=10.6 required=5.0 tests=HTML_30_40,HTML_FONT_BIG,
HTML_MESSAGE,J_CHICKENPOX_14,J_CHICKENPOX_15,J_CHICKENPOX_21,
J_CHICKENPOX_22,J_CHICKENPOX_23,J_CHICKENPOX_26,J_CHICKENPOX_29,
J_CHICKENPOX_42,J_CHICKENPOX_44,J_CHICKENPOX_45,J_CHICKENPOX_62,
MSGID_FROM_MTA_HEADER,SARE_OEM_FAKE_YEAR,SARE_OEM_SOFT_IS
autolearn=no version=2.63
X-Spam-Level: **********
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_40F8AEFF.224F4EA6"
<snip>
Many thanks!
Geoff
Re: .procmailrc problem
Posted by Geoff Soper <ge...@alphaworks.co.uk>.
>
> ----- Original Message -----
> From: "Geoff Soper" <ge...@alphaworks.co.uk>
> To: <sp...@incubator.apache.org>
> Sent: Saturday, July 17, 2004 6:36 AM
> Subject: .procmailrc problem
>
>
>> Can anyone suggest why this .procmailrc rule:
>>
>> <snip>
>> # Spam
>> :0:
>> * ^X-Spam-Flag: YES
>> * ^TO_*.my_address@my_domain
>> * !^X-Loop: my_loop_address@my_domain
>> | (formail -r -I"Precedence: junk" \
>> -A"From: do_not_reply@my_domain" \
>> -A"X-Loop: my_loop_address@my_domain" ; \
>> cat /home/username/auto_responders/geoff_spam) | $SENDMAIL -t
>> <snip>
>
> No, but I would try it with X-Spam-Status instead of X-Spam-Flag FWIW.
>
Oops, it was actually using X-Spam-Status until this morning when I tried
changing to see if that was the problem. I've realised the problem to
actually be the
>> * ^TO_*.my_address@my_domain
recipe which should be
>> * ^TO_.*my_address@my_domain
I'd mistyped the regular expression! Simple when you know..
Thanks,
Geoff