Ok, now we're getting somewhere. I had $mime_forward=no. If I set
$mime_forward=ask-yes, do the tag ;f, and say yes to mime it works.
(Thanks for your previous post about $mime_forward!)
One more wrinkle. I'm not sure how to say this, so here's a screen
shot of the latest test I did. (Had to make up some email, since the
original is long since gone.) Say the original email I got looked
sort of like:
1 <no description> [text/plain, 7bit, 0.1K]
2 test [message/rfc822, 7bit, 174K]
3 tq><no description> [text/plain, 7bit, 0.1K]
4 tq>one.bmp [applica/octet-stre, base64, 86K]
5 mq>two.bmp [applica/octet-stre, base64, 86K]
I tagged just two.bmp, did ;f and sent it to myself. It looked like a
single attachment when I sent it. Here's the message that was
produced.
1 <no description> [text/plain, 7bit, 0.1K]
2 Fwd: test [message/rfc822, 7bit, 87K]
3 mq>two.bmp [applica/octet-stre, base64, 86K]
It included the message/rfc822 (#2 originally, #2 now) part from the
original message. It didn't include any of the text/plain part from
the original, just the headers.
It's not that of a deal, but there are times when I don't really want
the original headers traveling in my forward. Ideas?
Thanks for you help!
Rob
On Thu, Oct 21, 1999 at 08:54:33AM +0200, Jan Houtsma wrote:
> hmm strange. i tried a mix with 2 text files and one jpg file
> and it worked fine.
> also Mutt 1.0pre3us (1999-09-25).
>
> jan
