From: Steven L Baur <steve@miranova.com>
Cc: ding@ifi.uio.no
Subject: Re: Forwarding mail
Date: 18 Jul 1996 10:34:05 -0700 [thread overview]
Message-ID: <m27ms14gaa.fsf@deanna.miranova.com> (raw)
In-Reply-To: David Lebel's message of 17 Jul 1996 22:54:04 -0400
>>>>> "David" == David Lebel <lebel@socom.com> writes:
David> Hello,
David> when forwarding mail, message.el (or is it TM?) is enclosing
David> the forwarded mail into a "Content-type: message/rfc822" MIME
David> enclosure. This is nice, however the enclosed mail doesn't keep the
David> original encoding type ...
That reminds me ...
Digest extraction with C-d has the same flaw, and is especially
painful with QP.
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone
except you in November.
next prev parent reply other threads:[~1996-07-18 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-18 2:54 David Lebel
1996-07-18 17:34 ` Steven L Baur [this message]
2017-04-26 20:59 forwarding mail David Mann
2017-04-26 21:20 ` Eric Abrahamsen
2017-04-26 23:18 ` Emanuel Berg
2017-04-27 17:06 ` David Mann
2017-04-28 20:30 ` Emanuel Berg
2017-04-29 4:13 ` David Mann
2017-04-27 6:21 ` Adam Sjøgren
2017-04-29 7:38 ` Sivaram Neelakantan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m27ms14gaa.fsf@deanna.miranova.com \
--to=steve@miranova.com \
--cc=ding@ifi.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).