Re: Behavior of postscreen_access_list = static:retry

2012-01-31 Thread Mark Alan
On Mon, 30 Jan 2012 19:17:17 -0500 (EST), Wietse Venema wie...@porcupine.org wrote: Mark Alan: Would the following be an acceptable way to do it? postconf -e 'postscreen_access_list = reject' postconf -e 'soft_bounce = yes' Only if this is documented. The soft_bounce

Re: Behavior of postscreen_access_list = static:retry

2012-01-31 Thread Noel Jones
On 1/31/2012 4:36 AM, Mark Alan wrote: On Mon, 30 Jan 2012 19:17:17 -0500 (EST), Wietse Venema wie...@porcupine.org wrote: Mark Alan: Would the following be an acceptable way to do it? postconf -e 'postscreen_access_list = reject' postconf -e 'soft_bounce = yes' Only if this is

Re: Behavior of postscreen_access_list = static:retry

2012-01-31 Thread Wietse Venema
Mark Alan: On Mon, 30 Jan 2012 19:17:17 -0500 (EST), Wietse Venema wie...@porcupine.org wrote: Mark Alan: Would the following be an acceptable way to do it? postconf -e 'postscreen_access_list = reject' postconf -e 'soft_bounce = yes' Only if this is documented. The

Re: Behavior of postscreen_access_list = static:retry

2012-01-31 Thread Mark Alan
On Tue, 31 Jan 2012 06:17:39 -0600, Noel Jones njo...@megan.vbhcs.org wrote: You need to set both postscreen_blacklist_action = drop and soft_bounce = yes. The soft_bounce changes the 521 hangup into a 421 hangup. Thank you Noel, If we wanted a mere 4.x.x hangup, it would be more elegant to

Re: Behavior of postscreen_access_list = static:retry

2012-01-31 Thread Wietse Venema
Mark Alan: It did not imagine that it would be so difficult to configure postscreen/postfix to achieve such a simple specification. The hardest part of support on this mailing list is to get a precise spec that does not conflict with itself. Once we have that, configuration is not hard at all.

Re: Behavior of postscreen_access_list = static:retry

2012-01-30 Thread Viktor Dukhovni
On Mon, Jan 30, 2012 at 09:03:39PM +, Mark Alan wrote: Regarding the config option: postscreen_access_list = static:retry Where is retry documented as a valid access list keyword? 3) the similar syntax of 'transport_maps = static:retry' The transport table is not access(5) table, and

Re: Behavior of postscreen_access_list = static:retry

2012-01-30 Thread Mark Alan
On Mon, 30 Jan 2012 21:50:52 +, Viktor Dukhovni postfix-us...@dukhovni.org wrote: On Mon, Jan 30, 2012 at 09:26:42PM +, Mark Alan wrote: Is there any other way to make the postscreen/postfix combination temporarily defer all incoming emails with '450 4.3.2 Service currently

Re: Behavior of postscreen_access_list = static:retry

2012-01-30 Thread Wietse Venema
Mark Alan: Would the following be an acceptable way to do it? postconf -e 'postscreen_access_list = reject' postconf -e 'soft_bounce = yes' Only if this is documented. The soft_bounce parameter is listed on the postscreen(8) manpage, this is perhaps a sufficient promise to