On 02/04/2011 11:53 AM, J4K wrote: > On 02/04/2011 11:45 AM, Stan Hoeppner wrote: >> J4K put forth on 2/4/2011 4:20 AM: >> >>> Back to the Stan's pcre file:- I've been running through the logs for >>> rejects specifically caused by this file (or prepends). However I did >>> not see any. Is there a string I could search for, >> Try: >> ~$ egrep "Dynamic - Please|Generic - Please|X-GenericStatic" /your/mail/log >> >>> and how could I white >>> list IPs instead of editing the pcre file? >> Whitelisting in Postfix is simply using an access table with an accept rather >> than reject action. See man 5 access. Example: >> >> smtpd_recipient_restrictions = >> permit_mynetworks >> reject_unauth_destination >> check_recipient_access cidr:/etc/postfix/whitelist >> check_reverse_client_hostname_access pcre:/etc/postfix/fqrdns.pcre >> ... >> ... >> >> /etc/postfix/whitelist >> >> 10.1.2.3 OK >> 10.2.3.4 OK >> 192.168.0.0/16 OK >> > Ahh this better: > # egrep "Dynamic - Please|Generic - Please|X-GenericStatic" > /var/log/mail.log | wc -l > 180 > > Thank-you for the example. Can the /etc/postfix/whitelist be an empty file? Answering my own question:-
# ls -l /etc/postfix/whitelist -rw-r----- 1 root root 0 Feb 4 11:53 /etc/postfix/whitelist Feb 4 11:53:17 logout postfix/smtpd[9365]: fatal: open /etc/postfix/whitelist: No such file or directory Nope, it cannot. I added a random 10.1.2.3 OK and it worked.
