I have a problem with Evolution where some emails are not parsed correctly, this started a year ago or so, so it is nothing new. The strange thing is that emails that come from the same company, but from different users, using the same images in their signatures, are parsed differently. This is the signature of a mail that is parsed correctly:
This one is not (email background is not white, images are not in-line, they come as attachments):
Of course, when an email is parsed incorrectly, all (in-line) images in the mail comes as an attachment, not just the signatures. Both the senders of the emails above are in the Edit/Preferences/Mail preferences/Html Messages/Allow for senders list, if that matters.
I have tried View/Load Images (CTRL+i), but that just shows a red cross over the attachments/images for a second or two.
The key question is: what email client(s) are being used to send the messages that don’t parse, and is there a difference from the ones that do parse? If so, this is likely to be a configuration issue at the sender’s end, related to incorrect MIME encoding.
it looks like the message structure is somehow broken. You can check
that in the message source (Ctrl+U), search for “Content-Type” in
there. It will be there multiple times. You won’t see the “tree”
structure of the parts and the subparts, but I suspect it will look
like something similar to this:
The images have also Content-ID, which correspond to what you see as cid:. The best would be if you could ask one of the users to send you
a test message, with nothing private in it, and attach it here or
somewhere from where you’d be able to remove it, if needed.
Also, what does Edit->Preferences->Mail Preferences->HTML Messages
->Plain Text Mode say for you, please? It can be set to prefer Plain
Text, in which case you are looking into the text/plain part, not the
text/html part (see above).
I will try to find out what clients they are using, but I realized when I was looking through old mails that some emails are parsed correctly and others incorrectly from the same user, so I suspect that it must be something else!? My guess would be that they are all using Microsoft Outlook (the latest desktop office version).
Thus they are using tnef format, which is a special Microsoft thing for
formatted mails. There is a tnef plugin for Evolution, which decodes
and shows those, but it seems you’ve it missing. Maybe your distro
packages it separately, or they do not ship it at all. It’s part of the
main sources; it can be the libytnef dependency is the reason why they
I also do not find a Plain Text Mode under HTML Preferences? I am
using version 3.44.4-0ubuntu1 of Evolution under Linuxmint 21.1 vera.
I have it at the very bottom of that tab. It’s also a built-in plugin,
weird you do not have it installed. Or it can be disabled under
Edit->Plugins, maybe. In any case, it’s not the problem here.
The plain-text-plugin was disabled for some reason, after I enabled it and restarted Evolution, I can now see the setting you referred to.
I searched for the TNEF plugin in the plugin settings and the Linux Mint software manager, but it does not appear there. I will take a backup of my Evolution data, and install the flatpak version instead, and see if that solves my problem. I will also look around in the Linux Mint forums and see if someone there knows more about this plugin.
If neither of those things solves my problem, I’ll just leave it as it is. I have managed to live with this for a year, so I’ll be ok if I don’t find a solution to this
Either way, now I know what the problem is, I did not know that TNEF was a thing, so many thanks for that!
it will not solve it, the Flathub.org’s version has the YTNEF support
You might be able to build the plugin yourself, from the sources:
but it’s beyond this forum how to do it, I’m afraid. I can try to write
a cook book/how-to, if you think it’ll be helpful, though you might
check first whether you have available the YTNEF library in your
By the way, if I recall correctly, the Outlook has an option to not use
the TNEF format (they may call it RTF in the GUI) - it’s better to not
use it, if they want to “support” more than just Microsoft Outlook for