-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christian Schoepplein wrote:

What do I have to set in mm_cfg-py to enable personalisation by default for new lists (not full personalisation). In listconfigs i saw, that

personalize = 1

would be the thing to set, but is it possible to use this setting in mm_cfg.py?

I don't know that this would work. Looking at Mailman/MailList.py, it looks like personalize is always initialized to 0. This probably isn't the right way to handle it, but just for fun I changed MailList.py and added a DEFAULT_LIST_PERSONALIZATION variable to mm_cfg.py. If both that and OWNERS_CAN_ENABLE_PERSONALIZATION are non-zero, then personalize picks up that value. Otherwise, it gets set to 0. Here's the small patch I made to Mailman/MailList.py: - --- Mailman/MailList.py~ Tue Sep 30 16:56:33 2003 +++ Mailman/MailList.py Mon Dec 1 14:35:20 2003 @@ -340,7 +340,10 @@ self.filter_action = mm_cfg.DEFAULT_FILTER_ACTION # Analogs to these are initted in Digester.InitVars self.nondigestable = mm_cfg.DEFAULT_NONDIGESTABLE - - self.personalize = 0 + if mm_cfg.OWNERS_CAN_ENABLE_PERSONALIZATION and mm_cfg.DEFAULT_LIST_PERSONALIZATION: + self.personalize = mm_cfg.DEFAULT_LIST_PERSONALIZATION + else: + self.personalize = 0 # New sender-centric moderation (privacy) options self.default_member_moderation = \ mm_cfg.DEFAULT_DEFAULT_MEMBER_MODERATION - -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp ====================================================================== The average woman would rather be beautiful than smart because the average man can see better than he can think. --Unknown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE/y56yuv+09NZUB1oRAsVbAJsFxETqTaesrsmamXRFgVA+LguTGgCeJjes treH5dSQt0L5aVfYm925GvI= =66M4 -----END PGP SIGNATURE-----