Bug #32273 for MIME-tools: Re: Bug#460411: MIME::Entity wrong about *digest* boundaries

Sun Jan 13 06:18:36 2008 jidanni [...] jidanni.org - Ticket created

CC:	460411 [...] bugs.debian.org, bug-mime-tools [...] rt.cpan.org
Subject:	Re: Bug#460411: MIME::Entity wrong about digest boundaries
Date:	Sun, 13 Jan 2008 19:18:03 +0800
To:	dfs [...] roaringpenguin.com
From:	jidanni [...] jidanni.org

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.

Sun Jan 13 22:23:46 2008 jidanni [...] jidanni.org - Correspondence added

CC:	460411 [...] bugs.debian.org, bug-MIME-tools [...] rt.cpan.org
Subject:	mulitpart/digest newline needed after boundary [rt.cpan.org #32273]
Date:	Mon, 14 Jan 2008 11:23:20 +0800
To:	dfs [...] roaringpenguin.com
From:	jidanni [...] jidanni.org

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);

Mon Jan 14 00:17:59 2008 jidanni [...] jidanni.org - Correspondence added

CC:	ding [...] gnus.org
Subject:	mulitpart/digest newlines around boundaries [rt.cpan.org #32273]
Date:	Mon, 14 Jan 2008 13:17:03 +0800
To:	bug-mime-tools [...] rt.cpan.org
From:	jidanni [...] jidanni.org

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

Thu Apr 29 11:24:11 2010 dmo+pause [...] dmo.ca - Correspondence added

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.

Thu Apr 29 11:24:12 2010 The RT System itself - Status changed from 'new' to 'open'

Thu Apr 29 11:24:12 2010 dmo+pause [...] dmo.ca - Status changed from 'open' to 'rejected'