Though not a perfect solution, setting an SPF in your DNS will help. Enter something along the lines of:
v=spf1 include: mailServerDomainName.com ip4:<old_IP_Address> ip4:<new_IP_address> ~all
(obviously, change the generic entries to real values, and use IP6 addresses if appropriate. )
On Tue, Mar 27, 2018 at 6:34 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 03/27/2018 03:43 PM, Stephen J. Turnbull wrote:
My feeling is that you want to ask on Postfix channels, since I don't see a good reason to involve Mailman itself in what is really a task for the MTA. Mailman was deliberately designed to not know anything about outgoing mail except a host and port to send to.
Which brings up the point I've been meaning to post for days but it keeps slipping off the back burner and falling on the floor.
I can think of a couple of ways to hack the code in Mailman 2.1 to select a different outgoing MTA by list. It can also be done in Mailman 3 by having separate MTA configs per list, but I can't give you a recipe off hand.
But, the way I would do this is what you are presumably doing anyway. That is have separate Mailman installations on the old and new server. Then you can move the lists incrementally and gradually. Then all you need is a transport map in Postfix on the old server to route mail to the new server for the already moved lists, and then finally update DNS after all the lists are moved.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/