After a few weeks rolling out some frequently requested new webhook-related features, we worked on a some less visible things to keep Mailgun new and shiny for you. Specifically, we decreased the number of queries per second on our main MongoDB instance by 50%.
Happy Friday! This week’s update is the sequel to last week where we rolled out easy testing for Routes webhooks. We’ve finished what we started and now all our webhooks have an easy to use Test feature that sends a sample webhook to a URL of your choosing for easy debugging.
Many of our customers run large-scale digital marketing applications on top of Mailgun for their own customers. For example, Vero and Userfox are email service providers that built their awesome digital marketing automation apps on top of Mailgun
Being in the API business has its challenges and maintaining the robustness of the system during peak hours is one of them. That’s why we do lots of stress testing here at Mailgun.
Last week we released a much-requested email tracking feature: domain-level webhooks. Continuing on that theme, this week we’ve released another webhook-related feature: easy testing for Routes webhooks.
In January we announced that we had partnered up with Meteor to power the email back-end that comes with the Meteor platform. To see an example, check out this event registration form we blogged about recently, but today we want to demo another example of Meteor+Mailgun integration.
This week’s main theme was webhooks and we’ve got an exciting (and much requested) new feature to announce: domain-level webooks. In addition, we’ve been focused on improving our reputation system to catch spammers and scammers before they can do their damage.
It has become clear from our support logs that a lot of developers use Action Mailer to send emails. If you are one of these developers you should know that there is one issue that we have seen repeatedly which will cause your emails to get filtered as spam by Gmail: malformed message-ID. This also may occur with other libraries but we see this issue mostly with Action Mailer.
Originally posted on April 12, 2013. This week we focused on backend improvements to make Mailgun more performant, reliable and scalable. Lots of boring stuff, but hopefully you’ll feel the difference.
This post was originally published by Jay Baird on the Rackspace DevOps blog. The Rackspace team has been using Mailgun for a variety of projects (like this one), and just open-sourced an SDK for integrating Mailgun in iOS apps.
It’s always fun chatting with customers about what they like about Mailgun (and what they’d like to see improved ).
This week, we’ve rolled out an enhancement, ok, we’ve fixed a bug, in our email parsing API, which is part of our incoming email handling system called Routes.