jkoral@luc.edu wrote on 2025-07-22 11:11:
we would really like to use both lists.luc.edu and listservnew.luc.edu. Is that possible?
It is possible, and since it's impossible to get 100% of users to update all future mail to the new list, it's desirable.
Is the old server still handling mail for your domain in any capacity? Depending on how mail is routed would determine where the following stuff would go.
On the server's postfix settings, in a canonical mapping file (aka $your_file_name), something like this (from my new server):
## talk mailing list talk@gtalug.org talk@lists.gtalug.org ## talk-admin@gtalug.org talk-admin@lists.gtalug.org talk-bounces@gtalug.org talk-bounces@lists.gtalug.org talk-confirm@gtalug.org talk-confirm@lists.gtalug.org talk-join@gtalug.org talk-join@lists.gtalug.org talk-leave@gtalug.org talk-leave@lists.gtalug.org talk-owner@gtalug.org talk-owner@lists.gtalug.org talk-request@gtalug.org talk-request@lists.gtalug.org talk-subscribe@gtalug.org talk-subscribe@lists.gtalug.org talk-unsubscribe@gtalug.org talk-unsubscribe@lists.gtalug.org
Be sure to add entries for each list migrated from old to new list.
And be sure to run postmap $your_file_name after creating this file.
In /etc/postfix/main.cf, need to include a reference to $your_file_name something like this:
## BC_RON: redirect mail to, say, talk@gtalug.org to ## talk@lists.gtalug.org: ## ## Invoke the mm2 line when decommissioning Mailman v2 on old server: recipient_canonical_maps = hash:/etc/postfix/recipient_canonical.map, hash:/etc/mailman3/mm2_to_mm3_gtalug.org_to_lists.gtalug.org.map
I found I also had to configure "Acceptable aliases" in "Message Acceptance" in each list's Settings for it to not reject mail to old address with "Implicit destination" errors.
All that should get you pointed in the right direction...