[Mailman-Users] issues with mm_cfg.py

[Mark Sapiro]

Knabe, Troy wrote:

>This is my mm_cfg.py but it doesn't appear that mailman is utilizing it.  I had to change my DEFAULT_EMAIL_HOST in Defaults.py in order for it to take affect on install, and now I am trying to set the DEFAULT_MSG_FOOTER and it is not using this one.  Any insights?


See <http://wiki.list.org/x/mIA9>.

As for DEFAULT_MSG_FOOTER, that is the default for lists created after
you made the change. It has no effect on exisitng lists. (more below)


>cat mm_cfg.py
<snip>
>###############################################
># Here's where we get the distributed defaults.
>
>from Defaults import *
>
>##################################################
># Put YOUR site-specific settings below this line.
>IMAGE_LOGOS = '/images/'
>DEFAULT_EMAIL_HOST = 'mydomain.district.edu'
>DEFAULT_MSG_FOOTER = """_______________________________________________
>%(real_name)s mailing list
>%(real_name)s@%(host_name)s
>http://webserver.mydomain.district.edu/staff/mailing
>"""


Also, both DEFAULT_EMAIL_HOST and DEFAULT_MSG_FOOTER are used in
Defaults.py to set other things, and those things are imported before
you make your changes, so you actually need

DEFAULT_EMAIL_HOST = 'mydomain.district.edu'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
DEFAULT_MSG_FOOTER = as you have it
DEFAULT_DIGEST_FOOTER = DEFAULT_MSG_FOOTER

Otherwise, the VIRTUAL_HOSTS table will retain the Defaults.py setting
for DEFAULT_EMAIL_HOST, and similarly for DEFAULT_DIGEST_FOOTER.

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