Skip Menu |
 

This queue is for tickets about the MIME-tools CPAN distribution.

Report information
The Basics
Id: 32273
Status: rejected
Priority: 0/
Queue: MIME-tools

People
Owner: Nobody in particular
Requestors: jidanni [...] jidanni.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Received: from x1.develooper.com (x1.develooper.com [63.251.223.170]) by diesel.bestpractical.com (Postfix) with SMTP id 0F3C64D8070 for <bug-mime-tools [...] rt.cpan.org>; Sun, 13 Jan 2008 06:18:25 -0500 (EST)
Received: (qmail 16977 invoked from network); 13 Jan 2008 11:18:25 -0000
Received: from x16.dev (10.0.100.26) by x1.dev with QMQP; 13 Jan 2008 11:18:25 -0000
Received: from lax-green-bigip-5.dreamhost.com (HELO blingymail-a1.g.dreamhost.com) (208.113.200.5) by 16.mx.develooper.com (qpsmtpd/0.40-dev) with ESMTP; Sun, 13 Jan 2008 03:18:22 -0800
Received: from jidanni2 (122-127-54-159.dynamic.hinet.net [122.127.54.159]) by blingymail-a1.g.dreamhost.com (Postfix) with ESMTP id 45D0D5CDCE; Sun, 13 Jan 2008 03:18:10 -0800 (PST)
CC: 460411 [...] bugs.debian.org, bug-mime-tools [...] rt.cpan.org
Delivered-To: cpan-bug+mime-tools [...] diesel.bestpractical.com
MIME-Version: 1.0
Subject: Re: Bug#460411: MIME::Entity wrong about *digest* boundaries
X-Spam-Status: No, hits=-2.6 required=8.0 tests=BAYES_00
Return-Path: <jidanni [...] jidanni.org>
X-Spam-Check-BY: 16.mx.develooper.com
X-Original-To: bug-mime-tools [...] rt.cpan.org
Date: Sun, 13 Jan 2008 19:18:03 +0800
X-Spam-Level: *
Message-Id: <87y7au0yac.fsf [...] jidanni.org>
References: <4788D136.6090909 [...] roaringpenguin.com>
content-type: text/plain; charset="utf-8"
To: dfs [...] roaringpenguin.com
From: jidanni [...] jidanni.org
X-RT-Original-Encoding: us-ascii
Content-Length: 1429
Download (untitled) / with headers
text/plain 1.3k
Show quoted text
>>>>> "DFS" == David F Skoll <dfs@roaringpenguin.com> writes:
Show quoted text
DFS> jidanni@jidanni.org wrote:
Show quoted text
>> I visited http://www.mimedefang.org/ but could not find a Submit Bug >> button. Never mind.
Show quoted text
DFS> The proper place to submit bug reports for CPAN modules is DFS> http://rt.cpan.org/Public/Dist/Display.html?Name=mime-tools
OK, wish what we see in the debian package would mention that. Or maybe it did. Show quoted text
>> MIME::Entity has got it wrong about *digest* boundaries.
Show quoted text
DFS> Yes, probably. We'll look into it. If you wouldn't mind opening a DFS> ticket on rt.cpan.org, I would appreciate it.
Uh oh, https://rt.cpan.org/index.html?goto=/Public/Dist/Display.html%3FName%3Dmime-tools is too complex. Two different accounts or whatever. I'll try mime-tools in bug-<distribution-name>@rt.cpan.org: bug-mime-tools@rt.cpan.org ... the submit via email option. Maybe that will work. If it does, then "the bug is at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460411 ". Show quoted text
DFS> A workaround that I'd recommend is to make each sub-part of the digest DFS> a message/rfc822 entity and include everything (headers and all) in the DFS> body part. MIME-tools always wants to add at least a Content-Type: DFS> header to every subpart and fixing that is unlikely to happen.
But my spam digest has no bodies... Actually I was using a RFC1153 digest with no such bloat until I ran into some MUAs that wanted a MIME digest... OK, thanks. See ya.
CC: 460411 [...] bugs.debian.org, bug-MIME-tools [...] rt.cpan.org
MIME-Version: 1.0
X-Spam-Status: No, hits=-2.6 required=8.0 tests=BAYES_00
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: us-ascii
Received: from x1.develooper.com (x1.develooper.com [63.251.223.170]) by diesel.bestpractical.com (Postfix) with SMTP id 405254D80A2 for <bug-MIME-tools [...] rt.cpan.org>; Sun, 13 Jan 2008 22:23:39 -0500 (EST)
Received: (qmail 9390 invoked from network); 14 Jan 2008 03:23:38 -0000
Received: from x16.dev (10.0.100.26) by x1.dev with QMQP; 14 Jan 2008 03:23:38 -0000
Received: from lax-green-bigip-5.dreamhost.com (HELO blingymail-a1.g.dreamhost.com) (208.113.200.5) by 16.mx.develooper.com (qpsmtpd/0.40-dev) with ESMTP; Sun, 13 Jan 2008 19:23:37 -0800
Received: from jidanni1 (122-127-46-235.dynamic.hinet.net [122.127.46.235]) by blingymail-a1.g.dreamhost.com (Postfix) with ESMTP id 89EED5C634; Sun, 13 Jan 2008 19:23:32 -0800 (PST)
Delivered-To: cpan-bug+MIME-tools [...] diesel.bestpractical.com
Subject: mulitpart/digest newline needed after boundary [rt.cpan.org #32273]
Return-Path: <jidanni [...] jidanni.org>
X-Spam-Check-BY: 16.mx.develooper.com
X-Original-To: bug-MIME-tools [...] rt.cpan.org
Date: Mon, 14 Jan 2008 11:23:20 +0800
X-Spam-Level: *
Message-Id: <87k5mdks47.fsf [...] jidanni.org>
To: dfs [...] roaringpenguin.com
From: jidanni [...] jidanni.org
X-RT-Original-Encoding: utf-8
RT-Message-ID: <rt-3.6.HEAD-16275-1200281026-1282.32273-0-0 [...] rt.cpan.org>
Content-Length: 1095
Show quoted text
> make each sub-part of the digest a message/rfc822 entity
OK, now the hard-to-get-rid-of empty line after each boundary is what makes the digest pleasant tasting to mutt, etc. I am now in a "unpleasant things that I wish not to understand further but worksforme" state. "Maybe it was all due to a lack of man page documentation for us minority mulitpart/digest guys." OK, thanks. < push @{ $headers{$name} }, $_, $bighead->get_all($_); --- Show quoted text
> $headers{$name} .= "$_: " . $bighead->get($_);
< push @{ $headers{$name} }, "X-Size", $size, "X-File", $name; --- Show quoted text
> $headers{$name} .= "X-Size: $size\nX-File: $name"; #be stingy:no \n
< $top->attach( --- Show quoted text
> my $part = MIME::Entity->build( > Type => "message/rfc822", #be stingy:
< @{ $headers{$_} }, "Data", < "" --- Show quoted text
> Top => 0, > Data => $headers{$_} > $top->add_part($part);
< my $repair = $top->stringify; < $repair =~ s/^------------=_.*/$&\n/gm; ##RFC 2046 and mutt and gnus DIGESTS < print MAIL $repair; --- Show quoted text
> $top->print(\*MAIL);
CC: ding [...] gnus.org
MIME-Version: 1.0
X-Spam-Status: No, hits=-2.6 required=8.0 tests=BAYES_00
References: <87k5mdks47.fsf [...] jidanni.org>
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: us-ascii
Received: from x1.develooper.com (x1.develooper.com [63.251.223.170]) by diesel.bestpractical.com (Postfix) with SMTP id 3C1F44D80A2 for <bug-mime-tools [...] rt.cpan.org>; Mon, 14 Jan 2008 00:17:32 -0500 (EST)
Received: (qmail 22190 invoked from network); 14 Jan 2008 05:17:31 -0000
Received: from x16.dev (10.0.100.26) by x1.dev with QMQP; 14 Jan 2008 05:17:31 -0000
Received: from lax-green-bigip-5.dreamhost.com (HELO blingymail-a1.g.dreamhost.com) (208.113.200.5) by 16.mx.develooper.com (qpsmtpd/0.40-dev) with ESMTP; Sun, 13 Jan 2008 21:17:28 -0800
Received: from jidanni1 (122-127-46-235.dynamic.hinet.net [122.127.46.235]) by blingymail-a1.g.dreamhost.com (Postfix) with ESMTP id 8D4B85C634; Sun, 13 Jan 2008 21:17:23 -0800 (PST)
Delivered-To: cpan-bug+mime-tools [...] diesel.bestpractical.com
Subject: mulitpart/digest newlines around boundaries [rt.cpan.org #32273]
Return-Path: <jidanni [...] jidanni.org>
X-Original-To: bug-mime-tools [...] rt.cpan.org
X-Spam-Check-BY: 16.mx.develooper.com
Date: Mon, 14 Jan 2008 13:17:03 +0800
X-Spam-Level: *
Message-Id: <87wsqdj8a8.fsf [...] jidanni.org>
To: bug-mime-tools [...] rt.cpan.org
From: jidanni [...] jidanni.org
X-RT-Original-Encoding: utf-8
RT-Message-ID: <rt-3.6.HEAD-16275-1200287879-1601.32273-0-0 [...] rt.cpan.org>
Content-Length: 486
Download (untitled) / with headers
text/plain 486b
Show quoted text
> $headers{$name} .= "X-Size: $size\nX-File: $name"; #be stingy:no \n
Now find I need \n\n here at EOL instead of none, for gnus. In other words the environment around a boundary between messages in an mulitpart/digest needs to at least be as below. Mutt is not as picky. Note my mulitpart/digest are just collections of spam headers with no bodies, see http://jidanni.org/comp/spam/ . X-Spam-Langua X-Size: 4116 X-File: Mail/ ------------= Date: Mon, 14 From: patdoud Subject: GREE
MIME-Version: 1.0
In-Reply-To: <87y7au0yac.fsf [...] jidanni.org>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
References: <4788D136.6090909 [...] roaringpenguin.com> <87y7au0yac.fsf [...] jidanni.org>
Content-Type: text/plain; charset="UTF-8"
Message-ID: <rt-3.8.HEAD-6788-1272554651-741.32273-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 163
Download (untitled) / with headers
text/plain 163b
Rejecting, as I'm not sure what this is trying to accomplish, nor how to verify that we don't do it anymore. Please reopen with a testcase if you think I'm wrong.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.