>>> C.3.4.  DESTINATION
>>> 
>>> A message must contain at least one destination address field (i.e. "To",
>>> "CC", "Bcc"). "To" and "CC" are required to contain at least one address,
>>> whereas "Bcc" may contain zero or more addresses.
> 
> 
> This makes it sound as if the "CC" field is REQUIRED to have an address in
> it.  Is that right?

If the CC field exists in the header, it must have at least one address.

However, there doesn't have to be a CC field.

> Or is it that between the "To" and "CC" fields there must be at least one
> address?

Nope, not quite.

If the To field exists in the header, it must have at least one address.

If the CC field exists in the header, it must have at least one address.

If the Bcc field exists in the header, its recipient list can be blank.


There must be at least one of the To, CC, and Bcc fields; however, there can
be more than just one.


> BCC always has confused me.  Is there an easy way to remember who can see
> what for BCC recipients?

Nope.  It's implementation specific.

The vast majority of the time, the BCC field isn't added to the visible
message.  But some clients and some servers may add it.

And life is further complicated here by the difference between reality and
the specifications.

Still, odds are that if you BCC someone, no one else will know.


However, some government and military servers are configured to add an
explicit Bcc listing to all such messages.  And a few corporate servers are
configured similarly.  While I've never heard of an ISP server being so
configured, it could happen.


But, generally speaking, so long as there is at least one explicit recipient
listed in either the To or Cc field, the Bcc recipient list won't appear.
In the absence of such, some misguided servers will add "Apparently-To"
headers to the message explicitly listing every recipient (including Bcc'd
recipients).

Personally, I've never understand the amount of hysteria that seems to
surround this topic.  But then I hardly ever use Bcc and I'm known for my
bad attitude.

mikel


-- 
To unsubscribe:               <mailto:[EMAIL PROTECTED]>
To search the archives: 
          <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>

Reply via email to