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

Owner: Nobody in particular
Requestors: jidanni [...]

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

CC: 460411 [...], bug-mime-tools [...]
Subject: Re: Bug#460411: MIME::Entity wrong about *digest* boundaries
Date: Sun, 13 Jan 2008 19:18:03 +0800
To: dfs [...]
From: jidanni [...]
Download (untitled) / with headers
text/plain 1.3k
Show quoted text
>>>>> "DFS" == David F Skoll <> writes:
Show quoted text
DFS> wrote:
Show quoted text
>> I visited 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>
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, I would appreciate it.
Uh oh, is too complex. Two different accounts or whatever. I'll try mime-tools in bug-<distribution-name> ... the submit via email option. Maybe that will work. If it does, then "the bug is at ". 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 [...], bug-MIME-tools [...]
Subject: mulitpart/digest newline needed after boundary [ #32273]
Date: Mon, 14 Jan 2008 11:23:20 +0800
To: dfs [...]
From: jidanni [...]
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 [...]
Subject: mulitpart/digest newlines around boundaries [ #32273]
Date: Mon, 14 Jan 2008 13:17:03 +0800
To: bug-mime-tools [...]
From: jidanni [...]
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 . X-Spam-Langua X-Size: 4116 X-File: Mail/ ------------= Date: Mon, 14 From: patdoud Subject: GREE
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 infrastructure.

Please report any issues with to