Extension

Developer
Supported

Escort

ExpressionEngine 2, ExpressionEngine 3, ExpressionEngine 4

Back to this add-on's main page
View Other Add-ons From Derek Hogue

     

You must be logged in to post.

Escort no longer working with Mailgun or SparkPost

Support Request

Jason Morehead
Jason Morehead

Up until a few weeks ago, my site was working with Mailgun. However, I recently checked the developer log and Mailgun deliveries have been failing for several weeks now. Instead, I just get this error:

Escort tried to deliver your email with Mailgun but the service failed.

Nothing’s been changed on the Mailgun or EE side; I’ve confirmed that I’m still using the correct credentials.

As a test, I also signed up for a SparkPost account, but haven’t had any luck with that, either.

I’m using Escort v1.3.0 and EE v2.11.7. All of the website’s forms are created with Freeform v4.2.5.

Any help would be greatly appreciated.

Derek Hogue
# 1
Developer
Derek Hogue

I’m away right now and don’t have great facilities to troubleshoot this, but some first thoughts. Any changes on your server by your web host (new versions of packages, addition or removal of packages)? Do any other services work (SendGrid for example)? If you disable Escort entirely, does the default EE email library work?

Jason Morehead
# 2
Jason Morehead

As a test, I signed up for Postmark and, as of yesterday, that appears to be working.

I’m still not sure why Postmark works when Mailgun and SparkPost doesn’t, but at this point, I’m just happy things are back to normal.

Derek Hogue
# 3
Developer
Derek Hogue

All of my sites which use Escort with SendGrid are still working as usual, so I can only assume that there was an issue with your account or API key?

bluebloc
# 4
bluebloc

I have the same issue. Escort started to fail with Sparkpost on 27 April. We only noticed today. I have changed the API for Sparkpost and updated in EE but with no change. AM running EE 2.8.0 and Escort 1.3.1

Derek Hogue
# 5
Developer
Derek Hogue

Are both your sending domains (i.e., the domain name used in the “from” line in your emails) verified with SparkPost? SparkPost will only send from verified sending domains (again, the domain used in the “from” line, not the domain that your website is running from). See this doc on their site for more info.

bluebloc
# 6
bluebloc

Yes. Sending domain is marked “ready to send” in Sparkpost with its DKIM record verified.

Derek Hogue
# 7
Developer
Derek Hogue

And you are using this same verified domain in your “from” address when generating emails? Sorry to be a broken record, but this is the #1 issue I see with Escort (e.g., user-submitted form notifications coming “from” a user’s Gmail address, and thus failing.)

bluebloc
# 8
bluebloc

Yes. Have double checked on both Form notifications.

Derek Hogue
# 9
Developer
Derek Hogue

Can you do a simple test using the Communicate admin page as well, to bypass any possible add-on issues? If it’s still not working, I’d like to take a closer look with some FTP and EE credentials, if you’d be OK with that. (Can email to derek@amphibian.info.)

bluebloc
# 10
bluebloc

Communicate admin page email doesn’t work using Escort. Will get the FTP credentials and send to you tomorrow. It’s late here now.
Thanks

mediapimp
# 11
mediapimp

I have been having the same issue as well with Sparkpost.

Derek Hogue
# 12
Developer
Derek Hogue

I just tested Escort with SparkPost once again to make sure nothing’s changed in their API, and all is working as expected. The #1 issue that comes up with SparkPost is that people have not added and verified the domain matching the one used in the “from” email address.