Escort
ExpressionEngine 2, ExpressionEngine 3, ExpressionEngine 4, ExpressionEngine 5, ExpressionEngine 6
Back to this add-on's main page
View Other Add-ons From Derek Hogue
SparkPost failing with EE 2.10.1
Support (Resolved)
|
deaconweb
|
| Posted: 22 April 2016 07:12 PM |
|
|
|
|
I have updated Escort to v. 1.3.0 and added the API credentials for SparkPost. I have tried to send messages using Communicate and Freeform. In both cases Sparkpost fails.
Any suggestions?
|
|
|
|
|
Derek Hogue
|
| Posted: 22 April 2016 07:43 PM |
# 1
|
|
|
Developer
|
Sure thing - but first question: have you verified your sending domain in SparkPost?
|
|
|
|
|
deaconweb
|
| Posted: 23 April 2016 02:26 PM |
# 2
|
|
|
|
Yes. SPF and dkim are set up correctly and domain is verified. I am able to send from within SparkPost interface successfully.
|
|
|
|
|
Derek Hogue
|
| Posted: 25 April 2016 07:54 AM |
# 3
|
|
|
Developer
|
I’m having trouble replicating this. In my test setup I am able to send with SparkPost from the Communicate tab, both plain text and complex HTML emails. Are you getting a notice in the Developer Log that SparkPost failed?
|
|
|
|
|
deaconweb
|
| Posted: 25 April 2016 08:28 AM |
# 4
|
|
|
|
I am getting a message in the developer log that it is failing. I saw in another thread that having Libraree installed could be a problem. I have disabled Libraree, but it is still installed.
|
|
|
|
|
Derek Hogue
|
| Posted: 25 April 2016 08:46 AM |
# 5
|
|
|
Developer
|
If Escort is getting to the point where the failure is being logged, then Libraree isn’t likely the culprit. Do you have cURL installed on the server? Can you try one of the other services maybe?
|
|
|
|
|
deaconweb
|
| Posted: 25 April 2016 09:48 AM |
# 6
|
|
|
|
Yes. Mandrill works correctly.
|
|
|
|
|
Derek Hogue
|
| Posted: 25 April 2016 01:27 PM |
# 7
|
|
|
Developer
|
Very odd. Is this on a live site? Any chance I could get FTP and EE credentials so I could troubleshoot? derek@amphibian.info.
|
|
|
|
|
mediapimp
|
| Posted: 25 April 2016 04:09 PM |
# 8
|
|
|
|
I am having a similar issue with EE 2.5.5. Would like to know the solution once it has been found.
|
|
|
|
|
Derek Hogue
|
| Posted: 26 April 2016 12:06 PM |
# 9
|
|
|
Developer
|
The issue here was that the emails were being sent with a “from” address within a domain which was not verified in SparkPost. When using SparkPost, you can only send “from” addresses in verified sending domains.
|
|
|
|
|
mediapimp
|
| Posted: 26 April 2016 02:05 PM |
# 10
|
|
|
|
That was my issue as well. Thank you!
|
|
|
|
|
garabedium
|
| Posted: 22 September 2016 08:50 PM |
# 11
|
|
|
|
I’m experiencing the same issue on a client’s site. It might be useful to be able to stipulate the domain name for Sparkpost the same way that you can for Mailgun.
|
|
|
|
|
Derek Hogue
|
| Posted: 23 September 2016 08:53 AM |
# 12
|
|
|
Developer
|
@garabedium: it doesn’t work this way I’m afraid. Any domain name used as a “from” address in an email routed through SparkPost must be previously verified inside of SparkPost’s dashboard. There’s nothing Escort can do to change this.
The “domain name” setting for Mailgun is simply part of Mailgun’s APi authentication.
|
|
|
|
