MIME boundary being set incorrectly

Bug #265623 reported by Tgrace
2
Affects Status Importance Assigned to Milestone
GNU Mailman
Invalid
Medium
Unassigned

Bug Description

In 2.0.8, if a user has chosen to receive a MIME
digest, the mime boundary is declared as --__--__--
but the actual boundary used is __--__--

This causes problems for some mail servers.

[http://sourceforge.net/tracker/index.php?func=detail&aid=538001&group_id=103&atid=100103]

Revision history for this message
Barry Warsaw (barry) wrote :

You might be thinking of the plain text digests, which don't
set a boundary parameter on the Content-Type: header (and
actually, the Content-Type: header isn't even multipart0.
Plain text digests uses --__--__-- as a separator, which is
allowed by RFC 934.

MIME digests use a different boundary, which is properly set
and used.

Revision history for this message
Tgrace (tgrace) wrote :
Download full text (5.4 KiB)

Here's an example from my MIME digest subscription:

List-Unsubscribe:
<http://www.tgrace.com/mailman/listinfo/nortel-list>,
 <mailto:<email address hidden>?
subject=unsubscribe>
List-Archive: <http://www.tgrace.com/mailman/private/nortel-
list/>

--192.206.167.199.1002.2397.1017766802.776.17036
Content-type: text/plain; charset=us-ascii
Content-description: Masthead (Nortel-list digest, Vol 1
#1037)

--192.206.167.199.1002.2397.1017766802.776.17036
Content-type: text/plain; charset=us-ascii
Content-description: Today's Topics (38 msgs)

--192.206.167.199.1002.2397.1017766802.776.17036
Content-type: multipart/digest; boundary="__--__--"

--__--__--

Message: 1

etc

Outlook seems to interpret it ok, giving me a text file
attachment with a summary of the message, an attachment
containing individual messages for the last 24 hours, and
the list footer. I have dbl checked my subscription and it
is indeed set to MIME digest. The following is a complete
header from todays digest up to msg 2:

Received: from mailrelay.thestar.ca ([150.150.14.161]) by
snads.thestar.ca with SMTP (Microsoft Exchange Internet
Mail Service Version 5.5.2650.21)
 id H43R2LLX; Tue, 2 Apr 2002 11:57:54 -0500
Received: from [192.206.167.199] by mailrelay.thestar.ca
(NTMail 7.02.3028/NY6754.00.c310e891) with ESMTP id
njdtzbaa for <email address hidden>; Tue, 2 Apr 2002 12:02:24 -
0500
Received: from snoopy.tgrace.com (localhost [127.0.0.1])
 by snoopy.tgrace.com (8.12.1/8.12.1) with ESMTP id
g32H11wd002557;
 Tue, 2 Apr 2002 12:01:01 -0500 (EST)
Date: Tue, 2 Apr 2002 12:01:01 -0500 (EST)
Message-Id: <email address hidden>
From: <email address hidden>
Subject: Nortel-list digest, Vol 1 #1037 - 38 msgs
X-Mailer: Mailman v2.0.8
MIME-version: 1.0
Content-type: multipart/mixed;
boundary=192.206.167.199.1002.2397.1017766802.776.17036
To: <email address hidden>
Sender: <email address hidden>
Errors-To: <email address hidden>
X-BeenThere: <email address hidden>
X-Mailman-Version: 2.0.8
Precedence: bulk
Reply-To: <email address hidden>
X-Reply-To: <email address hidden>
List-Help: <mailto:<email address hidden>?
subject=help>
List-Post: <mailto:<email address hidden>>
List-Subscribe:
<http://www.tgrace.com/mailman/listinfo/nortel-list>,
 <mailto:<email address hidden>?
subject=subscribe>
List-Id: Mailing list for Northern Telecom related issues
<nortel-list.tgrace.com>
List-Unsubscribe:
<http://www.tgrace.com/mailman/listinfo/nortel-list>,
 <mailto:<email address hidden>?
subject=unsubscribe>
List-Archive: <http://www.tgrace.com/mailman/private/nortel-
list/>

--192.206.167.199.1002.2397.1017766802.776.17036
Content-type: text/plain; charset=us-ascii
Content-description: Masthead (Nortel-list digest, Vol 1
#1037)

--192.206.167.199.1002.2397.1017766802.776.17036
Content-type: text/plain; charset=us-ascii
Content-description: Today's Topics (38 msgs)

--192.206.167.199.1002.2397.1017766802.776.17036
Content-type: multipart/digest; boundary="__--__--"

--__--__--

Message: 1
To: <email address hidden>
Subject: RE: [Nortel-list] AUD313
MIME-Version: 1.0
Message-ID: <OFC40A8F2E.FBAC6BF3-
ON86256B8E.005D...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.