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.