Does changing MX impact Mailman 2.1 processing?

Hi!
My email + mailman provider had a server crash and is migrating all mail services to a different hardware. There is a temporary SMTP server up collecting incoming mail, but they are held and not propagated until the whole system runs again.
Since that timeframe is unknown, I am thinking about pointing the MX record for the affected domain to an own cold-standby backup server.
Question: will the Mailman 2.1 on the old system, once fed with the already accepted mails, correctly deliver these to the recipients *even* if the list domain's MX record points somewhere else?
I.e. is Mailman 2.1 in any way dependent on DNS MX record resolving of its own domain *after* mail has already been accepted my an MTA?
(I do not know the details of the Mailman installation, and my provider should be the first to be asked, and I did. I'd still value a shot-in-the-dark third opinion.)
Thanks,
Florian

On 12/17/2016 01:31 AM, Florian Berger wrote:
Question: will the Mailman 2.1 on the old system, once fed with the already accepted mails, correctly deliver these to the recipients *even* if the list domain's MX record points somewhere else?
I.e. is Mailman 2.1 in any way dependent on DNS MX record resolving of its own domain *after* mail has already been accepted my an MTA?
As far as Mailman itself is concerned, it is not affected by any DNS records. If the mail gets to Mailman, it will be processed the same regardless of how it got there.
It is possible that there will be issues with mail delivery depending on how Mailman delivers outgoing mail. This would depend on the MTA that it is delivering to and what mail acceptance checks that MTA does.
This is not likely to be an issue if Mailman is delivering to an MTA on localhost.
participants (2)
-
Florian Berger
-
Mark Sapiro