If we do that, we could do with a corresponding __FAKE_THEBAT_MUA rule,
which should then be trivial.

Cheers,

Phil

--
Phil Randal | Networks Engineer
Herefordshire Council | Deputy Chief Executive's Office | I.C.T.
Services Division
Thorn Office Centre, Rotherwas, Hereford, HR2 6JT
Tel: 01432 260160
email: [email protected]

Any opinion expressed in this e-mail or any attached files are those of
the individual and not necessarily those of Herefordshire Council.

This e-mail and any attached files are confidential and intended solely
for the use of the addressee. This communication may contain material
protected by law from being passed on. If you are not the intended
recipient and have received this e-mail in error, you are advised that
any use, dissemination, forwarding, printing or copying of this e-mail
is strictly prohibited. If you have received this e-mail in error please
contact the sender immediately and destroy all copies of it.

-----Original Message-----
From: Maxim Masiutin [mailto:[email protected]] 
Sent: 11 February 2009 09:58
To: [email protected]
Subject: a reliable way to detect The Bat! is by message-id, not by
x-mailer

Hello Dev,

  A reliable way to detect The Bat! is to parse the Message-ID. 

  The Bat! uses a special algorithm to construct it, I wrote to Malte S.
Stretz about it already, and he have implemented a corresponding rule
several years ago.

  I suggest to drop the following rule entirely __THEBAT_MUA
X-Mailer =~ /The Bat!/
  and only rely to the message-id to detect The Bat! 
  


--
Best regards,
Maxim Masiutin                          mailto:[email protected]

Reply via email to