Avatar

Level 6

Never setup 1 IP per affinity... You need at least 2 per affinity
An "affinity" is a dedicated pool of IPs that will be used for dedicated sendings (see

 doc from Anshar)

Why never using just one? In case you have a deliverability issue with it, you'll then lose all your delivery messages.
You have to calculate the amount of IPs you'll need dedicated per use.
For example, imagine you have some sendings dedicated for China and others dedicated for Europe.
You'll then need at least 2 affinities: one for China, one for Eu.
Generally speaking, an IP can deliver up to 150K emails per hour with a really good warm up for reputation and following deliverability best practices.
As china ISPs are different from Europe ones, you'll then prefer to dedicate a pool of IP specially for China and another one specially for Europe. To isolate those both pools will permit you to isolate also any issue that occurs on one pool from the other and let you warm up efficiently your IP reputation.
But now, you know that you send 2 millions of emails between 10am and 12am for China and 1 million for Europe.
It means, that you'll then need 1 million per hour for China (so 7 ips) and 500K for Europe (so 4 ips)
you'll then create your China affinity containing 7 ips and Europe affinity with only 4

if you want to know which Ips had mostly an issue (generally this is not just one but the all pool), you can extend the broadlogRcp schema in order to add the "publicId" that you'll declare in the config-instance.xml file