On 10/07/2015 08:23 AM, Lindsay Haisley wrote: > On Wed, 2015-10-07 at 07:32 -0700, Mark Sapiro wrote: >> On 10/06/2015 08:49 PM, Lindsay Haisley wrote: >>> >>> Where in the code can I list this substitution variable so that it >>> doesn't throw this error on this page? >> >> >> Add it to the definition of PERSONALIZED_ALLOWEDS in >> Mailman/Gui/NonDigest.py. > > And then turn on OWNERS_CAN_ENABLE_PERSONALIZATION in mm_cfg.py and > enable personalization for the list, yes?
Well, I assumed you'd already done that since I don't see how you can include a recipient unique token in the msg_footer if delivery isn't personalized. However, all you need is for the list's delivery is to be personalized. Whether you accomplish this by turning on OWNERS_CAN_ENABLE_PERSONALIZATION and setting personalize via the GUI or setting personalize some other way, e.g. via withlist, that's all you need. If for some reason you're not personalizing, but ensuring a single recipient per SMTP transaction by setting VERP_DELIVERY_INTERVAL = 1 then yes, you would need to either set the list's personalize attribute non-zero or you could add your variable name to ALLOWEDS in Mailman/Gui/Digest.py, but setting personalize is the right way to do it. If the list's delivery is not personalized and VERP_DELIVERY_INTERVAL is or becomes unequal 1 (and SMTP_MAX_RCPTS is unequal 1) you will wind up decorating multiple recipients messages with the same data. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
