Hi Thomas,
On Sunday, December 24, 2000, 1:28:55 AM, you wrote to the list:
>>> I feel that there is a potential for problems with the current
>>> process, in which a "Reply to all" includes the original/main
>>> recipient of the email of which you received a Blind Copy
MSG>> I really agree with this one. A friend of mine just had a
MSG>> similar situation occur when one of his employees replied to him
MSG>> about a client but inadvertently sent a copy of his reply about
MSG>> the client to the client as well because he hadn't realized the
MSG>> client had received a bcc of the email sent to him! It took a
MSG>> bit of fast talking to the client to get out of that one.
TF> I doubt this. When the client received a BCC copy, then it would
TF> not be in the headers of your friend's employee's incoming email
TF> at all. He can hit Reply All all he wants, the reply will go only
TF> to the addresses in the TO and CC headers of the incoming email.
100 % correct, and RFC state as that. BCC: address *must* not listed
on the recipient message header.
But on some condition, which the postmaster not well setting his MTA,
the bcc: header listed on the Message header of recipient.
I saw this happent on Qmail MTA user who use mail aliasing , user
[EMAIL PROTECTED] send mail to some addresses on bcc:, and one of them is
[EMAIL PROTECTED], then [EMAIL PROTECTED] can see all address on the bcc: list,
it's shame :-(
On that case, click reply to all will put all listed address on cc:
list, note that not only TB! will do this, but most E-mail client will
do as well.
My comment is this is MTA fault, not TB! fault, so address this fault
to the Postmaster.
--
Best regards,
Syafril mailto:[EMAIL PROTECTED]
--
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team double click here:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, double click here and send the message:
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
You are subscribed as : [email protected]
