Your documentation says nothing about List-Unsubscribe, only about common unsubscribe links. You should update your documentation to reflect information about List-Unsubscribe.25 votes
It would be great if you guys would add Google Apps Script to your how-to's and code samples. Google has reduced the amount of emails many clients are able to send from their Mail API resulting in a flurry of conversation in the Google forums. One user has posted a workaround with some Google Apps Script Code that utilizes MailGun, which is how I found you.
This seems like a great little marketing niche/opportunity for you guys.
See 4th post in this thread: http://stackoverflow.com/questions/21444588/has-google-lowered-the-email-limits-for-google-apps-script8 votes
The major ISP's all seem to have special requirements when it comes to setting up DNS for MailGun. GoDaddy and 1&1 IONOS both require details which are not covered in your instructions and not commonly known by their first line support.
It took me over a week to get DNS properly configured with these two ISPs. How about either (1) getting instructions for major ISPs or (2) contacting major ISPs with your requirements or (3) giving a list of common pitfalls?3 votes
Your entire API for PHP demands that you can use Composer. However PHP is being used on a number of different platforms, amongst others, Windows, where the use of Composer is not that normal, so it would be nice, if you just had an example of a simple implementation using simply the basic PHP functionality.3 votes
While trying to figure out how to forward emails from the main domain to an external domain with the same address, I came across this article:
However, the named capture example (I.e.) is wrong, it should have a \ in front of g:
I wasn’t exactly sure where to post this, but hopefully you guys can fix the blog post!1 vote
Your API is RESTful (http request/response) but you do not provide raw HTTP request examples. You only provide examples which use cURL, C# classes, etc., which has the effect of concealing your actual API. IMO this is ridiculous that you don't actually document the API itself, which consists of HTTP/HTTPS requests and responses.
You don't need to document the responses. But I definitely need you to document example HTTP / HTTPS requests.1 vote
It would be a great service to the world, if you could provide step-by-step setup instructions for using Mailgun to programmatically send email from a web application (e.g. a PHP script) running on an AWS EC2.
[Background: In the past AWS allowed their users to send massive quantities of email spam, which resulted in AWS servers being blocked by all spam filters. The great majority of AWS users, who are not spammers, are now saddled with intolerably severe restrictions (imposed by AWS) on programmatically sending emails to their customers.]1 vote
- Don't see your idea?