MailEnable Enterprise v10.29

When WebMail Properties -> "Prevent the loading of remote images in HTML" is enabled, remote images will not print when the end-user prints a email. Even after they've clicked to "Download Remote Images".

MailEnable 10.27 Enterprise: - Through webmail, create a mailbox filter. Sent any description and any criteria. Set the filter action to "Move message to folder...", and a Directory from the drop-down (I used one called "TestFolder"). Save the filter rule. - Edit the filter rule you just created. Ma...

Both problems still persist in latest version (10.27)

If you create a new filtering rule, or edit an existing filtering rule and set Filter Action: "No Action", MailEnable will return a .NET error: Server Error in '/MEWebMail' Application. Object reference not set to an instance of an object. If you edit an existing rule and change it's Filter Descrip...

If I create a filtering rule with a "Message Subject Contains" criteria, it will match against messages with a plain-text subject line, but not if the subject uses UTF-8, or other such encoding. For example, if I create a rule -> Message Subject Contains: testing it will match this: Subject: I am te...

Forwarding any type of message via the Mobile Webmail interface breaks the formatting of the original message.

Open Outlook 2016, compose a new message. Address it to a MailEnable user. Write something in the message body that uses the "supportLists" tag. For example, use the button in the attached image. Send the message. Login to the recipient's mailbox via WebMail. Click to view the message. Click the "fo...

MailEnable Enterprise v10.20

Message formatting sometimes breaks when forwarding messages through the Webmail interface.

For example, I've noticed this for messages that were originally composed through Outlook 2016 that use the "if !supportLists" tag.

This appears to have been fixed in the new release v10.20

Problem has been confirmed corrected in v10.20

MailEnable Enterprise v10.19

The registry settings provided in your knowledgebase appears to have no effect. Is it still supported in MailEnable v10?
https://www.mailenable.com/kb/content/a ... D=ME020610

MailEnable Enterprise v10.19 The registry setting provided in your knowledgebase appears to have no effect. Is it still supported in MailEnable v10? https://www.mailenable.com/kb/content/article.asp?ID=ME020480 The message in question was still forwarded even though the below header entry was append...

MailEnable Enterprise v10.19

Message written in Arabic (possibly other Unicode languages) sent via the MailEnable Web Mail interface display correctly when viewed through Web Mail, but not through a third-party email client such as Outlook or Thunderbird.

MailEnable Enterprise v10.19

Ever since upgrading to v10.19, when I open messages through Webmail that do not have a Content-Type header, it returns a .NET error.

Yeeeeesssss, I could do that, but it ultimately makes Spamassassin less effective. Since MailEnable is already aware of the problem (since at least May 4, 2016), I guess the operative question is, "is fixing this in MailEnable's roadmap?"