I'm not sure if this is the correct forum for this question, but I'm pretty sure if there is expertise on how to do what I want to do, it can be found here.
Overview of what I am looking to do:
Due to the impending shutdown (in the next 6 months) of the data center where our mailman server lives, we are being forced to move the installation. We are going to be moving it to a different location.
Here is our problem...
Moving things is not really a problem in and of itself - I'm confident that I can get things set up correctly elsewhere. However, our email server sends somewhere around 100,000 emails per day, and if you cut over from one IP address to another IP address, my understanding is that most ISPs will start to ban you, because they are not used to that sort of volume coming from an unknown IP. I know it would be better if we could keep the IP address, but again, due to circumstances beyond my control, this is not going to be a possibility.
We have been told that "warming up" the IP is the way to go - that is, cutting over just some of the traffic a little at a time. So what I am looking for is a way for all mail on our domain to be sent to our current mailman installation, and based on some configuration (certain mailing lists?) certain emails being sent out to the list subscribers will first be forwarded to the new server and be sent from the new IP address.
Does that make sense?
Does anyone know a way that mailman/postfix can be configured to accomplish this?
Is there a different forum where I might be able to ask experts about this?
Thanks,
-Darren
I'm not sure if this is the correct forum for this question, but I'm pretty sure if there is expertise on how to do what I want to do, it can be found here.
Overview of what I am looking to do:
Due to the impending shutdown (in the next 6 months) of the data center where our mailman server lives, we are being forced to move the installation. We are going to be moving it to a different location.
Here is our problem...
Moving things is not really a problem in and of itself - I'm confident that I can get things set up correctly elsewhere. However, our email server sends somewhere around 100,000 emails per day, and if you cut over from one IP address to another IP address, my understanding is that most ISPs will start to ban you, because they are not used to that sort of volume coming from an unknown IP. I know it would be better if we could keep the IP address, but again, due to circumstances beyond my control, this is not going to be a possibility.
We have been told that "warming up" the IP is the way to go - that is, cutting over just some of the traffic a little at a time. So what I am looking for is a way for all mail on our domain to be sent to our current mailman installation, and based on some configuration (certain mailing lists?) certain emails being sent out to the list subscribers will first be forwarded to the new server and be sent from the new IP address.
Does that make sense?
Does anyone know a way that mailman/postfix can be configured to accomplish this?
Is there a different forum where I might be able to ask experts about this?
Thanks,
-Darren Hi Darren Your current IP(s) is used for correct PTR lookups, when remote mail server is decide to receive or reject your mail. So when you change your IP for outgoing mail server (or mailman, if mta on the same host such as postfix ), you must update those records in DNS. This takes some time. If you know your new IP, you may add new PTR for it and when it start resolves, just switch working services.
On 03/23/2018 10:05 AM, Darren Smith wrote:
We have been told that "warming up" the IP is the way to go - that is, cutting over just some of the traffic a little at a time. So what I am looking for is a way for all mail on our domain to be sent to our current mailman installation, and based on some configuration (certain mailing lists?) certain emails being sent out to the list subscribers will first be forwarded to the new server and be sent from the new IP address.
Does that make sense?
Does anyone know a way that mailman/postfix can be configured to accomplish this?
Is this Mailman 3 or Mailman 2.1? The Mailman side of this would be different depending on which. If it's Mailman 2.1, a better list is mailman-users@python.org <https://mail.python.org/mailman/listinfo/mailman-users>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark,
This is Mailman3.
On Mon, Mar 26, 2018 at 1:53 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 03/23/2018 10:05 AM, Darren Smith wrote:
We have been told that "warming up" the IP is the way to go - that is, cutting over just some of the traffic a little at a time. So what I am looking for is a way for all mail on our domain to be sent to our current mailman installation, and based on some configuration (certain mailing lists?) certain emails being sent out to the list subscribers will first
be
forwarded to the new server and be sent from the new IP address.
Does that make sense?
Does anyone know a way that mailman/postfix can be configured to accomplish this?
Is this Mailman 3 or Mailman 2.1? The Mailman side of this would be different depending on which. If it's Mailman 2.1, a better list is mailman-users@python.org <https://mail.python.org/mailman/listinfo/mailman-users>
-- 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/
Darren Smith writes:
We have been told that "warming up" the IP is the way to go - that is, cutting over just some of the traffic a little at a time.
AIUI the IP that receiving ADs care about is the last hop IP, ie, the source of the SMTP connection. I haven't done this myself, so take this with a grain of salt, but I would
(1) Document the new IP with an MX record for your domain, as well as A and AAAA records as appropriate. This means you'll have to configure it to MX for the whole domain, of course. You can keep the load down by giving it low priority.
(2) Set up the MTA on the Mailman host to send occasional mail via the new host. If the MTA doesn't know how to do it itself, you could do something really hacky like restart the Mailman host's MTA with different configurations at say 8am (current outgoing MX) and 5pm (new outgoing MX).
You could also do something even more hacky with the routing tables.
I don't think this really has anything to do with Mailman itself, although it probably wouldn't be hard to add code to round-robin some outgoing mail to an MTA configured to MX via the new IP.
So what I am looking for is a way for all mail on our domain to be sent to our current mailman installation,
All mail, or just the list mail?
and based on some configuration (certain mailing lists?)
I would not do this by mailing list. Some reputation systems work on tuples, ie, (target mailbox, source IP, source domain), so only the lists configured to go via new IP would "warmed up". It also seems likely that recipient domains with only a few subscribers on your lists would have unbalanced distribution across your lists, and so might be missed entirely.
certain emails being sent out to the list subscribers will first be forwarded to the new server and be sent from the new IP address.
Does that make sense?
As a strategy, yes, but how difficult to implement reliably, I don't know.
Does anyone know a way that mailman/postfix can be configured to accomplish this?
Is there a different forum where I might be able to ask experts about this?
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.
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
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/
participants (5)
-
a.matveev＠lan-project.ru -
Bill Christensen -
Darren Smith -
Mark Sapiro -
Stephen J. Turnbull