Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replying to an email with format=flowed messes up the quoted text #3868

Closed
cketti opened this issue Jan 9, 2019 · 4 comments · Fixed by #5603
Closed

Replying to an email with format=flowed messes up the quoted text #3868

cketti opened this issue Jan 9, 2019 · 4 comments · Fixed by #5603
Labels
type: bug Something is causing incorrect behavior or errors

Comments

@cketti
Copy link
Member

cketti commented Jan 9, 2019

Replying to the message

Content-Type: text/plain; charset=utf-8; format=flowed

The quick brown fox jumps over the lazy dog. All work and no play makes 
Jack a dull boy

results in

Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

response text here

On January 9, 2019 2:56:02 AM GMT+01:00, cketti <xxx> wrote:
>The quick brown fox jumps over the lazy dog=2E All work and no play makes
>
>Jack a dull boy

The original message is displayed correctly. But when the text is added as quoted text the line breaks from the message source are retained. Ideally, we'd use the same code to extract the text for the viewing and for the composing part in K-9 Mail.

@cketti cketti added type: bug Something is causing incorrect behavior or errors status: help wanted Issues seeking help from the community labels Jan 9, 2019
@Iey4iej3
Copy link

Iey4iej3 commented Oct 8, 2020

I signal a similar case. I find that some of my emails are rendered incorrectly which might be related to this. I get a test (which is not perfect but reflect something abnormal):

Reply to

Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US

A line extremely extremely extremely extremely extremely extremely 
extremely extremely extremely extremely extremely extremely long long 
long long long long long long long long long long long long long long 
long long long.

> A line extremely extremely extremely extremely extremely extremely 
> extremely extremely extremely extremely extremely extremely long long 
> long long long long long long long long long long long long long long 
> long long long.

See above

will give

Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

XXX wrote:
>A line extremely extremely extremely extremely extremely extremely=20
>extremely extremely extremely extremely extremely extremely long long=20
>long long long long long long long long long long long long long long=20
>long long long=2E
>
>> A line extremely extremely extremely extremely extremely extremely=20
>> extremely extremely extremely extremely extremely extremely long long
>
>> long long long long long long long long long long long long long long
>
>> long long long=2E
>
>See above

@GNUDimarik
Copy link
Contributor

Seems people suffering without it https://www.ietf.org/rfc/rfc2646.txt :-D
@cketti is this still isn't implemented?

@GNUDimarik
Copy link
Contributor

Ok then. I'll find time for working on this in next week since people thinks it's priorty issue :-)

@joelchrono12
Copy link

I had a similar, if not the same problem recently, I just append it here to keep this issue alive :P

https://forum.k9mail.app/t/fix-wrapping-of-messages-with-fixed-width-linebreaks/2871/3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something is causing incorrect behavior or errors
Projects
None yet
4 participants