[Bug 1251821] Re: Part x of 67 of a multipart message

Will Chapman qbuster at gmail.com
Mon Nov 18 10:04:55 CET 2013

Hello Mark,

Herewith an attempt to reproduce the error by attaching a similar file
to you

Saturday, November 16, 2013, 7:13:13 PM, you wrote:

> OK. So there are two issues. The first is that the attachment is sent in
> 67 or however many partial attachments and the second is that Mailman is
> sending 67 copies of each partial message instead of just 1.

> The first issue is due to the sending MUA (user's email client) breaking
> the large attachment across multiple messages (presumably Content-Type:
> message/partial) which have to be reassembled by the recipient's MUA.
> This issue is strictly due to the sending MUA and has nothing to do with
> Mailman.

> Note that splitting messages into multiple message/partial messages is a
> bad idea in general, both for security because most virus and spam
> scanners work only with the individual partial messages rather than the
> reassembled content, and because many MUAs don't know how to reassemble
> the partial messages into a complete whole.

> The second issue of Mailman sending multiple copies of each partial
> message is a bug somewhere. It may be something in the cPanel Exim
> Router/Transport definitions for Mailman or in cPanel Mailman or in
> Mailman itself. It is hard to say without seeing server logs, but if you
> could send a message with an attached PDF (preferably not TOO big) in
> the same way it's sent to Mailman to mark at msapiro.net, I can do some
> testing.

> You probably do not have access to any server logs. If I don't find
> anything, you'll have to take this up with your cPanel host. See the FAQ
> at <http://wiki.list.org/x/sYA9>.

Best regards,
  mailto:nbquidditch at btinternet.com

** Attachment added: "Flood_Risk_Assessment_&_Drainage_Strategy_Part1.pdf"

You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.

  Part x of 67 of a multipart message

To manage notifications about this bug go to:

More information about the Mailman-coders mailing list