DevHeads.net

temp avoiding RBL block with client_checks OK?

one of the users is waiting for an email from server currently listed on
<a href="http://www.dnsbl.manitu.net/lookup.php?value=203.12.160.162" title="http://www.dnsbl.manitu.net/lookup.php?value=203.12.160.162">http://www.dnsbl.manitu.net/lookup.php?value=203.12.160.162</a>

chances are it might get fixed in 12 hours, or, maybe not

short of removing dnsbl.manitu.net from my RBL checks, is there a way to
'bypass' this current predicament, and, allow mails from the IP/host?

can I simply put IP ? hostname ? both ? in /etc/postfix/client_checks ?

or is it /etc/postfix/sender_checks ? as so:

203.12.160.162 OK
mail12.tpgi.com.au OK

from main.cf:

Comments

Re: temp avoiding RBL block with client_checks OK?

By Dominic Raferd at 02/13/2018 - 06:18

For use within restriction list(s):
check_client_access is for checking the purported address, or the ip, of
the incoming connecting client
check_sender_access is for checking the MAILFROM address (envelope sender)
check_helo_access is for checking the HELO/EHLO response name

For use outside restriction list(s): (hence later/slower)
header_checks can be used for checking email headers - including the
'From:' header address (which may well be different to the MAILFROM
address).

In your case you can put either the ip or the client address onto a new
line in the file referenced by check_client_access, followed by ' OK', and
then postmap it afterwards. You might want to add ​tpgi.com.au rather
than ​mail12​​.tpgi.com.au (assuming smtpd_access_maps is listed in
parent_domain_matches_subdomains, which is the default case).

Yes it is a little confusing at first...

Re: temp avoiding RBL block with client_checks OK?

By Voytek Eymont at 02/13/2018 - 07:43

On Tue, February 13, 2018 9:18 pm, Dominic Raferd wrote:

Dominic,

thanks both for confirming as well as explaining the details, much
appreciated

also, forgot to ask, is there some command to test such change to confirm ?

V

Re: temp avoiding RBL block with client_checks OK?

By Dominic Raferd at 02/13/2018 - 08:03

On 13 February 2018 at 11:43, Voytek < ... at sbt dot net.au> wrote:
If there is something wrong you will see the error when you do:
postmap hash:/etc/postfix/client_checks

For failsafe, make changes to a copy of client_checks in another
location and then postmap this, if no error then copy the amended
client_checks file into /etc/postfix and postmap there.

The changes will be implemented in active postfix pretty quickly after
postmap, but to force immediately do:
postfix reload