> I checked a little bit more into the situation to see if i can find a way
> to identify such test mails and excempt them from the test, but could not
> find a criteria which would be secure enough.
Oh, err on my side. What i thought to be a unique identifier or something
like that in the subject is in fact text. The testmail in my case reads
> Subject: =?utf-8?B?TWljcm9zb2Z0IE9mZmljZSBPdXRsb29rLVRlc3RuYWNocmljaHQ=?=
which is base64 encoded for "Microsoft Office Outlook-Testnachricht". This
is german. The english variant of the subject is "Microsoft Office Outlook
Test Message".
I just wrote a patch for check_basicheaders which will excempt the mail
from the date header check if the subject is encoded in utf-8 and base64
(as above) and begins with "Microsoft Office Outloo" which will catch both
the german and the english variant.
The patch is crude and shall better be rewritten with proper decoding of
the various possible charset encodings, but here it is nethertheless in
case one is interested.
--- check_basicheaders.old 2006-06-30 10:16:45.000000000 +0200
+++ check_basicheaders 2006-06-30 10:32:48.000000000 +0200
@@ -51,6 +51,9 @@
return (DENY, "Mail with no From header not accepted here")
unless $transaction->header->get('From');
+ my $subject = $transaction->header->get('Subject');
+ return (DECLINED) if ( $subject =~
/^=\?utf-8\?B\?TWljcm9zb2Z0IE9mZmljZSBPdXRsb29/ );
+
my $date = $transaction->header->get('Date');
return (DENY, "Mail with no Date header not accepted here")
Regards
Michael
--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks
