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 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. > On Tue, Nov 08, 2005 at 09:52:49AM -0800, Justin Mason wrote: > > What are those "other reject rules"? On 08.11.05 19:17, Philip Armstrong wrote: > 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. actually, server only breaks the RFC if it refuses the mail _just because_ helo string does not match the connecting hostname/IP address. if a server refuses mail because of any other reason, even if it's related to helo string (nonexistent host in HELO/EHLO, bare IP not enclosed in [], IP in blacklist, ...), they don't violate the RFC (unless they violate it elsewhere). > > 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 fine for assigning score > > 2. that you're delivering direct-to-MX fine for rejecting the mail at all > > 3. that the HELO string matches the dynamic-looking rDNS this is correct behaviour of SMTP clients required by RFC 2821, so it should not be penalized in any way. I much often have problems with machines that do NOT send their hostname (worms, viruses, spamware, etc.) > > 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. I don't think this has to be changed in any way. > 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. if the IP is statically allocated, the DNS record should clearly say so. It seems, currently this IP has different record (kantaka.co.uk). I'd like to heas SA maintainers' opinion on my notes above... -- Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Microsoft dick is soft to do no harm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
