domingo 03 octubre 2021 :: 1144hrs (UTC +01:00)
I have just read your problem. If we were approached about this issue we would offer an explanation for a fee, to put most people off, though unlikely to be asked a further fee to re-write the code. Basically we only work with clients on contract and resolution of this sort of issue would normally be included.
However, as I can’t get out on my JetSki this morning because of a brief thunder & lightening storm, here is a brief explanation:
When you see something like =3D, what you’re seeing is a single character in what’s called “quoted-printable” encoding. “=3D” is, in fact, an equal sign, so what you have in your example is ==.
What you can call “funny characters” or character sequences. They always begin with an equals sign, though. For example, things like =0D=0A and =3D appear throughout html message source code.
You’d think that with plain-text email having been around for as long as it has, issues like this would have been resolved by now.
The problem is that there’s “plain text” email, and then there’s “plain text” email.
No that’s correct not a typo — not all “plain text” is created equal.
So, when you see something like =3D, what you’re seeing is a single character of “quoted-printable” encoding.
A few examples: “=3D” is, in fact, an equal sign. =0D is a Carriage Return (CR), =0A is a Line Feed (LF), and =0D=0A is a CRLF combination. CR, LF, and CRLF are all used to indicate the end of a line of text in plain text emails. In fact, any character can be represented as a three character “=” sequence in quoted-printable. “=00A=00s=00k=00 =00S=00k=00y=00b=00a=00t”, for example, is “Ask Skybat!” in full quoted-printable encoding.
Quoted-printable is one of several encodings used to get around the fact that not all mail software (and in the past, not all network transports) can handle what are called “non-printable” characters, or certain types of non-alphanumeric characters.
CR and LF, for example, don’t cause anything to be displayed; they just “mean something”: the end of a line. That’s why they’re called “non-printable”.
Non-printable characters in email messages can confuse some email software, particularly older, legacy systems. The work-around is to represent them in a way that doesn’t confuse the old mailers.
When an email message uses quoted-printable, one of the hidden headers — the information you don’t normally see — explicitly says so.
If you’re seeing the quoted-printable characters in their quoted-printable form, that header is either missing, malformed, or it’s been overlooked.
In the case of your mailing list, the approvals are probably arriving in some kind of “raw” form. Your mailing list software has probably removed or overridden the header information. As a result, your mail program doesn’t know that it should decode the encoded characters. It sees it as unencoded plain text email and displays it as-is or not at all.
In short you will need to speak to whoever is encoding and or mailing out for you.
Some years back I created a useful tool for encoding email links for html insertion using quoted-printable.
Go to: https://www.compucall.com
Click any of the email links to open your email client to view an example.
Then at the top of the page in the ‘drop down’ click ‘Mailto’ button for the tool.
¡Saludos desde la soleada Valencia en España!
¡Mis mejores deseos y mantente a salvo!
Hablo español, luego portugués e inglés, con conocimiento de varios otros idiomas.