I've upgraded to Confluence 6.0.6 and Lotus Notes 9.0.1.  The same issue still occurs with Confluence 6.0.6.  Are there any plans to provide a fix?

We are also facing the same Problem. It is annoying for me and uncomfortable for our users.
Sure, its just a kind of feeling, but this is not cool.

May be there is a kind of workaround for this issue?

Michael, any update on this? We are now on Confluence 5.8.18 and Lotus Notes 9.0.1 and the issue is still present.

We are using CONF 5.5.7. We had also an incident in the company concerning Lotus Notes mail. The button to reset the password is not shown, only the link back to the forgotpassword.action. So why you don't replace the button by a simple link which is correctly rendered in any case? Would be a pragmatic approach.

At present this is not on our short term roadmap for bug fix. At the moment we're working with the dev team to determine if this still occurs in the latest version (4.3.x), and will prioritise it based on that.

I'll update this ticket as soon as we have more info.

Good Morning. I am trying to track this same issue. I have Confluence 3.5.17 installed and we are using Lotus Notes 8.5.2 for email. I have the same issue where HTML notifications are not displaying the email body content.

Here are my testing scenarios:

Setting email notifications in my profile to TEXT or HTML.
-Wiki page updates received with body content displayed with no problems

Setting email notification in my profile to TEXT or HTML
-Email notifications received for updates to Team Calendar events does not show the body content in the email.
-If I forward the email, the body content then shows up in the forwarded email at the bottom where the original email is shown.
-This problem does not present itself viewing the original notification email from the web based lotus notes client.
-This issue seems to only affect notifications for Team Calendar events

I see it mentioned here there is a patch for JIRA. Is there a patch available for Confluence 3.5.17? Thanks!

Thanks Stefan, but seems like this patch will mess up the Email content if certain character is entered into the Page title: CSP-65951. I have attached the new Email.java that will fix the issue for page titles with apostrophes, but if you do encounter any issue with other characters, you can add the character to the following line of Email.java:

Pattern p = Pattern.compile("&'#(.*?);"); //Add the character into the REGEX, after the apostrophe character

After that, put an additional entityMap line (Example for apostrophe):

entityEntityMap.put((short)39,"apos");

Recompile Email.java under ConfluenceSource\confluence\src\java\com\atlassian\confluence\mail

Do note that this patch is not provided by Atlassian (Therefore, unsupported by Atlassian), attempts to apply it should be done with care, with backups of your original Confluence build, should you run into issues.

Still we are facing the same issue - Atlassian

I just had a closer look: This is actually hidden in a call stack made up of com.opensymphony.webwork.util.VelocityWebWorkUtil.htmlEncode(String) and then com.opensymphony.util.TextUtils.htmlEncode(String).

If I got Mark right (how they fixed the JIRA issue) they will be fixing this by changing the behaviour of com.opensymphony.util.TextUtils.htmlEncode(String). This approach should work also with Confluence, but there might be other side-effects.

In the meantime I have migrated the patched Email class (from the JIRA Issue) to Confluence. Tested on Confluence 3.1, but will work on 3.2.1, too (same atlassian-mail version).