Bug#337922: too much aggressive HELO_DYNAMIC_* tests

2006-07-24 Thread Matus UHLAR - fantomas
Hello, This may not have been the wisest choice by the administrator considering the circumstances, but I think it's hard to argue that people should use an HELO string different from the rDNS... Philip Armstrong writes: Quite. If I set it differently to the rDNS then I hit

Bug#337922: too much aggressive HELO_DYNAMIC_* tests

2005-11-08 Thread Philip Armstrong
Apparently I'm hitting spamassassin tests :( On Mon, Nov 07, 2005 at 11:41:50PM +0100, Marco d'Itri wrote: On Nov 07, Duncan Findlay [EMAIL PROTECTED] wrote: The SpamAssassin scores are carefully optimized -- I won't change any scores from upstream. What seems more likely is that your Yes,

Bug#337922: too much aggressive HELO_DYNAMIC_* tests

2005-11-08 Thread Justin Mason
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philip Armstrong writes: This may not have been the wisest choice by the administrator considering the circumstances, but I think it's hard to argue that people should use an HELO string different from the rDNS... Quite. If I set it

Bug#337922: too much aggressive HELO_DYNAMIC_* tests

2005-11-08 Thread Marco d'Itri
On Nov 08, Justin Mason [EMAIL PROTECTED] wrote: Seems extreme for someone who has a static ip address has set the SMTP HELO to match the rDNS for that ip. Given that this is *precisely* what is suggested by the relevant RFCs I'm slightly peeved! I'm seeing 4.7 here, nowhere near 7.7.

Bug#337922: too much aggressive HELO_DYNAMIC_* tests

2005-11-08 Thread Philip Armstrong
On Tue, Nov 08, 2005 at 09:52:49AM -0800, Justin Mason wrote: Philip Armstrong writes: This may not have been the wisest choice by the administrator considering the circumstances, but I think it's hard to argue that people should use an HELO string different from the rDNS... Quite. If

Bug#337922: too much aggressive HELO_DYNAMIC_* tests

2005-11-07 Thread Marco d'Itri
Package: spamassassin Version: 3.1.0a-1 Severity: important A single generic rDNS in a Received header is enough to raise way too much the score. Also, it appears that this check would be applied even to mail delivered trought an ISP relay. X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13)

Bug#337922: too much aggressive HELO_DYNAMIC_* tests

2005-11-07 Thread Justin Mason
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 HELO_DYNAMIC_DHCP and HELO_DYNAMIC_IPADDR both will not match if an ISP's relay is used; they fire only if the last untrusted IP delivered them directly. They also do not act on rDNS; they act on HELO strings that match that kind of rDNS. Major

Bug#337922: too much aggressive HELO_DYNAMIC_* tests

2005-11-07 Thread Duncan Findlay
severity 337922 normal thanks On Mon, Nov 07, 2005 at 10:58:51AM +0100, Marco d'Itri wrote: A single generic rDNS in a Received header is enough to raise way too much the score. Also, it appears that this check would be applied even to mail delivered trought an ISP relay. The SpamAssassin

Bug#337922: too much aggressive HELO_DYNAMIC_* tests

2005-11-07 Thread Marco d'Itri
On Nov 07, Duncan Findlay [EMAIL PROTECTED] wrote: The SpamAssassin scores are carefully optimized -- I won't change any scores from upstream. What seems more likely is that your Yes, I am arguing that the scores for these two tests are too much aggressive. The message was rejected (even after