It's been a busy couple of months here at Mandrill. After a soft feature freeze in November, we've been working on scaling the application to put us on a solid footing for future growth. In the past few months, we've set up dozens of new application and database servers and migrated terabytes of data, without taking the application down for maintenance - even for a minute.
This week, we're coming out of the freeze with a handful of new features that we've been working on. We're excited about the foundational improvements that we're making, and we'll talk more about those in a future post. But for now, it's Friday, which means: features!
Rejection Blacklist Imports
We've added some additional options for importing rejection blacklist entries. It was always easy to add multiple email addresses to the rejection blacklist via the API but the UI only allowed you to add addresses one at a time. Now you can add multiple addresses at once or you can upload a text file containing a large number of addresses (each address on a separate line).
Subaccount Management Tools
Subaccounts are Mandrill's way to let you isolate the reputation and quotas for your users. Once you have more than a handful of accounts, you want more than a flat listing of subaccounts; you need to be able to target accounts that need action. To help with this, we've made some tweaks to the subaccount management interface.
The columns are now sortable, and we show the time of first send so you can easily see your largest, newest, or worst subaccounts. We've added a visual indication for subaccounts that have been paused so you can see which accounts can and can't send. In the subaccount detail view we've added a table of the most recent sends so you can easily see the account's recent activity without having to navigate to a different page. More improvements are planned for subaccount management in the coming weeks.
A while back we added the ability to resend a message that wasn't delivered. Turns out there's another reason why you might need to resend the message, and just resending it as it was originally crafted will never work. That reason is the dreaded typo. Now when you resend a message you can specify a different recipient which makes it easy to recover from this common problem.
Google Image Proxy Handling
In December, Gmail changed how they display images in the Gmail web client to proxy all image requests through a caching server. Mandrill, like most ESPs, uses an embedded invisible image in our HTML messages to track opens and provide geolocation and email client data. Since all Gmail image requests seem to come from Google rather than the recipient's browser, Mandrill can't accurately detect the location and email client used.
To improve the accuracy of this data, we now strip Gmail open requests from the geolocation stats, and we report the email client as "Gmail image proxy." We can still get accurate user browser and geolocation stats from clicks data, but not for Gmail opens. Gmail users that use a desktop email program with IMAP or POP are not affected.