Hi, James. I use this here, but mine is a small server. When I see what looks like a real message that was blocked, I usually email the postmaster of the other system with a canned letter advising them of the issue and how to fix it. It's usually just a line in their config that sets the helo name. Sometimes I hear back and they're grateful for the pointer, sometimes I never hear back.
Other larger sites will silently drop mails from such misconfigured systems, though this isn't consistent. If more systems would enforce this, I think it would be better for everyone involved. Jim On Feb 6, 2012, at 7:36 AM, James Day wrote: > Just wanted to get public opinion on this one. > > reject_unknown _helo_hostname > > My understanding is that to be RFC compliant your HELO greeting must be a > valid hostname (ie there is a public A record). > > However since implementing this restriction under smtpd_helo_restrictions I > have had nothing but complaints from people who think their messages are > being unfairly blocked. > > I know we don’t live in a perfect world and not everybody is going to have a > correctly configured mail server but I don’t think it is unreasonable for me > to stick to my guns and reject these messages. > > Having said that, some people have more influence than others and should they > voice any concerns I would be forced to make some changes. With that in mind, > what would be the best way to make exceptions? > > My current line of thought is to use a check_helo_access map to make > exceptions on a per server basis, is there a better way? > > Kind regards, > > James Day > (IT Engineer) > >
