I stand corrected: Three different functions. The line
BCC: nsb(_at_)guppylake(_dot_)com
might better be represented as
I-Sent-a-BCC-To: nsb(_at_)guppylake(_dot_)com (for my files)
BCC-Should-Be-Sent-To: nsb(_at_)guppylake(_dot_)com
(written by a UA as a request to an MTA)
Why-You-Got-This: You were BCC'ed as nsb(_at_)guppylake(_dot_)com (for viewing
by the bcc recipient)
None of this makes me any more fond of bcc's. -- N
On Aug 13, 2004, at 7:15 PM, Bruce Lilly wrote:
Nathaniel Borenstein wrote:
But the bottom line is that software uses bcc
for two very different functions: to tell another email
transport-related entity to send a bcc, or to tell the user that he
has
received a bcc.
Not just the (Bcc recipient) user; also to remind the author (via his
file copy) to whom he sent bccs (perhaps some time after the fact).