Edit report at http://pear.php.net/bugs/bug.php?id=12716&edit=1
ID: 12716
Updated by: [email protected]
Reported By: joel at panacea dot null dot org
Summary: Invalid Content-Transfer-Encdoing on multipart
messages
-Status: Open
+Status: Bogus
Type: Bug
Package: Mail_Mime
Operating System: UNIX
Package Version: 1.5.2
PHP Version: Irrelevant
Roadmap Versions:
New Comment:
-Status: Open
+Status: Bogus
Mail_mime doesn't set Content-Transfer-Encoding for multipart messages.
Previous Comments:
------------------------------------------------------------------------
[2009-12-29 10:24:49] alec
Unable to reproduce. Could you provide a test script?
------------------------------------------------------------------------
[2007-12-18 00:26:22] jjr
Description:
------------
An email generated by Mail_Mime had the following headers.
...
MIME-Version: 1.0
From: <[email protected]>
Content-Type: multipart/alternative;
boundary="=_90be54e8dab1de0e2d340c1331fbc037"
Content-Transfer-Encoding: quoted-printable
...
According to
http://tools.ietf.org/html/rfc2045#section-6.4
this is in error. From the RFC:
Certain Content-Transfer-Encoding values may only be
used on certain
media types. In particular, it is EXPRESSLY FORBIDDEN
to use any
encodings other than "7bit", "8bit", or "binary" with
any composite
media type, i.e. one that recursively includes other
Content-Type
fields. Currently the only composite media types
are "multipart" and
"message". All encodings that are desired for bodies
of type
multipart or message must be done at the innermost
level, by encoding
the actual body that needs to be encoded.
Please include
[email protected]
in followups since while I noticed the problem, Francois
is managing the system.
------------------------------------------------------------------------
