Unable to send mail via Mailgun over api or smtp

青春壹個敷衍的年華 提交于 2019-11-28 00:10:01

Faced the same issue while sending emails via api by php curl. I solved it by changing API Base URL https://api.mailgun.net/v3/YOUR_DOMAIN_NAME to https://api.mailgun.net/v3/YOUR_DOMAIN_NAME/messages. It's because their api is not only for sending. Hope this helps.

For anyone else trying to figure out what "Mailgun Magnificent API" means in a Mailgun HTTP 200-OK API response, it occurs when posting to https://api.mailgun.net/v3/YOUR_DOMAIN_NAME/some/api/endpoint when /some/api/endpoint is not a valid Mailgun API endpoint.

There are several ways you could accidentally see this. Say your sender domain is "mg.example.com". All of these will respond with "Mailgun Magnificent API":

  • Omitting the API endpoint: https://api.mailgun.net/v3/mg.example.com (as noted in another response)
  • Misspelling the endpoint: https://api.mailgun.net/v3/mg.example.com/massages (that should be messages with an e)
  • Including a # after your domain: https://api.mailgun.net/v3/mg.example.com #/messages (perhaps you tried to add a # comment to your config file, but your config format doesn't support inline comments?)
  • Including an extra path after your domain: https://api.mailgun.net/v3/mg.example.com/myapp/messages (maybe you're using a Mailgun client library and set MAILGUN_DOMAIN_NAME='mg.example.com/myapp'—the /myapp part doesn't belong in your domain name)

Note that you won't see "Mailgun Magnificent API" if YOUR_DOMAIN_NAME is not a valid sending domain you've registered with Mailgun. (In that case, Mailgun instead responds 404-Not Found).

标签
易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!