This week, the Mandrill developers have been busy adding new features based in large part on what users have been requesting and where we've seen user questions. We've added extended content storage, a way to easily add unsubscribe links, more details about rejections, and (more) webhook testing.
Extend Content Storage
Not too long after Mandrill launched, a lot of users asked for a way to view the actual content being sent instead of just metadata about the messages. We added a quick option to view the contents of emails for 24 hours after an email was sent. This is generally long enough if you're doing a quick audit while testing or occasionally as you're sending more volume. For some users, though, viewing content is used for troubleshooting or to help their support teams confirm information contained in emails, so having access to the content for longer periods of time is really important.
Storing content for every email sent in the past 24 hours is a non-trivial task. It's a lot of data, and can get expensive to manage at the volumes being handled by Mandrill. Since users' preferences about how long to store the data varies, if you need a longer period of time, you can now extend the amount of time that Mandrill stores the message contents for your account to include the View Content link for up to 30 days.
Extra storage is $0.02 per thousand emails for each day that you extend the storage period. We'll bill you daily for the extra storage, so if you send 10,000 emails per day, and want to extend the storage by 3 days (so 4 days total), you'll pay $0.60 daily.
Easy Unsubscribe Links
Transactional email generally doesn't require an unsubscribe link. Why would someone want to unsubscribe from a password reset they requested, or an order confirmation email? Mandrill users send more than transactional email, though, and many want an easy way to add an unsubscribe link, and the ability to track unsubscribes in their Mandrill account. Up until now, there hasn't been an automated way to add an unsubscribe link but we added a new merge tag this week that will let you do this quickly and easily for bulk emails or templates. You'll need to provide a URL on your website where recipients will be redirected after clicking the link. Mandrill will process the unsubscribe, redirect to your URL and include a few query parameters so you can do your own processing, too, if desired. Here's more on setting up the unsubscribe link.
Reject Reason in Sending API Calls
Mandrill's Rejection Blacklist helps automatically manage spam complaints, bounces, and unsubscribes. We also found that rejected emails can be a source of confusion for users unfamiliar with the Rejection Blacklist or who are just getting started with Mandrill. We track trends and data across a lot of aspects of the application, as well as support. The entire Mandrill team (devs, too) monitor incoming requests and questions. Over the last 30 days, around 10% of our tickets included a question in some fashion about rejected emails or why an email was rejected, and it was pretty clear that we could (or should) do something to help answer this question before it got to the support team.
We've added an extra return value to the messages/send and messages/send-template API calls,
reject_reason, to tell you why the email address was added to the rejection blacklist in the first place. For successfully sent or queued messages, this will be
null, but for rejected emails, it will include why the email was rejected, such as
soft-bounce. If you're interested or want more data, you could also use the reject reason to get more information about the rejected email address.
Testing for Inbound Webhooks
About a month ago, we announced testing for webhooks. This week we added the same testing for Inbound Webhooks with sample data so you can test inbound destinations, too. It's also just a button.