On Thu, Jul 9, 2009 at 8:28 AM, Jon<[email protected]> wrote: > Looking for some clarification to help me understand. Are > smtpd_*_restrictions processed in this order: > > smtpd_client_restrictions > smtpd_helo_restrictions > smtpd_sender_restrictions > smtpd_recipient_restrictions > smtpd_data_restrictions >
I am no expert but that order has been previously stated in this mail group. > > > If these restriction mechanisms share a common hash file for their check, > for example: > > /etc/postfix/main.cf > ... > smtpd_client_restrictions = check_client_access > hash:/etc/postfix/access_hash ... > ... > smtpd_sender_restrictions = check_sender_access > hash:/etc/postfix/access_hash ... > ... That I do not know. In the systems I started working with (already established and running) separate hash files are used for each. > > /etc/postfix/access_hash > ip.ad.dre.ss ok > tld.com REJECT Access denied > > would this OK if found in smtp_client_restrictions trump REJECT if found by > smtpd_sender_restrictions against tld.com and allow the message to queue? > > -- Robert Lopez Unix Systems Administrator Central New Mexico Community College (CNM) 525 Buena Vista SE Albuquerque, New Mexico 87106
