What a week! We've added powerful dedicated IP management tools, improved stats comparisons, and made it easier to troubleshoot webhooks.
Dedicated IP Management
Dedicated IPs give you a lot of control over your sender reputation, but they also require more careful management as your traffic starts growing beyond what a single IP can handle. Without warmup, a new IP can experience delivery problems, even if you haven't changed anything else about your email.
To make it easier to transition to using a dedicated IP, or multiple IPs, we've added an automatic IP warmup feature. When you purchase a new dedicated IP, you can choose to start warming it up immediately. With automatic warmup, Mandrill starts sending a tiny percentage of your email over the new IP, and slowly ramps that volume up over the next 30 days. If you only have one dedicated IP, we'll continue to send some of your mail over shared IPs until the month passes and your IP is fully warmed up - we do this because our shared IPs are already warmed up enough to send huge amounts of email daily.
You can also switch an existing dedicated IP into warmup mode at any time, which is useful if you want to reduce the traffic that an IP is sending and then slowly ramp it back up over time.
Custom Date Ranges for Stat Comparisons
In the initial rollout for stats comparison, we automatically used a 14-day window for comparing filters. Starting this week, you can specify a custom date range for your report based on the type of filter you have set up. If you have a search query, you can go back 30 days, and if you only use tags, the date ranges can go back indefinitely. This is a great way to compare your major tags to each other at a glance.
More Webhook Debugging and Management
We've added a bunch of tools to webhooks to make it easier to test and monitor their status once things go live. Some problems don't show up in testing, and it can be hard to log and debug things on production. Expanded debugging support for failed webhook batches gives you detailed batch info to help replicate and test problems.
For the cases where you know why a batch is failing, but you either aren't able or don't want to fix the problem, the new "give up" button lets you stop the retry cycle for the batch and frees your webhook for receiving new events.
Click the "view batch" button to see exactly what data Mandrill tried to send to your server, the headers we used, and an easy curl command that you can use to emulate the request yourself.