| Summary | incorrect signature display |
| Queue | IMP |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | slusarz (at) horde (dot) org |
| Requester | vilius (at) lnk (dot) lt |
| Created | 02/03/2005 (7584 days ago) |
| Due | |
| Updated | 02/08/2005 (7579 days ago) |
| Assigned | 02/03/2005 (7584 days ago) |
| Resolved | 02/04/2005 (7583 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
the answer.
example of "correct" display since that message was generated with an
IMP version that prouced incorrectly formatted messages.
And anyway, that message is, in fact, rendering correctly. Please
read RFC 2646 if you don't believe me. The 2 spaces at the beginning
of those lines after the signature are correctly rendered as only 1
space - those are "space-stuffed" lines due to the fact the previous
line is flowed.
spaces (see screenshot and message source for details) still exist.
problem for some other people (besides me) because I saw the problem
fix itself in Jan's postings to the mailing list yesterday after Jan
presumbaly updated his framework from CVS :)
State ⇒ Resolved
State ⇒ Assigned
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ incorrect signature display
Queue ⇒ IMP
State ⇒ Unconfirmed
properly anymore. Text after -- ir not wrapped, and there are missing
spaces in message view. See attached screenshot and code of the test
message.