Okay Bigpond is giving me the shits today, I have a few customers that insist on using Bigpond for their mail and as such I need to ensure I can get mail from bigpond even when they are on the RBL shit lists which is a daily occurrence.
A normal white list in salocal.cf.in won’t cut it as those white lists are for spam assassin and we are dealing with postfix here. So I can either drop the RBL that is blocking Bigpond or I can create a framework for dealing with whitelists and RBLS for postfix. Dropping the RBL is not the solution I am looking for.
Ok lets get this show on the road…su zimbra cd /opt/zimbra/conf vi postfix_rbl_override
This file is going to contain our “white list” either as a domain or IP address, for bigpond mine looks like;220.127.116.11 OK 18.104.22.168 OK 22.214.171.124 OK bigpond.com OK bigpond.net.au OK
So what I have here are the known black listed IP’s of mail servers I want to get through and the domains of the provider. Now we want to run the command postmap /opt/zimbra/conf/postfix_rbl_override This will alert postfix changes have been made to the database and to reload it.
Next step is to tell postfix to check our override file when rejecting recipient mail vi postfix_recipient_restrictions.cf
Under “reject_unauth_destination” we want to add the line “check_client_access hash:/opt/zimbra/conf/postfix_rbl_override” So what you should end up with is the file that looks like;reject_unauth_destination check_client_access hash:/opt/zimbra/conf/postfix_rbl_override reject_unlisted_recipient
Once this has been done you are in business however you should probable run zmmtactl restart to be safe.