I know this was mentioned a while ago, but I couldn't find it in the
archives...
Bascially, the problem is that Outlook Express 6 uses a different format for
Undisclosed Recipients. Here's the top of a message that got flagged:
From: "Removed" <[EMAIL PROTECTED]>
To: <Undisclosed-Recipient:@mimas.island.net;>
Subject: Fw: men vs women
Date: Mon, 11 Feb 2002 17:01:36 -0800
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Status: Yes, hits=6.2 required=5.0 tests=FROM_ENDS_IN_NUMS,FAKED_UNDISC_RECIPS
version=2.01
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.01 (devel $Id: SpamAssassin.pm,v 1.61
2002/01/25 04:41:02 jmason Exp $)
X-Spam-Prev-Content-Type: text/plain;
charset="iso-8859-1"
SPAM: -------------------- Start SpamAssassin results ----------------------
SPAM: This mail is probably spam. The original message has been altered
SPAM: so you can recognise or block similar unwanted mail in future.
SPAM: See http://spamassassin.org/tag/ for more details.
SPAM:
SPAM: Content analysis details: (6.18 hits, 5 required)
SPAM: Hit! (1.94 points) From: ends in numbers
SPAM: Hit! (4.24 points) Faked To "Undisclosed-Recipients"
SPAM:
SPAM: -------------------- End of SpamAssassin results ---------------------
Since the regexp for FAKED_UNDISC_RECIPS is
To =~ /Undisclosed.*Recipient\S*@/i this matches.
Can anyone suggest a way to reformat that regexp to not catch this case? Or
should the rule just get scored lower?
Dan.
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
