Éric Araujo added the comment:
Mitchell Hashimoto provided this link on a duplicate report:
> RFC2616 page 31 (http://tools.ietf.org/html/rfc2616#page-31) states that
> headers must be separated
> by CRLF. Specifically, the above "\n\n" for the header separator is causing
> issues with some
>
R. David Murray added the comment:
I know this is closed so the comment may not be relevant, but the byte/string
issues with email should be sorted out in the code that is in 3.2/3.3 at this
point. That is, it is possible once again to work with binary data, using the
correct (new) classes.
Éric Araujo added the comment:
> I'm having a look at this ticket now. It looks like this can be
> rewritten to use common code
Indeed! As such, I’m folding this feature request into #12169, which has a
patch under review.
--
resolution: -> duplicate
stage: needs patch -> committed/
