-
Notifications
You must be signed in to change notification settings - Fork 92
MailgunAPIError: <Response [400]> #34
Comments
I've got this error too when moving from staging to production. I'm guessing it has something to do with ALLOWED HOSTS but I have not been able to crack it as yet |
Apologies for leaving this hanging for so long. Life got in the way. Does anyone know if Mailgun changed their API? FWIW, I'm not having these problems myself. I can't reproduce them. Not yet anyway. |
I received the same error message, it was due a typo in an e-mail template. MailGun raised a 400 which sent me on a wild goose hunt. In the example above, if there is something awry with the ctx, it may do the same. |
Hi, I still cannot get this work... So I have to convert to gmail, unfortunately :( Is there any solution for this? Thank you |
You can see error details in your Mailgun Logs. I got 400 response because I haven't activated account. |
This project is unsupported. Please use https://github.com/anymail/django-anymail instead. |
Got the same error @alzearafat try below settings in mailgun Security Settings For Outgoing Mail it works for me |
Hi, Thank you, I will test it out! Thanks ! :D |
Hi,
I just following your readme, but I keep getting this error :
This is my setting (I'm not sure, whether I should using secret key or public key, but both is error when I'm trying to send email) :
My views.py :
I'm using django 1.9.2, Python 2.7
Did I miss something here?
Thank you in advance for any help you can provide :)
Regards,
The text was updated successfully, but these errors were encountered: