OWNERS_CAN_ENABLE_PERSONALIZATION: Flag which controls whether list

admins can "personalize" their mailing lists.  Personalization is a
new feature where each recipient gets their own copy of the message,
and the headers and footers can include additional information
specific to the user.  Since this can impose a greater system burden,
it must be enabled by the site administrator in order for the list
admins to see or set the option.

Note that this currently only works for regular delivery.

GLOBAL_PIPELINE: Add the "Personalize" handler module, which actually
sets the messages up for personalization.

1 files changed, 8 insertions, 0 deletions

diff --git a/Mailman/Defaults.py.in b/Mailman/Defaults.py.in
index d8b118cb3..8aa4c6a31 100644
--- a/Mailman/Defaults.py.in
+++ b/Mailman/Defaults.py.in
@@ -241,6 +241,7 @@ GLOBAL_PIPELINE = [
     'CookHeaders',
     'ToDigest',
     'ToArchive',
+    'Personalize',
     'Decorate',
     'AfterDelivery',
     'Acknowledge',
@@ -397,6 +398,13 @@ ADMINDB_PAGE_TEXT_LIMIT = 4096
 # administrator, via the command line script bin/rmlist.
 OWNERS_CAN_DELETE_THEIR_OWN_LISTS = 0
 
+# Set this variable to 1 to allow list owners to set the "personalized" flags
+# on their mailing lists.  Turning these on tells Mailman to send separate
+# email messages to each user instead of batching them together for delivery
+# to the MTA.  This gives each member a more personalized message, but can
+# have a heavy impact on the performance of your system.
+OWNERS_CAN_ENABLE_PERSONALIZATION = 0
+
 # These define the available types of external message metadata formats, and
 # the one to use by default.  MARSHAL format uses Python's built-in marshal
 # module.  BSDDB_NATIVE uses the bsddb module compiled into Python, which