This question is similar to others about PTR and DNS for SMTP, but one specific aspect was unanswered: what if one machine does SMTP and HTTP on the same IP address. For example:
SMTP at mail.example.com, also HELO. (184.108.40.206) HTTP at www.example.com (220.127.116.11) general access like ssh at example.com (18.104.22.168)
What are the requirements for the PTR record on the address 22.214.171.124 to be accepted by spam filters? The 'main' hostname for 126.96.36.199 is example.com, but if reverse DNS lookups require an exact match, I have to set it to mail.example.com. That's stupid. I mean, reverse lookups of 188.8.131.52 don't result in mail.google.com.
Or, is it enough if a reverse lookup finds example.com and mail.example.com as MX record on it? In other words, should I set the PTR to example.com?
One could argue that I should make SMTP access and the HELO example.com, but that causes inflexibility, because then I can never move SMTP to another machine by simply changing the A record.
Edit: it seems unclear what I mean, so let me clarify:
The server in question hosts DNS, SMTP, WWW and a lot more. It does all of it's own DNS. Example.com points to that machine, say 184.108.40.206. Because mail is not its main thing, I don't want 220.127.116.11 to reverse resolve to mail.example.com
The server runs postfix and its HELO is mail.example.com, which also points to 18.104.22.168. For the PTR to match, 22.214.171.124 should reverse resolve to mail.example.com, but as I said, I want it to resolve to example.com, because mail is not the server's main task.
Does that mean I have to change the mailname to example.com, and having it at mail.example.com will cause some spam filters to reject it, even though mail is an mx record of example.com?