| The FORGED_MUA_* rules mainly compare the X-Mailer header with the
| format of the Message-ID header. From the mail header below, it seems
| that Outlook is not generating a Message-ID at all, relying on the
| next step to insert one (this behaviour is permitted by the
| standards). This suggests that this version of Outlook should be
| excluded from the FORGED_MUA_OUTLOOK check.
We had false +ve FORGED_MUA_OUTLOOK recently. Clearly the Message-ID was
not written by outlook! Maybe outlook didn't generate one.
OR, I think there are sites where the gateway MTA strips the
client-generated Message-ID and replaces it with a "corporate" standard
one.
Plausible ?
Example headers below - apologies the msg had been thru about 3 scanners
before I got it so I've had to strip some irrelevant stuff.
Chris
--
Chris Edwards, Glasgow University Computing Service
Received: from mail5.hostinguk.net ([195.224.49.142])
by hillhead.cent.gla.ac.uk with esmtp (Exim 4.10)
id 19xoXA-0005TX-00; Fri, 12 Sep 2003 15:04:24 +0100
Received: from JDORNAN [81.136.202.144] by mail5.hostinguk.net with ESMTP
(SMTPD32-8.00) id A2598B2001E; Fri, 12 Sep 2003 15:04:09 +0100
From: xxxx
To: xxxx
Date: Fri, 12 Sep 2003 15:04:04 +0100
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0011_01C3793F.1BC239C0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300
Disposition-Notification-To: "Jean Dornan" <[EMAIL PROTECTED]>
X-Declude-Sender: [EMAIL PROTECTED] [81.136.202.144]
X-Note: This E-mail was scanned for spam.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
