A couple of years ago i had a tool (vbs script) in outlook 2000 that
revealed the bcc field on received items. That way it was possible to see
(as a receiver) to who the mail also was send to. Anyone familiar with this
tool because I lost it L

"K.P. CijsouwCijsouwk.nl>" <Kris@<> wrote in message
news:(E-Mail Removed)...
> A couple of years ago i had a tool (vbs script) in outlook 2000 that
> revealed the bcc field on received items. That way it was possible to see
> (as a receiver) to who the mail also was send to. Anyone familiar with
> this tool because I lost it L
>
>

Absolutely impossible. Because, the list of BCC recipients never leaves the
Senders machine....I think you must be thinking of something else...

If the BCC field never leaves the senders machine, then how is it possible
that the receiving mailserver knows to which mailbox/user the mail has to be
delivered?! I'm 100% positive that this tool exists (at least for Outlook
2000).

No, it doesn't. While it does leave the sender's machine, the BCC field will
never be exposed when the sending mail server submits the message to the
delivery mailbox or server. The receiving mail server knows who it's for
since the address of the final recipient would still be in the envelope
information for that specific message. Other BCC addresses are not
submitted.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

http://www.msoutlook.info/
Real World Questions, Real World Answers

-----

"K.P. Cijsouw" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
> If the BCC field never leaves the senders machine, then how is it possible
> that the receiving mailserver knows to which mailbox/user the mail has to
> be delivered?! I'm 100% positive that this tool exists (at least for
> Outlook 2000).
>
>

I am aware of event sinks for SMTP servers that can identify the recipient's
address (useful for catchall mailboxes) but none that works on mail after
its dropped in the mailbox. The event sink will only show the address at
the incoming SMTP, not every BCC the message was sent to.

There was a bug in an early build of outlook that exposed the BCC field but
this happened on the senders end.

--
Diane Poremsky [MVP - Outlook]
Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com/

Outlook Tips by email:
mailto:dailytips-subscribe-(E-Mail Removed)

EMO - a weekly newsletter about Outlook and Exchange:
mailto:EMO-NEWSLETTER-SUBSCRIBE-(E-Mail Removed)

Poll: What version of Outlook do you use?
http://forums.slipstick.com/showthread.php?t=27072





"K.P. CijsouwCijsouwk.nl>" <Kris@<> wrote in message
news:(E-Mail Removed)...
> A couple of years ago i had a tool (vbs script) in outlook 2000 that
> revealed the bcc field on received items. That way it was possible to see
> (as a receiver) to who the mail also was send to. Anyone familiar with
> this tool because I lost it L
>
>

K.P. Cijsouw wrote:

> If the BCC field never leaves the senders machine, then how is it possible
> that the receiving mailserver knows to which mailbox/user the mail has to be
> delivered?! I'm 100% positive that this tool exists (at least for Outlook
> 2000).

The *fields* shown in the UI for your e-mail client have nothing to do
with e-mail delivery. They are there for YOUR convenience. When you
have your e-mail client send a message, it compiles an aggregate list of
all recipients specified in the To, Cc, and Bcc *fields* displayed in
its UI. Using this list of recipients, your e-mail client then issues a
RCPT-TO command to the mail server for each recipient. Once that is
done, your e-mail client issues one (just one) DATA command that
contains your message (headers, blank delimiter line, and body). The
mail server hasn't a clue which recipient was specified in which field
and it doesn't care. It has been told who are the recipients by the
list of RCPT-TO commands that it received. The recipients never get to
see the original list of RCPT-TO commands that the sender issued to
their sending mail server.

The headers in the message (what gets sent during the DATA command) is
whatever the e-mail client puts there. E-mail clients are NOT supposed
to included the Bcc field in their header section in the message but
some did (back when dinosaurs roamed the Earth). The e-mail client
should only insert To and Cc headers that match on the values specified
in the To and Cc fields in the e-mail client's UI. Since the Bcc field
was never copied to a Bcc header in the message, there is nothing within
the message's headers to indicate who were the Bcc'ed recipients. And
since recipients never get to see the list of RCPT-TO commands issued by
the sender to their mail server, there is no way for the recipient to
know who got Bcc'ed.

Even for old e-mail clients that used to include the Bcc header in the
message based on the value of the Bcc field in their UI (as, say, an
option to do so), many receiving mail hosts will strip out that header.
It wasn't supposed to get transmitted so it gets stripped out if
present. The whole point of the Bcc field is NOT to create a header
with that list of recipients. It is, after all, a BLIND carbon copy.

If the sender's e-mail client was misconfigured to include a Bcc header,
and if the recipient's mail host doesn't strip it out, then no
additional software is required to see that header. Just view the
headers in your e-mail client to see them. If the Bcc header is there
then you can see its list of recipients.

First of all I want to thank you for your explanation!
Second I'm starting to doubt myself about the mentioned UI (Outlook 2000).
In that time, "back when dinosaurs roamed the Earth" J) we were probably
using one of the first MS-Mail clients. Problem is that I'm pretty
convenient I had a similar tool like I mentioned. Perhaps a bug like
"VanguardLH" said in her reaction?
All with all I'm convinced that at this moment viewing all BCC recipients is
impossible.
KP

And thanks again for your time!