[Mailman-Users] where is mailman-bounces address defined?
msapiro at value.net
Fri Jul 20 18:16:57 CEST 2007
douglas repetto wrote:
>I found the problem. The address was defined correctly in mm_config.py,
>but for some reason it was truncated in Defaults.py. I don't really
>understand the mechanism by which changes in mm_config.py are propagate
>to Defaults.py...but something went wrong!
This is subtle, but here it is. The values in Defaults.py for
DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST come from the configure
options --with-urlhost= and --with-mailhost=. Defaults.py also contains
which adds this entry to the VIRTUAL_HOSTS dictionary.
Then you put correct settings for DEFAULT_URL_HOST and
DEFAULT_EMAIL_HOST in mm_cfg.py. This overrides the settings from
Defaults.py. You may even put
in mm_cfg.py which puts the correct entry in the VIRTUAL_HOSTS
dictionary, but if the mm_cfg.py value of DEFAULT_URL_HOST is
different from the Defaults.py value, this DOES NOT remove or replace
the original entry in the VIRTUAL_HOSTS dictionary.
Thus, we suggest that whenever you change DEFAULT_*_HOST in mm_cfg.py,
DEFAULT_URL_HOST = ...
DEFAULT_EMAIL_HOST = ...
>I edited Defaults.py and restarted MM and am monitoring our logs. So far
>I don't see any more errors.
If you put all 4 of the above lines in mm_cfg.py, it wouldn't matter
what was in Defaults.py. This is a gray area as far as editing
Defaults.py is concerned. Normally, you should never edit Defaults.py
as your edits will go away if you re-install or upgrade Mailman, but
in this case, the 'error' in Defaults.py was caused by a bad configure
option which might be corrected the next time you run configure, so
it's not clearly wrong to fix Defaults.py.
Still, if you fix mm_cfg.py as above, you don't have to worry about
mis-typing the configure options.
Mark Sapiro <msapiro at value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users