Migrating a list to a (Postfix) virtual host
Hey, I currently encounter the following problem: We have several mailing lists in our project, but we'll buy a new domain. The lists are currently running under our old domain. The new domain will point to the same server and will be "registered" as virtual_alias_domain in Postfix.
Is it possible to move the lists which aren't virtual hosted yet (they appear only in data/aliases) to the virtual host (so they appear additionally in data/virtual-mailman)? I searched the web but I didn't find anything helpful about this topic. The problem is that I don't want to re-create the list because it'd be good to keep the passwords and settings of the subscribers.
--Norbert
Norbert Aschendorff wrote:
It is not difficult, but requires a few steps.
- add
add_virtualhost('new.web.domain', 'new.email.domain')
and
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['new.email.domain']
to mm_cfg.py
- run Mailman's
bin/withlist -r fix_url LISTNAME -u new.web.domain
to move the LISTNAME list or run
bin/withlist -r fix_url -a -- -u new.web.domain
to do all lists.
- run Mailman's
bin/genaliases
- add
hash:/path/to/mailman/data/virtual-mailman
to virtual_alias_maps in Postfix main.cf and reload Postfix.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Yeah, sounds quite simple :)
Small question: genaliases looks at the URL in the list configuration and generates the aliases from it?
Thanks :)
Norbert Aschendorff wrote:
Small question: genaliases looks at the URL in the list configuration and generates the aliases from it?
Genaliases generates aliases for each list using only the list name. It also generates the virtual mappings (virtual-mailman) for those lists whose host_name attribute is in POSTFIX_STYLE_VIRTUAL_DOMAINS.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Another possibility (sufficient for at least my situation) came just to my mind: Adapt the list's /host_name/ and set up an alias respectively an entry in Postfix' virtuals table pointing to the list's address on the new virtual host. It's not really elegant, but it works so far.
--Norbert
Norbert Aschendorff wrote:
It is not difficult, but requires a few steps.
- add
add_virtualhost('new.web.domain', 'new.email.domain')
and
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['new.email.domain']
to mm_cfg.py
- run Mailman's
bin/withlist -r fix_url LISTNAME -u new.web.domain
to move the LISTNAME list or run
bin/withlist -r fix_url -a -- -u new.web.domain
to do all lists.
- run Mailman's
bin/genaliases
- add
hash:/path/to/mailman/data/virtual-mailman
to virtual_alias_maps in Postfix main.cf and reload Postfix.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Yeah, sounds quite simple :)
Small question: genaliases looks at the URL in the list configuration and generates the aliases from it?
Thanks :)
Norbert Aschendorff wrote:
Small question: genaliases looks at the URL in the list configuration and generates the aliases from it?
Genaliases generates aliases for each list using only the list name. It also generates the virtual mappings (virtual-mailman) for those lists whose host_name attribute is in POSTFIX_STYLE_VIRTUAL_DOMAINS.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Another possibility (sufficient for at least my situation) came just to my mind: Adapt the list's /host_name/ and set up an alias respectively an entry in Postfix' virtuals table pointing to the list's address on the new virtual host. It's not really elegant, but it works so far.
--Norbert
participants (2)
-
Mark Sapiro -
Norbert Aschendorff