devot:eeDevoted to ExpressionEngine

Hello,

we have recently upgraded from EE2.x to EE5.x and are now running into the issue that latest Escort 1.3.3 (on EE5.x, using Sparkpost) delivers our HTML emails rendered as text.

Meaning: one sees the html string in the actual email b/c it is presented in text format.

All of this used to work just fine on our EE2.x install, which also used Escort and Sparkpost. Our email templates have NOT changed and our domain is registered and verified in Sparkpost.

The only difference is that our new EE5.x test stage sits on a different sub-domain than our EE2.x test stage and our prod stage, but the main domain is the same for all of them. Escort and Sparkpost do work just fine on our EE2.x test stage and prod stage, both still using EE2.x and an older version of Escort.

EE5.x is set to send hml emails under EE admin > settings > outgoing email > mail format, and a test using the Communicate utility does deliver the html string of the email rendered as html…

So what could be the reason that our email html templates are now rendered as text when sent via Escort 1.3.3 on EE5.x and Sparkpost ?

Thanks.

If sending emails via Communicate is working, I’d guess the problem is with whatever addon is generating the particular emails you’re having trouble with - likely not respecting your preferred format, or maybe using its own setting for email format somewhere?

Is there any way to have Escort override whatever setting came from the addon and always default to HTML ?

We’re on latest EE5.3.2 and the latest version of the User addon 5.3.0 defaults to sending text version only emails for the Forgot password option - EE Harbor confirmed that.

For whatever reason this was different on EE2.x w/ User 3.x and Escort, meaning emails were ALWAYS sent as html…

Lmk about the above, please.

Thanks !

This is beyond Escort’s scope, as it’s really intended to be a “dumb” courier, simply taking what it’s given and passing that along to the intended service.

You could potentially use Escort’s extension hook to modify the data before it gets passed off to Sparkpost, but that would require some custom extension coding.

so here’s a similar issue we’re running into - again all of this worked on EE2.x w/ older Escort, we use the exact same templates on our new EE5.x install and still use Sparkpost.

Iur order confirmation email which is TEXT format we have one (1) link in the email message, and that link text is now being changed/altered.

This is the snippet from the email template - as you can see the link is at the end of the snippet:

This is what we receive in the email on EE5.x w/ latest Escort:

As you can see, the simple text link has been altered and converted to a completely different string. Clicking on it still works but this is not the appearance we want.

Is this done by Escort ?

Thanks.

to add on to my last reply, on our old EE2.x server w/ the old Escort addon, the same email goes out just fine and we are also using the exact same Sparkpost account for that…

So it would appear we can take Sparkpost out of the equation.

No, this is done by SparkPost when it processes the email - Escort never alters the contents of an email. Why this would be happening when sent via EE2 vs EE5 I can’t say honestly (both versions use an identical processing method for SparkPost) - but if you look for the options in your SparkPost account for Click Tracking and Open Tracking, those are the settings that will affect the rewriting of links like this when your emails are processed.

agreed on the link part, but the problem is we have click tracking completely disabled in Sparkpost. I’ll contact Sparkpost.