#37152: EmailMessage should block `bcc` in `extra_headers` and docs should not
suggest `bcc` is a header
-------------------------------------+-------------------------------------
Reporter: Natalia Bidart | Owner: diaxoaine
Type: | Status: closed
Cleanup/optimization |
Component: Core (Mail) | Version: 6.0
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia <124304+nessita@…>):
In [changeset:"dd4e1a4006cb0713713a97f1252da930abff07fd" dd4e1a4]:
{{{#!CommitTicketReference repository=""
revision="dd4e1a4006cb0713713a97f1252da930abff07fd"
[6.1.x] Fixed #37152 -- Raised ValueError when Bcc is used in EmailMessage
headers.
Bcc addresses are sent via the SMTP envelope and must never appear in
the message itself. A "Bcc" key in `extra_headers` was not excluded like
From/To/Cc/Reply-To, so it leaked into the generated message as a
visible header.
Thanks Mike Edmunds for reviews.
Backport of 09434486302078c3649e034dfa74cf3f102db20b from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/37152#comment:13>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019ed2a77bf5-789c565a-309e-43d9-bb02-cf72300583a0-000000%40eu-central-1.amazonses.com.
