The concerns Greg has are real. For example, a little over a year ago, the server mail.python.org that hosts over 300 @python.org lists (including this one) suffered a fatal hardware error on a Friday. With much scrambling, we were able to get everything up by the next Monday on a new server in the cloud, but with a different IP.
It was several weeks before we were able to set up feedback loops and such with the various services such as AOL, Gmail, etc., which knew our prior IP and get them to accept mail from the new IP without bounces, greylisting, etc. One thing we did observe is if possible, when the ISP has an IPv6 MX, make sure your outging MTA can use it as at least some of the ISPs are more lenient about what they accept via IPv6. Also, see <https://wiki.list.org/x/4030690> about signing up for feedback loop reporting with the various ISPs. If you can do this in advance for the new IP, this will help. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
