[ mailman-Bugs-1337731 ] Content-Transfer-Encoding header missing

SourceForge.net noreply at sourceforge.net
Thu Oct 27 03:00:08 CEST 2005

Bugs item #1337731, was opened at 2005-10-25 18:37
Message generated for change (Comment added) made by tkikuchi
You can respond by visiting: 

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: 2.0.x
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: DrV (i_am_drv)
Assigned to: Nobody/Anonymous (nobody)
Summary: Content-Transfer-Encoding header missing

Initial Comment:
When sending a digest, Mailman 2.0.9 doesn't include a
Content-Transfer-Encoding header, yet it seems to
encode the messages with quoted-printable.  As per IRC
  "Content-Transfer-Encoding: 7BIT" is assumed if the
Content-Transfer-Encoding header field is not present.

In particular, =## sequences are included, which are
not decoded correctly by mail readers (tested with
Mozilla Thunderbird), because the
Content-Transfer-Encoding does not specify

The digests include correct MIME version and
Content-type headers, but Content-Transfer-Encoding has
been missing in all cases I have seen.

>From - Tue Oct 25 12:01:55 2005
X-Account-Key: account2
X-UIDL: 406934627
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Received: from lists-outbound.sourceforge.net
[] by wwimail002.winsdns.com with ESMTP
  (SMTPD32-8.15) id A05B2BFF00F0; Tue, 25 Oct 2005
01:19:23 -0400
Received: from projects.sourceforge.net
(sc8-sf-list2-b.sourceforge.net [])
	by sc8-sf-spam1.sourceforge.net (Postfix) with ESMTP
	id E7BDE88948; Mon, 24 Oct 2005 22:20:05 -0700 (PDT)
Date: Mon, 24 Oct 2005 22:09:26 -0700
From: freedos-devel-request at lists.sourceforge.net
Subject: Freedos-devel digest, Vol 1 #668 - 4 msgs
X-Mailer: Mailman v2.0.9-sf.net
MIME-version: 1.0
Content-type: text/plain
To: freedos-devel at lists.sourceforge.net
Sender: freedos-devel-admin at lists.sourceforge.net
Errors-To: freedos-devel-admin at lists.sourceforge.net
X-BeenThere: freedos-devel at lists.sourceforge.net
X-Mailman-Version: 2.0.9-sf.net
Precedence: bulk
Reply-To: freedos-devel at lists.sourceforge.net
X-Reply-To: freedos-devel at lists.sourceforge.net
	<mailto:freedos-devel-request at lists.sourceforge.net?subject=unsubscribe>
List-Id: <freedos-devel.lists.sourceforge.net>
List-Post: <mailto:freedos-devel at lists.sourceforge.net>
<mailto:freedos-devel-request at lists.sourceforge.net?subject=help>
	<mailto:freedos-devel-request at lists.sourceforge.net?subject=subscribe>
<20051025052005.E7BDE88948 at sc8-sf-spam1.sourceforge.net>

I have only verified this for digests sent by
"X-Mailer: Mailman v2.0.9-sf.net" (for mailing lists of
sf.net projects).


>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2005-10-27 01:00

Logged In: YES 

mailman 2.1.x includes the fix. Please update.


You can respond by visiting: 

More information about the Mailman-coders mailing list