sitelist.cfg "personalization" setting

[Kathy Gee]

For Andy to review and advise the impact of changing this setting, if any. Not sure if this setting is overidden by the dlist stuff (though it could interact with the dlist stuff). Andy should understand whether this could be changed and what would happen.

[Andy Grover (andy-groveronline)]

You want to change it from personalization = 1 to 0? This shouldn't affect dlist, I'm pretty sure.

[Robin J (robin-jeffries)]

Kathy did you change this in the systers.org sitelist.cfg file? I'm trying to close out old bugs
-- Robin

[Kathy Gee (kathyg)]

I did not change anything here because we weren't sure what the impact on the performance will be. For reference, below is an explanation for this Personalize setting. Paragraph 2 talks about the performance and paragraph 3 talks about what each setting mean. As shown, systers.org is currently set to "Yes" or "1". Jen had requested we open a bug for this so Andy can perhaps make a recommendation and provide some insight as to how (if any) this impacts "dlist" -- Kathy

# Normally, Mailman sends the regular delivery 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.
#
# However, some lists can benefit from a more personalized approach. In
# this case, Mailman crafts a new message for each member on the regular
# delivery list. Turning this feature on may degrade the performance of
# your site, so 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.
#
# Select No to disable personalization and send messages to the members
# in batches. Select Yes to personalize deliveries and allow additional
# substitution variables in message headers and footers (see below). In
# addition, by selecting Full Personalization, the To header of posted
# messages will be modified to include the member's address instead of
# the list's posting address.
#
# When personalization is enabled, a few more expansion variables that
# can be included in the <a href="?VARHELP=nondigest/msg_header">message
# header and message footer.
#
# These additional substitution variables will be available for your
# headers and footers, when this feature is enabled:
#
# user_address - The address of the user, coerced to lower case.
# user_delivered_to - The case-preserved address that the user is
# subscribed with. user_password - The user's password. user_name - The
# user's full name. user_optionsurl - The url to the user's option page.
#
#
#
# legal values are:
# 0 = "No"
# 1 = "Yes"
# 2 = "Full Personalization"
personalize = 1

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Robin J
Sent: Saturday, March 06, 2010 3:05 PM
To: Kathy Gee
Subject: [Bug 315177] Re: sitelist.cfg "personalization" setting

Kathy did you change this in the systers.org sitelist.cfg file? I'm trying to close out old bugs
-- Robin

--
sitelist.cfg "personalization" setting
https://bugs.launchpad.net/bugs/315177
You received this bug notification because you are a direct subscriber
of the bug.

Status in Systers Mailman Custom Modifications: New

Bug description:
For Andy to review and advise the impact of changing this setting, if any. Not sure if this setting is overidden by the dlist stuff (though it could interact with the dlist stuff). Andy should understand whether this could be changed and what would happen.

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/systers/+bug/315177/+subscribe

[Robin J (robin-jeffries)]

I marked this won't fix, as I think we need to leave it as is. I haven't looked at the code for it, but I'm pretty sure that dlists uses this, and I think it's safest just not to touch this. So let's get it out of our hair