[issue18886] BytesGenerator does not handle 'binary' CTE correctly

R. David Murray added the comment: Just 3.6 at this point, since really support for CTE binary is a new feature (there may even be a separate issue saying that, in which case this one should be closed as a duplicate). We don't auto-update the issue versions when a new release comes out. Issu

[issue18886] BytesGenerator does not handle 'binary' CTE correctly

Nathaniel Manista added the comment: Also what's this bug's relationship to 19003? -- ___ Python tracker ___ ___ Python-bugs-list mail

[issue18886] BytesGenerator does not handle 'binary' CTE correctly

Nathaniel Manista added the comment: This is status:open but versions:3.3,3.4. Should 3.5 and 3.6 also be listed as being affected by this issue? -- nosy: +Nathaniel Manista ___ Python tracker

[issue18886] BytesGenerator does not handle 'binary' CTE correctly

R. David Murray added the comment: cte binary has nothing to do with headers (other than appearing as the value of the content-transfer-encoding header). It is about how the body of the email is handled. ByteGenerator needs to be modified to not do anything with a payload whose cte is binary

[issue18886] BytesGenerator does not handle 'binary' CTE correctly

Surya K added the comment: Forget about my previous comment. David Murray: One possible way to fix this issue is to ignore email.header.Header.encode() on Message values in email._policybase_Compat32._fold() if they come from BytesGenerator and not Generator. We can do this by encoding the val

[issue18886] BytesGenerator does not handle 'binary' CTE correctly

Surya K added the comment: I have a fix for this. But before putting it forward, can you please tell me about the below 1. email.header.Header.encode() --method How different is it from str.encode()? Does [1] method also performs what str.encode() does internally? -- nosy: +suryak __

[issue18886] BytesGenerator does not handle 'binary' CTE correctly

New submission from R. David Murray: ByteGenerator will assume that it can change any linesep characters to the linesep being used for the general message serialization, even if the content transfer encoding is 'binary'. This is incorrect, as existing \r and \n characters in binary parts must