Could it be a bug in the IERenderer?
It's pretty difficult to judge on this without having the actual message available since there are certain kinds of encodings applied to emails and especially URLs which all have an effect on what you see and what you get, just to give you an idea of what I can see in your sample:
https://example.com/
The above line contains twice the "=3D" encoding (encoding a simple "=" ) which might be an undecoded part of the quoted-printable transport encoding applied to lots of email messages and should never show up as the clicked link nor in any kind of human readable display except for the raw message view (which you rather likely copied it from). Then there are certain kinds of characters which aren't allowed to show up in URLs and therefore need to be UTF-8 encoded (language independent character set) and percent or HTML entity escaped (for hiding non-ASCII or special HTML characters such as &char; ) - which we don't have an example of in your case. And - what IER does not least: Send them through a WinInet processing function called InternetCanonicalizeURL() for verifying its validity (and there's more). IOW: Can you please forward such a message (as unmodified attachment) either to my private address (which I know you know ) or to <beta-reports [@] pmail.gen.nz>, Thomas?
This way I can figure out which one of the verification or conversion attempts fails for what reason: I suppose it's the InternetCanonicalizeURL() function because the "hash" sign usually designates the final part of a URL, namely an intra-page URL like this one: https://www.w3.org/TR/html4/intro/intro.html#fragment-uri (its a working one actually explaining itself). Another candidate would be the Tidy module for fixing lots of common HTML issues one of which I already recently needed to patch.
TIA
[quote="pid:54516, uid:2273"]Could it be a bug in the IERenderer?[/quote]
It's pretty difficult to judge on this without having the actual message available since there are certain kinds of encodings applied to emails and especially URLs which all have an effect on what you see and what you get, just to give you an idea of what I can see in your sample:
````
https://example.com/#/verify-email?userId=3D54dd1&token=3DCfDJ
````
The above line contains twice the "=3D" encoding (encoding a simple "=" ) which might be an undecoded part of the quoted-printable transport encoding applied to lots of email messages and should never show up as the clicked link nor in any kind of human readable display except for the raw message view (which you rather likely copied it from). Then there are certain kinds of characters which aren't allowed to show up in URLs and therefore need to be UTF-8 encoded (language independent character set) and percent or HTML entity escaped (for hiding non-ASCII or special HTML characters such as &char; ) - which we don't have an example of in your case. And - what IER does not least: Send them through a WinInet processing function called InternetCanonicalizeURL() for verifying its validity (and there's more). IOW: Can you please forward such a message (as unmodified attachment) either to my private address (which I know you know ;)) or to <beta-reports [@] pmail.gen.nz>, Thomas?
This way I can figure out which one of the verification or conversion attempts fails for what reason: I suppose it's the InternetCanonicalizeURL() function because the "hash" sign usually designates the final part of a URL, namely an intra-page URL like this one: https://www.w3.org/TR/html4/intro/intro.html#fragment-uri (its a working one actually explaining itself). Another candidate would be the Tidy module for fixing lots of common HTML issues one of which I already recently needed to patch.
TIA
Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C