Advanced dedicated IP addresses: edge cases, scale, and monitoring

This guide assumes dedicated IP addresses is already deployed and passing. It covers what breaks at scale and how mature teams operate it.

Edge cases that break a working setup#

• Buying a dedicated IP for a small list and letting it go cold.
• One dedicated IP for everything, so a promo blast delays receipts.
• Mail forwarded through mailing lists or personal forwarders, which alters headers and content.
• Acquisitions and rebrands that introduce domains nobody audited.
• Vendors silently changing their sending infrastructure.

Operating it as infrastructure#

1. Assign an owner for each sending domain and each vendor relationship.
2. Put DNS records under version control or a change-review process.
3. Alert on authentication pass rate drops and reputation changes, not just outages.
4. Run a quarterly audit against the setup steps below.
5. Document runbooks for the three most common failures.

Reference: the baseline setup#

1. Estimate steady daily volume; below roughly 50,000 per day, shared pools usually perform better.
2. If dedicated, warm up over 4 to 6 weeks and keep volume consistent.
3. Separate transactional and marketing onto different IPs or pools.
4. Monitor SNDS and Postmaster Tools per IP.

Frequently asked questions#