so it turns out that if you attach a mail message to your draft, using:
Attach: /home/pgf/Mail/inbox/1982
then mhbuild will generate this:
Content-Type: message/rfc822; name="1982"
Content-Description: 1982
Content-Disposition: attachment; filename="1982"
which is fine. except that gmail, at least, apparently won't
do anything at all with attachments except let you save them
to a file, which isn't the friendliest thing to do to someone
when you're forwarding them a piece of mail you'd like them
to read.
if you do the above, then run mime at whatnow?, and manually change
"attachment" to "inline", then gmail does exactly the right thing, and
the recipient can see what you sent.
many possibilities come to mind -- politely ask gmail to fix their
email infrastructure, augment "Attach:" with "Inline:", make "Attach:"
always generate "C-D: inline" for some content types, never use
"Attach:" for email messages, go back to using raw mhbuild
directives for everything, etc.
any ideas?
paul
=----------------------
paul fox, pgf(_at_)foxharp(_dot_)boston(_dot_)ma(_dot_)us (arlington, ma,
where it's 53.4 degrees)
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers