> > and another > > > check_recipient_access > > pcre:/etc/postfix/MISC_CHECKS/ascii.pcre, check_sender_mx_access > > cidr:/etc/postfix/NETWORK_CHECKS/drop.cidr, check_policy_service > > inet:127.0.0.1:10023, check_helo_access > > pcre:/etc/postfix/NETWORK_CHECKS/helo_hostnames.pcre, > > pcre:/etc/postfix/EMAIL_ADDRESS_CHECKS/to_recipients_bw.regexp > > reject_non_fqdn_helo_hostname reject_invalid_helo_hostname > > See "man postmap" and the -q option to query your maps: > > postmap -q unmunged@sender.address maptype:mapname
I tried this on all the areas you pointed out but nothing came back as being a REJECT. Is this possible? I did find one rule that looked suspicious just in a manual review but changing it and running postmap again didn't make a different in terms of the reject message. Most of our reject rules are labeled except where we are blocking because of an e-mail address pattern, so I would think it was obvious if it was a rule we were using that was NOT an e-mail address block. I did not know about the postmap query mode, but now that I have run it on all the restrictive maps and come up with no matches I am more confused where this block is happening.
