Hi,
(the other reason is to handle the Resent-* headers).
I use dist a lot. Note some email clients, Gmail included at one point
though perhaps not any more, *don't* display the resend-* headers which
can lead to confusion by recipients.
Cheers, Ralph.
Hi Ken,
I know those Resent-* headers have been in the RFCs forever, but it
seems that many MUA authors have forgotten about them. Does anything
other than dist generate them?
Sure, mutt(1) for one when you `bounce'.
Cheers, Ralph.
___
Sure, mutt(1) for one when you `bounce'.
Heirloom mail for another; it has `resend' and `Resend' commands; the
latter adds no headers.
Cheers, Ralph.
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
As Jerrad already explained, that's the way that dist
works. I always found it a bit weird myself, but I guess
the authors of dist didn't want people to alter the draft
message. That's part of the reason there's a whole bunch
of special case code for dist in send (the other reason
is to
Sure, mutt(1) for one when you `bounce'.
Heirloom mail for another; it has `resend' and `Resend' commands; the
latter adds no headers.
Fair enough; thanks for the info, Ralph!
--Ken
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
I use dist (via mh-e) all the time to add people who were not Cc'd.
Confuses the hell out of Outlook and Thunderbird users. That's part of
the charm.
Thanks
Jeff
--
Jeffrey C. Honig j...@honig.net
http://www.honig.net/jch
GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml
