> 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($_); --- > $headers{$name} .= "$_: " . $bighead->get($_); < push @{ $headers{$name} }, "X-Size", $size, "X-File", $name; --- > $headers{$name} .= "X-Size: $size\nX-File: $name"; #be stingy:no \n < $top->attach( --- > my $part = MIME::Entity->build( > Type => "message/rfc822", #be stingy: < @{ $headers{$_} }, "Data", < "" --- > 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; --- > $top->print(\*MAIL); -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]