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 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"?
I'm not referring to spamassissin specifically -- I've had mail rejected by smtp servers for both having a address the HELO which didn't match the reverse DNS string and for using a bare IP address. Such servers are breaking the RFCs of course, but it's understandable. > 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. I've had mail rejected. > I'm seeing 4.7 here, nowhere near 7.7. Still peeved :) It turns out that my ISP has got around to offering custom rDNS entries, so I suspect I'll be doing that in order to fix this. Are the available DUL lists so unreliable that your pattern matching is better? Many ADSL ISPs in this country are using this kind of naming scheme with both static and dynamic IP allocation. Phil -- http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
