-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mailgun no longer working #83
Comments
I can confirm same issue as @williamdavies90 - I ran a test run about half an hour ago and it's not appearing in the Mailgun logs. Last run i sent successfully, was on 22 Feb 2017. So it appears something has changed between then and now. @leemunroe anything in the source below that you think may be responsible? |
Yes. Having the same issues... same time frame. |
@leemunroe I'm updating the upstream packages your repo depends on with the new API implementation. I'll send a PR with the updated package version of grunt-mailgun once I'm done. |
Firstly thank you so much for this amazing workflow, it has made my life so much easier.
The last month or so I have noticed the mailgun task is no longer working. I have done some digging around and it would seem mailgun have updated their API but unfortunately I have not been successful in updating and changing this within the workflow. If its any help windows 10 throws a 301 error and OSX appears to send the email but it doesnt work.
Many thanks.
The text was updated successfully, but these errors were encountered: