MIME-encoded email headers not decoded (e.g. =?UTF-8?B?...?= shown literally)

[mfr]

Hi everyone,
I’ve noticed that incoming emails, especially from devices like FritzBox routers, sometimes contain MIME-encoded headers (e.g. Subject that look like this:

=?UTF-8?B?ZmI3NTkwIGVkZ2U=?=

Instead of seeing the decoded string (fb7590 edge in this case), EspoCRM displays the encoded form literally. While the MIME encoding is technically correct and RFC-compliant (even if the content itself is plain ASCII), I would expect EspoCRM to decode this automatically – as most mail clients do.

Is there a way to enable or enforce decoding of MIME-encoded words in email headers (especially the subject)?

Any hints regarding configuration options, extensions, or relevant files to look at would be much appreciated. Alternatively, is this a known limitation or a bug?

Thanks in advance!
Martin

[yuri]

Please check our bug report rules: https://forum.espocrm.com/forum/bug-...before-posting

It could be an issue in the latest version of the zbateson/mail-mime-parser library.

[yuri]

We observed a from-address encoding issue in some emails after we upgraded the lib to the latest version.

[mfr]

Thanks yuri. The first upcoming was around the Sep., 18th 2024 in my EMails. For your information.

[yuri]

Could you provide an original content of some problem email? It can be useful if we report the issue upstream.

[mfr]

Could you provide an original content of some problem email? It can be useful if we report the issue upstream.

Sorry yuri for the late reply. I don't know why, but this forum software doesn't notify me of new messages, even though I configured it correctly.

I have attached an example of an original email source code with all headers (anonymized )