This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.smith
Recipients Nonickname, barry, docs@python, eric.smith, r.david.murray
Date 2017-03-09.13:53:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1489067614.93.0.225025979516.issue29771@psf.upfronthosting.co.za>
In-reply-to
Content
You need to review how SMTP works. The contents of the mail message have no bearing on where messages are sent. That's exactly how BCC works: there's nothing in the message telling you who is BCC'd, but the mail is still sent to the BCC recipients, via SMTP.

Similarly, you could have the message say that someone@example.com is in the To: header, but not send it to them via SMTP.

I'm on the fence about including this in the examples.

In any event, this bug tracker is not a place for an email tutorial. From your SO link, there's a reference (by user xyref) to another question which explains this in detail: http://stackoverflow.com/questions/1546367/python-how-to-send-mail-with-to-cc-and-bcc. This completely explains the issue.
History
Date User Action Args
2017-03-09 13:53:34eric.smithsetrecipients: + eric.smith, barry, r.david.murray, docs@python, Nonickname
2017-03-09 13:53:34eric.smithsetmessageid: <1489067614.93.0.225025979516.issue29771@psf.upfronthosting.co.za>
2017-03-09 13:53:34eric.smithlinkissue29771 messages
2017-03-09 13:53:34eric.smithcreate