-----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 differently to the rDNS then I hit another set of > reject rules. Unfortunately, my ISP doesn't currently offer the > ability to set my own rDNS to match my personal domain, which is what > I'd prefer to do obviously. What are those "other reject rules"? The problem here is *not* simply that your rDNS looks "dynamic" in any way. We in SpamAssassin understand that many ISPs still do that, c'est la vie. The problem, instead, is threefold: 1. that the rDNS string appears symptomatic of a dynamic pool 2. that you're delivering direct-to-MX 3. that the HELO string matches the dynamic-looking rDNS The combination of all 3 has been a very strong spam signature with virtually nonexistent nonspam hits, for over a year. The easiest part to fix is number 3. Change your MTA to use its own name (e.g. "mail.yourdomain.com") as the HELO string, instead of whatever rDNS it has been assigned. To the best of my knowledge and experience, using a HELO string that doesn't match rDNS will not cause issues with filtering elsewhere, as it's SOP for many other domains. > > If after this you still believe that a 7.7 score is correct then please > > say so, at least he (who I Cc'ed) will know why in the future all his > > mail will be rejected by spamassassin. :-) > > 7.7! > > 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. - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Exmh CVS iD8DBQFDcOXxMJF5cimLx9ARAipXAJ9mu7L8z6j9KAPK5+eFMjzixCvpwgCgiA6j n9OkiyHTFXkltKzcHBqO+F0= =WqqW -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
