Skip to content

Instantly share code, notes, and snippets.

@mkarnicki
Created February 28, 2017 22:02
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save mkarnicki/c627d6377df58d57e7ef8dc1211a21cc to your computer and use it in GitHub Desktop.
Save mkarnicki/c627d6377df58d57e7ef8dc1211a21cc to your computer and use it in GitHub Desktop.
MailGun support fail
I was looking for transactional e-mail provider for a new website I'm building.
I found MailGun. The landing page says:
# Try our API. Copy & run this in your terminal.
So I did. Picked the default curl variant, pasted in the terminal. The only
thing I changed was the 'to' field and set it to my private mail.
Pressed Enter, waited 2 or 3 seconds and got this response:
{
"message": "Poor traffic quality."
}
I verified I haven't received the e-mail. "Well, that's sub-optimal"
I thought. Not a great demo, is it? So I e-mailed their support describing
the issue, just like I did above. This is the response I got:
--- response #1 from MailGun:
Hi $BAZ,
Thank you for contacting Mailgun support. We will need you to answer a few
questions so that we can assist you:
- Please provide account information so that we can find your account,
i.e. the admin email address, the account name, your username,
or a custom domain added to your account
- What is the URL that you obtained the code from
- Please provide the full text of the code that you submitted
and obtained the error.
Thanks,
$FOO@MG
--- EOM
Well, I replied with the following:
--- mail #2 to MailGun:
Dear $FOO...
1. Open mailgun.com
2. Assuming your on the very main page, copy the curl source from
the MAIN page to the terminal.
To be honest, I can't believe you don't know how the master page of
maingun.com looks. I'm really not sure I want to be involved in business
with Mailgun anymore, sorry.
Sincerely,
$BAZ
--- EOM
Then, I got the following response.
--- response #2 from MailGun:
Hello $BAZ,
The email address from this message doesn't appear to be tied to
a Mailgun account (<$BAZ email here>).
We cannot provide account information without account verification first.
We'll need you to provide one of the following of the account in question:
Last four digits of the private/secret API key
2.Last four digits of the SMTP password for the postmaster credential
of one of your domains
3.Last four digits of the credit card on file, name on the card, and type of card
Best Regards,
$BAR@MG
--- EOM
I literally can't believe a second person from MailGun's support fails to realize
Mailgun's demo from the very landing page is failing miserably and all I can tell
is Mailgun is not interested in a new, paying customer.
Your DEMO is failing miserably, Mailgun.
If you ask me, I'll put my money elsewhere and
look elsewhere for "transactional e-mail for developers".
Go ahead, open mailgun.com and copy their curl snippet, like it says. I'm pretty
sure you'll get the same message, at least around the time I publish this.
What a miserable experience :/
@mkarnicki
Copy link
Author

I have not replied to e-mail #2 from Mailgun support.

For full transparency, I received this HUMAN follow-up e-mail 2 hours later. Damage has been done, no longer interested in Mailgun.

Hello $BAZ,

Sorry for the misunderstanding. I thought you were referencing an error from an existing account. In full transparency the test domain provided in the example has been permanently disabled. We had to disabled all access because users were using it for spam. I realize now that you had a question about the error response. The error occurs when the email traffic leaving the account is bad and the bounce rate of the account goes above our bounce threshold 5.00%.

We'll be changing the wording that way no other users will get confused. Sorry for the inconvenience.

Best Regards,
$BAR@MG

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment