From: Michael Grubb <mg@duke.edu>
Subject: feature request for Bcc
Date: 06 Nov 1996 17:51:51 -0500 [thread overview]
Message-ID: <vw1zq0ualbs.fsf@cambot.oit.duke.edu> (raw)
It would be nice if blind carbon copy (Bcc) recipients saw something
indicating it was a Bcc. Really, anything in the headers or text would
be helpful. MH does this by inserting a " ----- Blind Carbon Copy" line
at the beginning of the message body, which is kinda nice.
Just a thought. Or maybe there's already a way to do this?
-- M.
--
Michael Grubb <mg@duke.edu>
Duke University Office of Information Technology
phone +1 919 660 6903 / 409 North Building, Durham NC 27708-0132 USA
next reply other threads:[~1996-11-06 22:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-06 22:51 Michael Grubb [this message]
1996-11-07 11:54 ` Samuel Tardieu
1996-11-08 1:37 ` Lars Magne Ingebrigtsen
1996-11-07 9:06 ` Kai Grossjohann
1996-11-07 9:21 ` Lars Balker Rasmussen
1996-11-07 16:29 ` Eric Hendrickson
1996-11-06 23:32 Katsumi Yamaoka
1996-11-07 1:06 ` Michael Grubb
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=vw1zq0ualbs.fsf@cambot.oit.duke.edu \
--to=mg@duke.edu \
/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).