Re: mynetworks hash issue

2013-10-07 Thread Viktor Dukhovni
One more thing to keep in mind. When used with mynetworks, as I already explained the RHS of the table entries is ignored. Therefore, your attempt at a reject rule: 10.147.11.11 reject is completely ineffective. If you want to use CIDR rules with exceptions to define trusted clients, you

Re: mynetworks hash issue

2013-10-07 Thread Viktor Dukhovni
On Mon, Oct 07, 2013 at 03:34:38PM -0600, Blake Farmer wrote: > Method 1 > [root@relay01 postfix]# grep cidr main.cf > cidr = cidr:${config_directory}/ > mynetworks = ${cidr}mynetworks.cidr > #mynetworks = cidr:/etc/postfix/mynetworks.cidr The above is broken. http://www.postfix.org/post

Re: mynetworks hash issue

2013-10-07 Thread Blake Farmer
I tried that method verbatium without success, postfix is able to start without issue however it continues to reject the machines I am using to test access and denied access. Your recomendation I beleive assigns the path and file designation to the variable cidr when then continues to the next

Re: mynetworks hash issue

2013-10-07 Thread Viktor Dukhovni
On Mon, Oct 07, 2013 at 01:06:59PM -0600, Blake wrote: > I tried Victor's soltuion adding the code he noted however postfix would > fail to reload or restart generating the following errors. > Oct 7 12:47:32 relay01 postfix[22897]: warning: macro name syntax error: > "/etc/postfix/" Your setting

Re: mynetworks hash issue

2013-10-07 Thread Wietse Venema
Blake: > 10.147.11.0/24 4 As Victor noted, the form 10.147.11.0/24 does not work with indexed files. This also written in the access(5) manpage. If you must use this, use cidr: format instead. Wietse

Re: mynetworks hash issue

2013-10-07 Thread Blake
Thank you to Victor & Wietse for your response. I thought the mynetworks parameter was the issue in terms of rejecting clients from access. I tried Victor's soltuion adding the code he noted however postfix would fail to reload or restart generating the following errors. Oct 7 12:47:32 relay01 p

Re: mynetworks hash issue

2013-10-07 Thread Viktor Dukhovni
On Mon, Oct 07, 2013 at 09:12:41AM -0600, Blake wrote: > However when I check the config after restarting or reloading postfix the > parameter does not seem to be updated when reviewing postconf -d. Not surprising, "postconf -d" returns compiled-in defaults as documented. This allows you to quic

Re: mynetworks hash issue

2013-10-07 Thread Wietse Venema
Blake: > mynetworks = hash:/etc/postfix/network_table > > # postmap -s hash:/etc/postfix/network_table > 11 10.147.9.0/24 That is backwards. The IP address is the lookup key. Wietse