I don’t want to go in the cart - I feel fine.*

I just passed Ben (MailChimp's CEO) on the stairs. All I heard was him chanting "blog post, blog post, blog post."

"When are you going to update the Mandrill blog?" "What are you guys working on?" "Is Mandrill dead?"

No, Mandrill isn't dead - it's very much alive. But, see, that last blog post that Chad made? It's sort of a hard act to follow. We've been busy adding new features and beefing up functionality but few of these features seemed to warrant a full blog post. Plus, the Mandrill blog is sort of a nerd's blog, which means code and the command line and...well, more on that later. Time to rip off the band-aid. Here's a little bit of what we've been up to:

  • Launched a shiny new (responsively-designed) website. To coincide with the website launch, Mandrill quietly left public beta. Internally, Mandrill sent MailChimp's transactional emails for months and we were confident in removing the 'beta' label. We've been steadily growing in both users and email volume through the summer.

  • Created the Mandrill Heroku add-on (now in public beta) and launched five official API client libraries.

  • Added support for inbound email processing so you can configure a webhook to process inbound email for your app or website.

  • Added graphs when you search or filter outgoing activity to visualize deliveries, bounces, rejects, opens and clicks. Check out the top of the Outbound Activity page to see the graphs in addition to the activity log.

  • We found that a lot of people were using Mandrill for their personal email. Something kept coming up over and over: if they sent an email to a group of people, like co-workers, no one could see who else got the email or use 'reply-all' to continue a group conversation. We added a feature to allow you to preserve the recipients in the 'To:' and 'CC:' fields when you send to more than one recipient so everyone who gets your email can see who else it was sent to, and reply to everyone at once. Head to the Sending Options page in your Mandrill account to set the default behavior, or specify on a per-message basis through the API or custom SMTP headers.

  • Some users wanted to be able to audit the content being sent by Mandrill without sending a copy of every email to someone on their team. You can now view the contents of emails sent through your Mandrill account for 24 hours after the email is sent (just look for the 'view content' link on the Outbound Activity page in your account).

  • Custom message metadata has been available for awhile, but we added the ability to specify per-recipient metadata and use mustache templates to customize the display of metadata in your Mandrill account.

Of course there are probably a lot of things that didn't make this short list and we've still got more in the works. Stay tuned here and via Twitter for more updates (and I promise, it won't be months between posts going forward!).

*Obligatory Monty Python reference