Whitelist mailservers with no rDNS - Postfix
For more info you can see the previous post, but the gist of it I was SUPPOSED to be receiving an email, which I wasn't.
After taking a look at my mailserver I found that it was rejecting the messages as the sender didn't have rDNS setup. As I automatically block all servers with no rDNS this was a problem. I didn't want to open up my server to spam, so I wasn't going the rule for everyone. Thus my only option was to whitelist the problem server.
Luckily with Postfix this is pretty easy.
The initial error:
Nov 20 19:59:35 meyling postfix/smtpd: NOQUEUE: reject: RCPT from unknown[220.127.116.11]: 450 4.7.1 : Helo command rejected: Host not found; from= to= proto=ESMTP helo=
My reject rules - in this case reject_unknown_helo_hostname is the culprit:
root@meyling:/# cat /etc/postfix/main.cf | grep reject_unknown reject_unknown_sender_domain reject_unknown_helo_hostname, reject_unknown_reverse_client_hostname,
The fix - create a whitelist file with the bad mailserver included AND set the Postfix rule BEFORE the reject so that it kicks in first (Postfix applies rules sequentially, from top to bottom). This is set in /etc/postfix/main.cf under smpdrecipientrestrictions.
smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, check_client_access hash:/etc/postfix/whitelist_helo reject_non_fqdn_helo_hostname, reject_unknown_helo_hostname, reject_unknown_reverse_client_hostname, reject_unauth_destination
We now need to create the whitelist file and include the bad servers IP which we wish to ignore.
root@meyling:/etc/postfix# cat /etc/postfix/whitelist_helo 18.104.22.168 OK
Next we run postmap to update our changes.
Now all that's left is for us to reload Postfix with our new config.
service postfix reload
We should now be receiving email from the badly configured mailserver! Now all that's left is to educate the admin on the other end and get them to fix, which is often easier said than done ;)