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?
cat mm_cfg.py # -*- python -*-
# Copyright (C) 1998,1999,2000,2001,2002 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
"""This module contains your site-specific settings.
The complete set of distributed defaults, with documentation, are in the file Defaults.py. In mm_cfg.py, override only those you want to change, after the
from Defaults import *
line (see below).
Note that these are just default settings; many can be overridden via the administrator and user interfaces on a per-list or per-user basis.
"""
############################################### # 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 """
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)
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@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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)
I understand that, but it didn't seem to work that way, I will test it again.
So here is my snip of mm_cfg.py, my concern is that my "mailhost" is mydomain.district.edu, but my DEFAULT_URL_HOST (I believe) is mailmanserver.mydomain.district.edu doesn't this setting set it to mydomain.district.edu?
################################################## # Put YOUR site-specific settings below this line. IMAGE_LOGOS = '/images/' DEFAULT_EMAIL_HOST = 'mydomain.district.edu' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) DEFAULT_MSG_FOOTER = """_______________________________________________ %(real_name)s mailing list %(real_name)s@%(host_name)s http://server.mydomain.district.edu/staff/mailing """ DEFAULT_DIGEST_FOOTER = DEFAULT_MSG_FOOTER
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@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Knabe, Troy wrote:
<snip>
No. What that setting says that the email domain for a list in the 'mailmanserver.mydomain.district.edu' web domain is 'mydomain.district.edu'.
The default web domain is still DEFAULT_URL_HOST.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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)
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@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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)
I understand that, but it didn't seem to work that way, I will test it again.
So here is my snip of mm_cfg.py, my concern is that my "mailhost" is mydomain.district.edu, but my DEFAULT_URL_HOST (I believe) is mailmanserver.mydomain.district.edu doesn't this setting set it to mydomain.district.edu?
################################################## # Put YOUR site-specific settings below this line. IMAGE_LOGOS = '/images/' DEFAULT_EMAIL_HOST = 'mydomain.district.edu' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) DEFAULT_MSG_FOOTER = """_______________________________________________ %(real_name)s mailing list %(real_name)s@%(host_name)s http://server.mydomain.district.edu/staff/mailing """ DEFAULT_DIGEST_FOOTER = DEFAULT_MSG_FOOTER
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@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Knabe, Troy wrote:
<snip>
No. What that setting says that the email domain for a list in the 'mailmanserver.mydomain.district.edu' web domain is 'mydomain.district.edu'.
The default web domain is still DEFAULT_URL_HOST.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Knabe, Troy -
Mark Sapiro