Closed paulgriffiths closed 4 years ago
Note that RFC 8951 subsequently (in November 2020) updated RFC 7030 to require all endpoints to ignore the value in any Content-Transfer-Encoding header, and to specifically confirm that:
Senders are not required to insert any kind of white space.
PR #31 has been raised to deprecate the Content-Transfer-Encoding header per RFC 8951
Per section 6.8 of RFC2045 which defines the Content-Transfer-Encoding header:
Currently, no line breaks appear in base64-encoded output.
All base64-encoded output used in a message with a Content-Transfer-Encoding value of base64 should be broken into lines of 76 or less characters.