[Mailman-Users] header as text and message as attachemt

Brad Knowles brad.knowles at skynet.be
Tue Jun 8 13:28:04 CEST 2004

At 6:40 PM +0200 2004-06-07, Matthias Rieber wrote:

>  when I add a header to the message, the message will be send as
>  attachemnt. The message is *not* html. It looks like this:

	I wonder if this may be a problem with character set differences 
(or perceived differences) in the headers versus the bodyparts versus 
the footers.  Comments below:

>  Date: Mon, 7 Jun 2004 18:31:18 +0200 (CEST)
>  <Pine.LNX.4.60.0406071828190.18605 at tld.de>
>  MIME-Version: 1.0
>  Content-Type: MULTIPART/MIXED;
>      BOUNDARY="-1521340903-909602307-1086625878=:18605"
>  From: xxx.xx
>  Subject: test 1 2 3
>  X-BeenThere: xxx.xx
>  X-Mailman-Version: 2.1.4
>  Precedence: list
>  Reply-To: lists at xxx
>  Cc: news at air2mp3.net
>  To: Matthias Rieber <matthias at xxx.xx>
>  Sender: news-bounces at xxx.xx

	Not that there is no character set or content-transfer encoding 
listed in these headers.

>  ---1521340903-909602307-1086625878=:18605
>  Content-Type: text/plain; charset="iso-8859-1"
>  MIME-Version: 1.0
>  Content-Transfer-Encoding: quoted-printable
>  Content-Disposition: inline

	This is the first bodypart.  Note that the Content-Type header is:

		Content-Type: text/plain; charset="iso-8859-1"

	In particular, note the capitalization of "text/plain" and the 
double-quotes around "iso-8859-1".

	Note that the Content-Transfer-Encoding header is:

		Content-Transfer-Encoding: quoted-printable

	Note the capitalization of "quoted-printable".

>  ---1521340903-909602307-1086625878=:18605
>  Content-Type: TEXT/PLAIN; charset=iso-8859-1
>  Content-Transfer-Encoding: QUOTED-PRINTABLE

	This is the second bodypart.  Note the differences in 
capitalization of "TEXT/PLAIN", the lack of double-quote characters 
around "iso-8859-1", annd the difference in capitalization of the 

>  I was using the same config, except security updates (Debian Woody), some
>  month ago without any problems. I switched from pine 4.51 to 4.60. But I
>  tried the old version again, still the same problem.

	I'd be inclined to check the code to see if it is sensitive to 
differences in capitalization or presence/absence of quote 
characters.  Note that this might be a difference in the way Python 
handles things as opposed to Mailman, so you should check all the 
relevant code and modules for Python itself, as well as the Python 
code for Mailman.

Brad Knowles, <brad.knowles at skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

   SAGE member since 1995.  See <http://www.sage.org/> for more info.

More information about the Mailman-Users mailing list