DogMatz wrote:
Emails from one of my accounts often get the HELO_DYNAMIC_IPADDR but I can´t
see why!
Nor can we since you didn't include the headers from the actual message
scanned, rather just the report_safe encapsulation headers.
Daryl
Check this mail:
Received: from localhost by webbox413.server-home.net
with SpamAssassin (version 3.1.3);
Tue, 08 May 2007 15:52:01 +0200
From: Marcel Korte <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: *****SPAM***** TEST!!!
Date: Tue, 8 May 2007 15:51:46 +0200
Message-Id: <[EMAIL PROTECTED]>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on
webbox413.server-home.net
X-Spam-Level: *******
X-Spam-Status: Yes, score=7.6 required=5.0 tests=AWL,BAYES_80,
FORGED_RCVD_HELO,HELO_DYNAMIC_IPADDR,PLING_PLING autolearn=no
version=3.1.3
X-Spam-Report:
* 4.2 HELO_DYNAMIC_IPADDR Relay HELO'd using suspicious hostname (IP addr
* 1)
* 0.1 FORGED_RCVD_HELO Received: contains a forged HELO
* 2.0 BAYES_80 BODY: Bayesian spam probability is 80 to 95%
* [score: 0.8032]
* 0.3 PLING_PLING Subject has lots of exclamation marks
* 1.0 AWL AWL: From: address is in the auto white-list
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_46408081.5D87A5E1"
This is a multi-part message in MIME format.
