Add the code that would be used if personalized digests were

supported.

1 files changed, 46 insertions, 1 deletions

diff --git a/Mailman/Gui/Digest.py b/Mailman/Gui/Digest.py
index 053e8ef52..ec08bad1c 100644
--- a/Mailman/Gui/Digest.py
+++ b/Mailman/Gui/Digest.py
@@ -29,7 +29,7 @@ class Digest:
     def GetConfigInfo(self, mlist):
         WIDTH = mm_cfg.TEXTFIELDWIDTH
 
-	return [
+	info = [
             _("Batched-delivery digest characteristics."),
 
 	    ('digestable', mm_cfg.Toggle, (_('No'), _('Yes')), 1,
@@ -79,3 +79,48 @@ class Digest:
              _('''Should Mailman send the next digest right now, if it is not
              empty?''')),
 	    ]
+
+##        if mm_cfg.OWNERS_CAN_ENABLE_PERSONALIZATION:
+##            info.extend([
+##                ('digest_personalize', mm_cfg.Toggle, (_('No'), _('Yes')), 1,
+
+##                 _('''Should Mailman personalize each digest delivery?
+##                 This is often useful for announce-only lists, but <a
+##                 href="?VARHELP=digest/digest_personalize">read the details</a>
+##                 section for a discussion of important performance
+##                 issues.'''),
+
+##                 _("""Normally, Mailman sends the digest messages to
+##                 the mail server in batches.  This is much more efficent
+##                 because it reduces the amount of traffic between Mailman and
+##                 the mail server.
+
+##                 <p>However, some lists can benefit from a more personalized
+##                 approach.  In this case, Mailman crafts a new message for
+##                 each member on the digest delivery list.  Turning this on
+##                 adds a few more expansion variables that can be included in
+##                 the <a href="?VARHELP=digest/digest_header">message header</a>
+##                 and <a href="?VARHELP=digest/digest_footer">message footer</a>
+##                 but it may degrade the performance of your site as
+##                 a whole.
+
+##                 <p>You need to carefully consider whether the trade-off is
+##                 worth it, or whether there are other ways to accomplish what
+##                 you want.  You should also carefully monitor your system load
+##                 to make sure it is acceptable.
+
+##                 <p>These additional substitution variables will be available
+##                 for your headers and footers, when this feature is enabled:
+
+##                 <ul><li><b>user_address</b> - The address of the user,
+##                         coerced to lower case.
+##                     <li><b>user_delivered_to</b> - The case-preserved address
+##                         that the user is subscribed with.
+##                     <li><b>user_password</b> - The user's password.
+##                     <li><b>user_name</b> - The user's full name.
+##                     <li><b>user_optionsurl</b> - The url to the user's option
+##                         page.
+##                 """))
+##                ])
+
+        return info