On Mon, 02 Jan 2012 16:14:56 -0600, Anton Melser <melser.anton@xxxxxxxxx> wrote:
In a nutshell, one client = one IP = one reputation = many MTAs (for redundancy and capacity and for no other reason) is the goal.
One client - one IP is NOT the method promoted by mailchimp, the service you said is an example of what you are doing. From the mailchimp.com page you referred me to (http://blog.mailchimp.com/should-you-send-from-a-dedicated-ip-address/): "[ISPs' spam filters give low ranking to new IPs that suddenly send a large volume of email.] To try to offset the high volume from this new IP, we take huge chunks of their campaign and distribute those across our shared IPs. Only a small fraction of this customer’s email is actually being sent from this dedicated IP during the break-in period. But as you can see, for some filters, it’s still risky looking. And so you get delivery problems for a while. So long as the volume stays somewhat consistent, and so long as spam complaints stay within acceptable thresholds, their dedicated IP will make its way to “Trusted.” Actually, it’ll go to “neutral” for a while, then trusted." I think the above makes it very clear why I understood that your service seeks to send out email for customers with source IPs *other* than the customers' own IP, at least during the IPs "break-in period". Now you explain what you are really trying to do is provide mail server redundancy. You can do that easily and cheaply with DNS failover. But that is off-topic. I must not understand the solution you have in mind, because I can't see how NAT could be of any help. -- Lloyd -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
