Over the past few days, I’ve received feedback from several people I’ve emailed saying that the emails were blank—that is, they contained no text. There haven’t been any updates to eM Client before I first noticed this. I haven’t changed anything else either. I use an Exchange account for my email, but nothing has changed there either.
Does anyone know what might be causing this and what I can do about it?
There was an update released two days ago to fis this issue, are you using that version?
Thanks for your support – no, my version is 10.4.5608. I will install it immediately.
After I noticed the problem, I tried „check for updates“, but there was no hint about an update. (I don’t understand how updates for eM Client are spreaded – an hotfix should appear when I am looking for update!)
Next time I will check the versions page on emclient.com.
Unfortunately the problem is still present although I updated my Client …
Hello
Same problem here. I have a mail recieved from emclient (lastest version, Exchange account) and it appears blank (no body) in Outlook (classic). But it’s ok in the webmail, with all the body.
I wonder if it’s a problem with emclient or with Outlook classic (Microsoft® Outlook® pour Microsoft 365 MSO (Version 2606 Build 16.0.20131.20154) 64 bits )
As mentioned before we’ve already released a version with a workaround for that Outlook bug:
And it is a problem of Outlook. It sends syntactically invalid html comments. We’ve just quickly developed a workaround for that issue and gradually pushing an update with the fix to everybody.
Hi,
We are still having problems when replying or followings mails (version 10.4.5642 (2a058e0)). I also have now problem when replying to mails with eMClient (while replying the mail I reply to isn’t showing).
Do you need some more informations ?
Hello,
I can confirm that the bug is still present. The fix released on July 22 (https://www.emclient.com/dist/v10.4.5642/setup.msi) did not solve this critical issue for me.
Regards,
Armin
We’ve tested the workaround quite thoroughly. Can you please send as the message you experience the issue with as EML file (here or if it is private to [email protected])?
I just want to repeat that it is primarily a bug in Outlook, we are just trying to workaround it until they fix it on their side.
Just sent the EML file to [email protected]
Thanks
Hello, I just sent a message to [email protected]; I’ve already performed the updates and tests, but it didn’t work. The email was sent from stela@…
On another machine, I have a 10.4.5326 version installed (not updated), it doesn’t seem to have this problem. I can send html emails that can be read fully with Outlook (classic).
I just want to clarify what the problem is, what our workaround fixes, and what it cannot fix.
Here’s the bigger picture:
Outlook Classic uses the Microsoft Word rendering engine to compose emails instead of a web browser engine. This provides a lot of flexibility for text formatting, but it also means that Outlook Classic must convert its internal Word document format to HTML before sending a message. The quality of the generated HTML has historically been poor, and it has long caused compatibility issues in other email clients and webmail services.
Outlook Classic also uses HTML comments to store internal commands and metadata.
In the latest version of Outlook Classic, Microsoft introduced a new syntax for these internal comments. Unfortunately, the new syntax is invalid because it contains nested HTML comments, which are explicitly prohibited by the HTML specification.
When replying to such messages, eM Client strips the invalid nested portion of these HTML comments during processing. As a result, when the reply is later opened in Outlook Classic, part of the internal metadata stored in those comments is missing. Outlook Classic therefore displays the message as blank.
Once a reply has been sent from eM Client without those invalid nested comments, it will always appear blank in Outlook Classic. Interestingly, Outlook (New) and Outlook on the web display the same message correctly because they do not rely on the Word rendering engine or the internal commands stored in these HTML comments.
eM Client 10.4.5642 specifically detects these invalid nested HTML comments and preserves them unchanged when sending replies. This resolves the problem for all newly created replies.
However, it cannot repair replies that were already sent by earlier versions of eM Client. Those messages have already been modified, and the missing HTML comments cannot be reconstructed.
These older messages continue to display correctly in eM Client, Outlook (New), Outlook on the web, and virtually every other email client. The problem only occurs in Outlook Classic.
The only way to “fix” replies that have already been sent with the nested HTML comments removed is to edit the affected messages manually.
Ok, thank you ! It’s fine know.