Jo wrote: > > I setup mail servers all the time and I always make sure the > > Mail server broadcast name, the 'A' record and the PTR all match, > > IT IS JUST GOOD PRACTICE.
No, it's NOT good practice. Seriously. Without battering the point, it's really perfectly legit for an MTA to use different HELO names (say, based on hosting of virtual servers), whilst the IP address for that MTA has a "fixed" PTR. That's not a sign of spam; not even a bit. It is, however, good practice, as I pointed out, to have those HELO names resolve to the IP address of the connecting client. Though not an RFC specific MUST, certainly a good idea to have one's own stuff in order. > > *cirencester.co.uk*(*c204131.adsl.hansenet.de*[213.39.204.131]) Clearly, the PTR used here indicates a dynamic IP address. That may prompt an immediate reaction. But Richard gave a good example: Received: from mail.apache.org (hermes.apache.org [209.237.227.199]) There is really nothing score-worthy about that (spam-wise). Your example, btw, on my server would be REJECT-ed for another reason, though: Go away, spammer! [213.39.204.131]: "United Kingdom" [.uk HELO] != "Germany" [.de PTR]" In the strictest sense, I'm not allowed to do that, either. But my rationale is, that the connecting host's HELO is perpetrating a lie here that under any reasonable circumstance is just irreconcilable with the PTR (the MTA simply cannot be in both countries at the same time). - Mark
