Remove redundant information.

Reformat general recommendations.

Include information on local recip rejection codes as given by Walter
Hop in SF bug #699900.

1 files changed, 26 insertions, 24 deletions

diff --git a/README.POSTFIX b/README.POSTFIX
index 7c9c6f98e..28520e280 100644
--- a/README.POSTFIX
+++ b/README.POSTFIX
@@ -9,21 +9,33 @@ GENERAL SETUP INFORMATION
     Postfix installation.  As of this writing I've tested it with
     Postfix 19991231 up to pl13, and with 200010228 up to pl08.
 
-    It is recommended that you set "owner_request_special = no" in
-    your main.cf config file so that Postfix won't treat -owner and
-    -request addresses specially (we want Postfix to simply deliver
-    such messages to the Mailman wrapper).  The default is "yes" I
-    believe.
+    By default, Postfix treats -owner and -request addresses
+    specially.  Since we want Postfix to delivery such messages to
+    Mailman, you should turn off this option by adding this to your
+    main.cf file:
+
+        owner_request_special = no
 
     In order to support Mailman's optional VERP delivery, you will
     want to disable luser_relay (the default) and you will want to set
-    recipient_delimiter for extended address semantics.  Here, my
-    recommendations are to comment out any luser_relay value in your
-    main.cf and just go with the defaults.  Also, set
-    "recipient_delimiter = +" so that the symbol used to separate an
-    address from its extended semantics is a + sign.  This will work
-    well with the default values for VERP_FORMAT and VERP_REGEXP in
-    Defaults.py.
+    recipient_delimiter for extended address semantics.  You should
+    comment out any luser_relay value in your main.cf and just go with
+    the defaults.  Also, add this to your main.cf file:
+
+        recipient_delimiter = +
+
+    Using + as the delimiter works well with the default values for
+    VERP_FORMAT and VERP_REGEXP in Defaults.py.
+
+    When attempting to deliver a message to a non-existent local
+    address, Postfix may return a 450 error code.  Since this is a
+    non-transient error code, Mailman will continue to attempt to
+    delivery the message for DELIVERY_RETRY_PERIOD (5 days by
+    default).  You might want to set Postfix up so that it returns
+    permanent error codes for non-existent local users by adding the
+    following to your main.cf file:
+
+        unknown_local_recipient_reject_code = 550
 
     Finally, if you are using Postfix-style virtual domains, read the
     section on virtual domain support below.
@@ -85,16 +97,6 @@ INTEGRATING POSTFIX AND MAILMAN
       alias_maps = hash:/etc/postfix/aliases,
           hash:/usr/local/mailman/data/aliases
 
-    - There are two other Postfix options that you probably want to
-      set.  To stop Postfix from doing anything special with -owner
-      addresses, you'll want to set the owner_request_special
-      variable.  If you plan on doing personalization (VERP), you'll
-      want to set the recipient_delimiter variable.  Here are settings
-      for the default Mailman settings:
-
-        recipient_delimiter = +
-        owner_request_special = no
-
     - When you configure Mailman, use the --with-mail-gid=mailman
       switch (actually, this will be the default if you configured
       Mailman after adding the `mailman' owner).  Because the owner of
@@ -108,7 +110,7 @@ INTEGRATING POSTFIX AND MAILMAN
     that it will take about a minute for Postfix to notice the change
     to the aliases.db file and update its tables.  I consider this a
     minor inconvenience.
-  
+
 
 VIRTUAL DOMAINS
 
@@ -170,7 +172,7 @@ VIRTUAL DOMAINS
     breaking the delivery of any dom1.ain mailing list.
 
     However, you would include dom2.ain and dom3.ain in mm_cfg.py:
-    
+
         POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dom2.ain', 'dom3.ain']
 
     Now, any list that Mailman creates in either of those two domains,