• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Errors in Forwarding HTML Message from Horde

teckna

Basic Pleskian
The following continues to be a problem for us, does anyone know if there is a fix for it?


Short Description
-------------------------
When your forward a message from Horde and add a bit of text to the top of the message, the added text is not displayed when the forwarded message is received in MS Outlook.

Detailed Description
-----------------------------
To recreate the problem:

1. Send a HTML message, and view this message in Horde
2. Click the forward link that opens the new window, add a bit of text to the top of the message. Please note that the default setting in 'Options for Mail'-'Message Composition'-'Compose messages with an HTML GUI by default' is OFF (NOT ticked).
3. Send the message.
4. Receive/view the message in MS Outlook and you will only see the original message (not your added text) displayed.
5. If you view the same message in Outlook Express, you will see the correct message (ie the original AND the added text) in the plain text version, but the html version still only displays the original message WITHOUT the added text.

If you view the actual source of the message sent from Horde you can see why the problem happens - Horde has produced several conflicting Content-Type parts with inconsistent data, I can forward you an example of a message source where this is clearly visible.
 
Back
Top