If you're changing things rather than just adding, try putting VIRTUAL_HOSTS.clear() ahead of your mm_cfg.py entries.

That was the first thing I tried. Just to make sure this isn't something weird. I am seeing this on the site wide mailing list mailman. I haven't tried other mailing lists yet.

Thanks

emd

Mark Sapiro wrote:

Erin Dalzell wrote:

...

...

If you're changing things rather than just adding, try putting VIRTUAL_HOSTS.clear() ahead of your mm_cfg.py entries.

That was the first thing I tried. Just to make sure this isn't something weird. I am seeing this on the site wide mailing list mailman. I haven't tried other mailing lists yet.

It's hard to say what might be happening without knowing what exactly you're doing in mm_cfg.py, but some things which are set in Defaults.py are also used in Defaults.py. Thus simply changing the setting in mm_cfg.py isn't enough, you also have to redo (maybe after undoing) the usage.

The most obvious example is DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST. These are set in Defaults.py and then used in Defaults.py in

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

Thus if either or both is changed in mm_cfg.py, the

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

must be repeated after the change, or to be completely sure, clear the existing entries and then re-add as in

VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

If you're still having problems, please provide the contents of your mm_cfg.py and a description of the actual problem behavior.

MTA = "Postfix" IMAGE_LOGOS = '/icons/' VIRTUAL_HOSTS.clear() add_virtualhost('www.thedalzells.org')

My process is:

• change the file
• Run fix_url
• restart mailman

The problem is that the links on the site-wide Mailman list aren't changed to whatever I have the the add_virtualhost call.

So I have made the changes in Defaults.py, which you are not supposed to do.

Thanks

emd

I would do the following:

Put Defaults.py back to it's original state.

Put the following in mm_cfg.py

MTA = "Postfix" IMAGE_LOGOS = '/icons/'

DEFAULT_URL_HOST = 'www.thedalzells.org' DEFAULT_EMAIL_HOST = 'thedalzells.org'

VIRTUAL_HOSTS.clear() add_virtualhost('www.thedalzells.org')

The last could equally well be add_virtualhost(DEFAULT_URL_HOST) or add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) as all three are equivalent in this case.

Then do

bin/withlist -l -a -r fix_url

and finally restart mailman.

If this doesn't work, then I don't know what's going on.

That worked. I think the adding of the virtual hosts just allows the list to be accessed through that URL. But by default it sets everything to the default ones. That must be it.

Thanks

emd

In a flurry of recycled electrons, Mel Sojka wrote:

Just a suggestion folks. I have been using mailman since it was the new kid on the block and it is truly a fantastic package, but since series 2.1 at least once a week the VIRTUAL_HOSTS issue hits the users list.
[...] someone to create a VIRTUAL_HOSTS howto , even the notes in the FAQ are a bit vague. If nothing else this may make life a bit easier for the answer guys.

Having just (still) gone (going) through the virtual hosts/lists dance... I was actually planning on writing up my experiences for this list. Could become a FAQ....

In the short form: AFAICT, none of the published patches work out of the box on 2.1.5 (I've been patching the patches). It -does- matter how you postfix setup is configured. There aren't any decent explanations of which foot bone connects to which ankle bone, and how list names change in the process. There are few, if any, patches for the ./bin utilities to do the right thing with virtual lists. I've already patched list_lists for that, and may get to the others RSN.

Oh, ya. check_perms doesn't seem to report that the alias file isn't owned by mailman.

z!