Re: forward messages to Eudora users is painful
Eric Jensen <ejensen1 <at> swarthmore.edu>
2003-09-04 18:09:31 GMT
In making the switch to a newer version of mh-e from an much older
one, I've found this way of forwarding messages to be hard to get
used to, precisely due to the problem Kevin mentions: unless I mess
with the message before sending it, I can't be confident that the
recipient will be able to read it. Could someone who knows more than
I do about mh-e comment on why the message is sent as an attachment?
That is, what would happen, or what features would be lost, if the
Content-Disposition were "inline" instead of "attachment"? Might it
be useful to have an optional switch to mh-forward (or a separate
function, I suppose) that would forward a simple message inline? I'm
guessing the reason for doing it as an attachment is to preserve
attachments in the original message as well.
In the meantime, Kevin, a workaround would be to have something that
adds the ".txt" automatically when you forward a message. You could
do something like this in your .emacs, to run some code whenever
mh-forward is invoked. This is a modified version of something I
use, but I haven't tested this version, so double-check it.
(defadvice mh-forward (after mh-forward-after activate)
"Commands to run after mh-forward to slightly modify the
way messages are forwarded."
; Use mh-mml-to-mime to expand the forwarded message into the buffer
; Change the filename of the forwarded message so Eudora can handle it
(if (search-forward "Content-Disposition: attachment\; filename=" nil t)