Migrating from old V2 server to new V3 server. Questions.
We have figured out how to migrate from one server to another, but after removing the list from the old server, the e-mails are still trying to go there. Is there something that needs to be done in mailman so that the e-mail list will hit the new server instead? Does it just take time?
Thank you, Joe Koral
On 9/30/24 12:15, jkoral@luc.edu wrote:
We have figured out how to migrate from one server to another, but after removing the list from the old server, the e-mails are still trying to go there. Is there something that needs to be done in mailman so that the e-mail list will hit the new server instead? Does it just take time?
This is a DNS issue. You need to update the MX and/or A records for the domain to point to the new server. After that is done, it still takes time for those changes to propagate depending on the TTL of the original records.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark, thank you for the quick reply. We will most likely need to migrate the lists over a period of time. So the DNS cannot be changed at the moment. Both servers have different FQDNs. Any suggestions on what we can do?
On 9/30/24 14:34, jkoral@luc.edu wrote:
Mark, thank you for the quick reply. We will most likely need to migrate the lists over a period of time. So the DNS cannot be changed at the moment. Both servers have different FQDNs. Any suggestions on what we can do?
If lists on the old and new servers have the same posting address domain you have to configure the incoming MTA on the old (MM 2.1) server to relay mail for the migrated lists to the new server.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
That makes sense. Are there instructions on how to do this?
Then once we are done migrating to the new server, then we can just change the DNS, correct?
On 9/30/24 14:44, jkoral@luc.edu wrote:
That makes sense. Are there instructions on how to do this?
It depends on the MTA. For Postfix you probably have a set of aliases for each of the form:
mailman: "|/path/to/mail/mailman post mailman" mailman-admin: "|/path/to/mail/mailman admin mailman" mailman-bounces: "|/path/to/mail/mailman bounces mailman" mailman-confirm: "|/path/to/mail/mailman confirm mailman" mailman-join: "|/path/to/mail/mailman join mailman" mailman-leave: "|/path/to/mail/mailman leave mailman" mailman-owner: "|/path/to/mail/mailman owner mailman" mailman-request: "|/path/to/mail/mailman request mailman" mailman-subscribe: "|/path/to/mail/mailman subscribe mailman" mailman-unsubscribe: "|/path/to/mail/mailman unsubscribe mailman"
You could change these, preferably in a separate aliases file so Mailman's genaliases won't overwrite them, to
mailman: mailman@new_server mailman-admin: mailman-admin@new-server mailman-bounces: mailman-bounces@new-server mailman-confirm: mailman-confirm@new-server mailman-join: mailman-join@new-server mailman-leave: mailman-leave@new-server mailman-owner: mailman-owner@new-server mailman-request: mailman-request@new-server mailman-subscribe: mailman-subscribe@new-server mailman-unsubscribe: mailman-unsubscribe@new-server
For exim, you would need to add another Mailman router ahead of the existing one which would match only the migrated lists and specify an smtp transport which relays to the new server.
Then once we are done migrating to the new server, then we can just change the DNS, correct?
Yes
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Here is my plan for forwarding. Let me know if this looks correct. First off, I deleted the list off of the old server, so I am assuming that removed the alias as well.
-Create new alias file in /var/lib/mailman/data/ called migratedaliases (this directory is where the aliases file is currently located, but under the aliases file). -Edit /etc/postfix/main.cf and add the path to migratedaliases to alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases. After editing, it will look like this: alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases, hash:/var/lib/mailman/data/migratedaliases. -Run newaliases command to update the aliases db. -Then add the alias for the the migratedaliases file the way you posted above.
Does that make sense?
On 10/1/24 13:17, jkoral@luc.edu wrote:
Here is my plan for forwarding. Let me know if this looks correct. First off, I deleted the list off of the old server, so I am assuming that removed the alias as well.
-Create new alias file in /var/lib/mailman/data/ called migratedaliases (this directory is where the aliases file is currently located, but under the aliases file). -Edit /etc/postfix/main.cf and add the path to migratedaliases to alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases. After editing, it will look like this: alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases, hash:/var/lib/mailman/data/migratedaliases. -Run newaliases command to update the aliases db. -Then add the alias for the the migratedaliases file the way you posted above.
Does that make sense?
Yes
On 10/1/24 13:19, jkoral@luc.edu wrote:
Or can I just put the forwarding alias in /etc/aliases?
Yes.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thank you for all your help. It seems to be attempting to forward, but I don't think the new server is receiving messages. I can send out from the server, but it is just not taking delivery. Any suggestions for what I can look at. Also, this server is behind an F5 so it has a local IP address and a Virtual IP address. The virtual IP address has the fully qualified domain name.
On 10/2/24 17:32, jkoral@luc.edu wrote:
Thank you for all your help. It seems to be attempting to forward, but I don't think the new server is receiving messages. I can send out from the server, but it is just not taking delivery. Any suggestions for what I can look at. Also, this server is behind an F5 so it has a local IP address and a Virtual IP address. The virtual IP address has the fully qualified domain name.
Look at the MTA logs on both servers.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Not sure if this means anything. This is the log from old server after trying to send. I edited the FQDN and IP though. Any thoughts? I think it may be the configuration of postfix on the new server though.
Oct 2 22:26:59 listservls01 postfix/smtp[139911]: B1FD27ED: to=<test@listservnew.example.com>, orig_to=<olivertest@lists.luc.edu>, relay=listservnew.example.com[x.x.x.x]:25, delay=0.01, delays=0/0/0.01/0, dsn=4.4.2, status=deferred (lost connection with listservnew.example.com[x.x.x.x] while receiving the initial server greeting) Oct 2 22:26:59 listservls01 postfix/smtpd[139918]: disconnect from mail-northcentralusazon11020123.outbound.protection.outlook.com[52.101.193.123]
On 10/2/24 20:33, jkoral@luc.edu wrote:
Not sure if this means anything. This is the log from old server after trying to send. I edited the FQDN and IP though. Any thoughts? I think it may be the configuration of postfix on the new server though.
Oct 2 22:26:59 listservls01 postfix/smtp[139911]: B1FD27ED: to=<test@listservnew.example.com>, orig_to=<olivertest@lists.luc.edu>, relay=listservnew.example.com[x.x.x.x]:25, delay=0.01, delays=0/0/0.01/0, dsn=4.4.2, status=deferred (lost connection with listservnew.example.com[x.x.x.x] while receiving the initial server greeting)
The message is deferred. Postfix will keep trying for maximal_queue_lifetime (default 5 days).
Possible causes are a firewall on the new server blocking port 25 connects or some postfix misconfiguration on that server. Can that server receive mail at all?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
jkoral@luc.edu
-
Mark Sapiro