[Mailman-Users] message body is blank for some users

[Mark Sapiro]

Heal Secretary wrote:
>
>The current filtering settings are -
>
>Should Mailman filter the content of list traffic according to the 
>settings below? YES
>Remove message attachments that have a matching content type. BLANK
>Remove message attachments that don't have a matching content type. 
>Leave this field blank to skip this filter test. BLANK
>Remove message attachments that have a matching filename extension A 
>LIST OF EXTENSIONS - EXE ETC
>Remove message attachments that don't have a matching filename 
>extension. Leave this field blank to skip this filter test BLANK


The net effect of the above is to remove all attachments with filename
extensions equal to one of the extensions in the list.


>Should Mailman collapse multipart/alternative to its first part content? YES

This could affect your issue. You could try setting it to No. When it
is set to yes, Mailman will replace a multipart/alternative part with
text/plain and text/html sub parts with just the text/plain part. If
that happens to be 'blank' you will get the result below.

However, the original message you posted at
<http://mail.python.org/pipermail/mailman-users/2006-August/052525.html>
was not structured in this way. It was a simple text/html message.


>Should Mailman convert text/html parts to plain text? This conversion 
>happens after MIME attachments have been stripped. NO


I'm surprised because 'Yes' combined with other problems seems to me to
be the most likely cause of this.


>Action to take when a message matches the content filtering rules. 
>FORWARD TO LIST OWNER
>
>I don't know what half of these mean so I'm none the wiser.
>If you think it would be a good plan I can turn content filtering off 
>altogether and ask Jonathan to send a new message......


That will allow everything to pass through Mailman as sent. Whether or
not this is a good idea depends on whether you want to filter the
attachments with matching file name extensions.


I would try setting collapse multipart/alternative to No first.


>Here's one of Jonathan's mails that was sent to the list with a blank 
>body (between asterisks)
>
>************************************************
> From ???@??? Wed May 31 19:18:38 2006
>Return-path: <activists-bounces at healheadingley.org.uk>
>Envelope-to: secretary at healheadingley.org.uk
>Delivery-date: Tue, 30 May 2006 21:23:59 +0100
>Received: from hopeful9 by colo16.ukhost4u.com with local-bsmtp (Exim 4.52)
>         id 1FlAkw-0006Ui-1F
>         for secretary at healheadingley.org.uk; Tue, 30 May 2006 21:23:59 +0100
>X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on colo16.ukhost4u.com
>X-Spam-Level:
>X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,
>         MSGID_FROM_MTA_HEADER autolearn=ham version=3.1.1
>Received: from localhost ([127.0.0.1] helo=colo16.ukhost4u.com)
>         by colo16.ukhost4u.com with esmtp (Exim 4.52)
>         id 1FlAkF-0006Pl-81; Tue, 30 May 2006 21:23:15 +0100
>Received: from [65.54.168.45] (helo=hotmail.com)
>         by colo16.ukhost4u.com with esmtp (Exim 4.52) id 1FlAkA-0006Of-6y
>         for activists at healheadingley.org.uk; Tue, 30 May 2006 21:23:10 +0100
>Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
>         Tue, 30 May 2006 13:23:15 -0700
>Message-ID: <BAY113-F35AF17143F677EB453ED2CD2920 at phx.gbl>
>Received: from 65.54.168.200 by by113fd.bay113.hotmail.msn.com with HTTP;
>         Tue, 30 May 2006 20:23:10 GMT
>X-Originating-IP: [62.252.224.13]
>X-Originating-Email: [Jonathan's email address]
>X-Sender: Jonathan's email address
>From: "Jonathan" <Jonathan's email address>
>To: activists at healheadingley.org.uk
>Bcc:
>Date: Tue, 30 May 2006 20:23:10 +0000
>X-OriginalArrivalTime: 30 May 2006 20:23:15.0960 (UTC)
>         FILETIME=[E1DCB780:01C68426]
>MIME-Version: 1.0
>X-Content-Filtered-By: Mailman/MimeDel 2.1.7


So it was manipulated by content filtering.


>Subject: [activists] Transport through Headingley
>X-BeenThere: activists at healheadingley.org.uk
>X-Mailman-Version: 2.1.7
>Precedence: list
>Reply-To: for local activists <activists at healheadingley.org.uk>
>Content-Type: text/plain; charset="us-ascii"


And content filtering converted it to a single text/plain part either
by collapsing a multipart/alternative part to the first subpart or by
converting an html part to plain text.

We think the second thing didn't happen because
convert_html_to_plaintext is No. The first thing is not consistent
with the message you posted earlier, so only further testing will tell.

Test 1 - set collapse multipart/alternative to No and see what happens.
If the post is still blank,

Test 2 - set filter_content.to No.

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan