The module produces output with incorrect nesting of multi-part types? Spam filters reject the messages in some cases. SpamAssassin gives an "EXTRA_MPART_TYPE" error on all emails sent using the module. Here is the offending nesting structure:

This is a multi-part message in MIME format.

--635bb4d496312ecdbddfccda0acf258a
Content-Type: multipart/alternative;
    boundary="b1205c2253bf6427e24c4cda4160d20c"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

--b1205c2253bf6427e24c4cda4160d20c
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

Bla Bla Bla

--b1205c2253bf6427e24c4cda4160d20c
Content-Type: text/html; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
</head>
<body id="mimemail-body">
<div id="content">
Bla Bla Bla
</div></body></html>

--b1205c2253bf6427e24c4cda4160d20c--

--635bb4d496312ecdbddfccda0acf258a--

Let me know if you need more information.

Comments

sgabe’s picture

Status: Active » Fixed

EXTRA_MPART_TYPE matches on Content-Type headers with a type parameter. RFC 2387 specifies that "multipart/related" MUST have a type parameter giving the MIME type of the root body part. The type parameter was introduced by #372710: HTML emails are text-only in Hotmail. However this has been fixed in SpamAssasin by lowering down it's score. See Bug 5110 and Bug 5270 for more information.

gregarios’s picture

Ok, thanks.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.