-- generated message --

postconf.5.html has been updated:

*** /tmp/postconf.5.html.orig	2012-03-04 20:52:00.000000000 +0100
--- /tmp/postconf.5.html	2012-03-03 15:02:00.000000000 +0100
***************
*** 12423,12443 ****
  
! <dd> A safety net for testing. When "<a href="postconf.5.html#warn_if_reject">warn_if_reject</a>" is placed
! before a reject-type restriction, access table query, or
! <a href="postconf.5.html#check_policy_service">check_policy_service</a> query, this logs a "reject_warning" message
! instead of rejecting a request (when a reject-type restriction fails
! due to a temporary error, this skips any implicit "<a href="postconf.5.html#defer_if_permit">defer_if_permit</a>"
! actions that would normally prevent mail from being accepted by
! some later access restriction). This feature has no effect on
! conditional (defer_if_) restrictions.  </dd>
! 
! <dt><b><a name="warn_if_permit">warn_if_permit</a></b></dt>
! 
! <dd>Another safety net for testing. When "<a href="postconf.5.html#warn_if_permit">warn_if_permit</a>" is placed
! before a permit-type restriction, access table query, or
! <a href="postconf.5.html#check_policy_service">check_policy_service</a> query, this logs a "permit_warning" message
! instead of permitting a request (when a permit-type restriction
! fails due to a temporary error, this skips any implicit "<a href="postconf.5.html#defer_if_reject">defer_if_reject</a>"
! actions that would normally prevent mail from being rejected by
! some later access restriction).  <br> This feature is available in
! Postfix 2.10 and later.  </dd>
  
--- 12423,12429 ----
  
! <dd>Change the meaning of the next restriction, so that it logs
! a warning instead of rejecting a request (look for logfile records
! that contain "reject_warning"). This is useful for testing new
! restrictions in a "live" environment without risking unnecessary
! loss of mail. </dd>
  

