[Mailman-Users] subscribed address that forwards to secondary address can't be identified

[Mark Sapiro]

On 04/07/2014 12:24 PM, Christopher Adams wrote:
> 
> I may be missing something, but I don't see anything under 'Non-digest
> options' for enabling Personalization. Does it just refer to custom
> headers, footers, etc? It seems that you can do that anyways without the
> setting allowing Personalization in mm_cfg.py. Also, when enabling
> something in mm_cfg.py, the guidelines say to use 1=true/yes, but then I
> see it looking something like the following. Maybe this is part of the
> problem. I would appreciate some clarification. Thank you.
> 
> VERP_PERSONALIZED_DELIVERIES = Yes
> 
> OWNERS_CAN_ENABLE_PERSONALIZATION = Yes


If you have set

OWNERS_CAN_ENABLE_PERSONALIZATION = Yes

in mm_cfg.py, the second setting under Non-digest options should be

Should Mailman personalize each non-digest delivery? This is often
useful for announce-only lists, but read the details section for a
discussion of important performance issues.
(Details for personalize)
	
No
Yes
Full Personalization

These additional replacements for msg_header and msg_footer are only
available if personalize is Yes or Full

    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.


Read the Details link for more.

Yes/No things in mm_cfg.py can be set to Yes or No as these are defined
appropriately in Defaults.py as are On and Off.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan