Re: [Nmh-workers] Forwarding MIME messages?

2004-05-20 Thread Nathan Bailey
Neil W Rickert <[EMAIL PROTECTED]> wrote: >Nathan Bailey <[EMAIL PROTECTED]> wrote on May 21, 2004: > forw -mime >to attach the original message as an rfc822 attachment. That does 90% of what I want, the only other bit is that occasionally I edit (gasp!) the messages to highlight the relevan

Re: [Nmh-workers] Forwarding MIME messages?

2004-05-20 Thread Jerry Peek
On 21 May 2004 at 10:06, Nathan Bailey <[EMAIL PROTECTED]> wrote: > Using forward (e.g. forw -format) means I have to clean up the message > by hand and re-attach any attachments -- a lot of work. I either use "forw -mime" (as Neil mentioned), or I put a #forw directive in the message body (which

Re: [Nmh-workers] Forwarding MIME messages?

2004-05-20 Thread Neil W Rickert
Nathan Bailey <[EMAIL PROTECTED]> wrote on May 21, 2004: >Using forward (e.g. forw -format) means I have to clean up the message >by hand and re-attach any attachments -- a lot of work. I could write You can use forw -mime to attach the original message as an rfc822 attachment. -NWR

[Nmh-workers] Forwarding MIME messages?

2004-05-20 Thread Nathan Bailey
I'm a long-time mh user (10+ years?) but possibly a fairly basic one (i.e. I don't necessarily know all the options available in its many features). I have found that the only way Windows users can easily see my attachments is doing them this way: #application/msword; name="whattheusersee