Hm; then I guess the question is, does Adobe have a function that will apply that encoding? The data we're using in the title is not static, but from a resource we have.

Well that's a new one. Something's changed now, and even without a special character, it breaks.The subject is now being UTF-8 encoded, which results in the emoji marker being encoded again, and so it decodes to the raw text of the =?UTF-8 stuff instead of the emoji as intended.Example:Subject: =?ut...

I just sent another test email to grab some screenshots:Subject: =?UTF-8?Q?=F0=9F=94=A5?= Emoji Test 1Result: https://i.imgur.com/D84v0UR.pngSubject: =?UTF-8?Q?=F0=9F=94=A5?= Émoji Test 2Result: https://i.imgur.com/Q8Kgupo.png

Yes, I've seen that thread before; as you'll note, we're using the same method described there. However, we're encountering the same issue as the last comment in that thread that was never replied to.It works fine until something like é or © shows up and then it all blows up. Something in Campaign i...

We're trying to send out an email with a fire emoji, represented by =?UTF-8?Q?=F0=9F=94=A5?=It works fine for the most part, until an email contains higher ascii such as © or ó, at which point it starts trying to mix encodings and set the rest of the title as windows-1252 according to the header out...