Anyone got any idea why an EXE attachment that came in a message with these
headers got through the current release of the system filter? It's catching
vast amounts of other stuff but missed this one....
[Headers are as revealed to the Outlook 2000-using recipient; I've changed the
"EXE" in the MIME headers to "XEX" to get this message out through the
filters!]
Alan
---
Received: from rebo.lancs.ac.uk ([148.88.16.230]) by
exchange-ims.lancs.ac.uk with SMTP (Microsoft Exchange Internet Mail Service
Version 5.5.2653.13)
id J4GT289A; Thu, 26 Apr 2001 11:09:17 +0100
Received: from compton.mirror.ac.uk ([212.219.56.140])
by rebo.lancs.ac.uk with esmtp (Exim 3.22 #2)
id 14sihl-0006Lh-00; Thu, 26 Apr 2001 11:08:57 +0100
Received: from Linux.dodo.sk (Linux.dodo.sk [193.58.193.11])
by compton.mirror.ac.uk (8.9.3+Sun/8.8.8/cf-evision: 1.5 ? with
ESMTP id LAA02700
for <webmaster@???>; Thu, 26 Apr 2001 11:08:44 +0100
(BST)
Received: from mars (Kosice18.r-net.sk [193.58.195.209])
by Linux.dodo.sk (Postfix) with SMTP id F09967F8FE
for <webmaster@???>; Thu, 26 Apr 2001 12:07:59 +0200
(CEST)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--VEQFWTMRGPUB4LUZODEJOD"
Message-Id: <20010426100800.F09967F8FE@???>
Date: Thu, 26 Apr 2001 12:08:00 +0200 (CEST)
From: MAILER-DAEMON@???
To: undisclosed-recipients:;
----VEQFWTMRGPUB4LUZODEJOD
Content-Type: text/plain; charset="us-ascii"
----VEQFWTMRGPUB4LUZODEJOD
Content-Type: application/octet-stream; name="JKLBAPJK.XEX" <====
"XEX" was "EXE" in original
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="JKLBAPJK.XEX" <====
"XEX" was "EXE" in original
----VEQFWTMRGPUB4LUZODEJOD--
