Please don't create duplicate tickets. If an old ticket needs to be 
re-opened we'll do it.

This first ticket, 4155, talks about Outlook with a display problem 
from Horde.  I've researched this in depth, and I don't believe that 
this was the right reply to this message.



I'm not sure if the build I have is the same, but I have the same problem.



http://bugs.horde.org/ticket/?id=4155



=========

07/13/06 fboaventura (at) gmail (dot) com State Ë Unconfirmed

Queue Ë IMP

Summary Ë reply/forward messages showing blank on outlook

Type Ë Bug

Priority Ë 2. Medium Reply to this comment

When I reply or forward a message trough IMP, and add some comments to 
the top of e-mail, those comments aren' t shown when opening on 
Outlook 2003 (haven' t tested with other versions).



But I'd tested with GMail, Yahoo!, IMP, Evolution and KMail without 
problems, on all of these clients the message is correctly shown.



=========



=========

07/15/06 Jan Schneider State Ë Not A Bug Reply to this comment

Why do you report this here then, and not to Microsoft?



=========



=========

06/14/07 e (at) bexz (dot) com Comment Reply to this comment
Microsoft won't help with this problem, they insist it's Horde's 
issue, and it really is.



It appears to be an issue with the "unnamed Plain/text".  When 
forwarding in Horde, the primary message is forwarded as an attachment 
(or as inline), and so is the forward. Horde creates two messages as 
attachements inclead of just Indenting the message and leaving the 
primary text intact.  This seems to be a problem with the inline 
method and the attachement method.



In outlook, it shows two seperate "unnamed", but when the first 
message was HTML, and forwarded as plain-text, the HTML message is 
being shown as the only message in the email body.   So, the either 
the attachement is broken or the text that's supposed to be inline 
isn't being converted to plaintext when forwarded.



Whether or not horde is configured to compose or display in html or 
plaintext, or in any combination that the user selects, it should be 
converting the message into the format of the sender- this is what the 
problem appears to be broken.  Horde isn't stripping away that HTML 
and dumping it into a message in plaintext, it's stripping away the 
plaintext version when it sees the duplicate "unnamed" in the message.



Is there a patch to fix the way the message is being attached or forwarded?

=========



Thanks!