Summary | Question Marks and Carriage Returns inject into replies |
Queue | IMP |
Queue Version | 6.2.19 |
Type | Bug |
State | Not Reproducible |
Priority | 1. Low |
Owners | |
Requester | cjdl01 (at) brokensolstice (dot) com |
Created | 07/20/2017 (2965 days ago) |
Due | |
Updated | 09/27/2017 (2896 days ago) |
Assigned | 07/21/2017 (2964 days ago) |
Resolved | 09/27/2017 (2896 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
get the tidy PHP extension. If you have it running already, try
updating it.
State ⇒ Not Reproducible
Any idea on how I can test this? Take Horde out of the equation?
Thanks.
New Attachment: test message.eml
As requested, attached is a source email. This is from Outlook 2013.
When I hit reply, it adds the extra blank lines and question marks...
Thanks.
Priority ⇒ 1. Low
State ⇒ Feedback
New Attachment: Screenshot_20170720_102945.png
the original post of the bug. As you can see, it is adding a lot more
blank lines....
New Attachment: qmcr.jpg
trying again...
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ Question Marks and Carriage Returns inject into replies
Type ⇒ Bug
seems to add an extra <br />?<br /> after each block element. There
are more than twice the number of carriage returns there should be,
and there is a line in the middle with only a question mark on it. In
complex messages, this can make the result nearly unreadable. People
receiving these replies become very confused, and many think it is the
result of a virus.
For certain, I can say that this happens when replying to emails
written in outlook. It may apply to others.
I have posted this problem, but haven't had any really relevant
responses (its been a week). The only response I had suggested to try
this:
<https://lists.horde.org/archives/horde/Week-of-Mon-20160104/055263.html>
Which I did, and it took care of the blank lines... but not the
question mark lines. I haven't tested it thoroughly, so I 'm not sure
if other problems will occur by implementing this workaround...
I can easily replicate this email simply by sending myself a message
from Outlook 2013.
Thank you.