Re: tcllib mime smtp proc sends BCC mail copies as attachments

On Jan 11, 3:13 pm, Darren New <d...@xxxxxxxxxx> wrote:
dhogaza wrote:
On Jan 11, 6:56 pm, Darren New <d...@xxxxxxxxxx> wrote:
dhogaza wrote:
rather than directly as it does to TO and CC addresses.
Does anyone here know why?
It keeps someone who does a reply-all to the bcc'ed mail from
embarrassing themselves? It's not that it's an attachment - it's that
it's not sent with the same to/cc headers.

Well, is it wrong for a reply-all to reply to the to/cc list?

No, it's correct. It can just be embarrassing because it reveals the
fact that you were bcc'ed. Plus, if you're using it to send messages to
customers and bcc'ing a monitoring address (e.g., customer service
repository), then you wind up accidentally sending something to a
customer if you reply to it.

In other words, sending it separately w/o the to/cc headers in no way
implies you have to transform the message to an attachment!

True. But then the recipient doesn't know who it was sent to. I.e., the
bcc recipient loses the headers.

This is such an easy concept. You are sending 'one' message to one
list of users. CC means 'carbon copy', BCC means 'blind carbon copy'.
What part of 'carbon copy' is so hard to understand? This is why I put
the example down: what you are sending is 'one message' which includes
certain headers and maybe a body to a group of 'recipients'. You don't
need to list all recipients, and in general, for instance, a mailing
list, or a group of your friends who don't know each other, or
students in your class, etc., it is really a bad idea to include
anyone's email address in the headers (To or CC).

If your software interprets the BCC as a separate group of users who
need a different email, with different headers, this is not correct.
You are not specifying different classes of recipients with BCC, just
additional recipients. If the user wants to handle the case without
BCC, they can CC themselves on the first email and then forward a copy
to an additional list of CC'd recipients.

You can also handle the embarrassment by adding a Reply-To header. For
instance, a mailing list could use this so that you can show who sent
the email (From: me), but still indicate replies should go to the list
address. Also, with a mailing list, you might want the To: header to
be the list address so you can filter on it.

Of course, if you use BCC for sending copies to shipping, or legal, or
whoever, they will very likely want to know who the email was sent to,
removing this information would be not good, including their internal
email address to outside users would also not be good.
.

Relevant Pages

  • Re: Preventing the use of CC: in outlook express.
    ... You will have an icon on your Desktop now with, depending on how you set it up, that when clicked on will open a new message window with the To and BCC fields already filled in. ... recipients don't want their email address made available to others. ... Potentially, something could be done at your SMTP mail server, assuming ... addresses or even strip or truncate the headers. ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Preventing the use of CC: in outlook express.
    ... Forgot to add the Group and BCC instructions. ... To use the BCC feature, In Create Mail, either click View | All Headers and type in the addresses separated by a; ... (Some ISPs require a legitimate address in the To line, and the recipients will know it is from the group). ... Potentially, something could be done at your SMTP mail server, assuming ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Writing my own mass-email script in PHP
    ... > and put the extra Bcc: headers in the extra headers argument to the PHP ... Putting all recipients in Bcc: is not a good idea because ...
    (comp.lang.php)
  • Re: Mass emails
    ... transmitting sites in some headers that we recieved. ... >> sent repeatedly from our server but through some of the recipients in the ... > The aforementioned POP3 connector contains a bug which causes it to ... > In view of the above, senders of any particular mailing or mailshot, ...
    (microsoft.public.exchange2000.admin)
  • Re: Messages apparently delivered to wrong users mailbox
    ... One of the recipients was a BCC. ... SMTP RFCs so you'll understand more about the foundation of e-mail. ... If it was a BCC or something I would expect the headers to have the ...
    (microsoft.public.exchange.admin)