#28598: BCC addresses are ignored in the console and file email backends
-------------------------------------+-------------------------------------
Reporter: zngr | Owner: Josh
Type: | Schneier
Cleanup/optimization | Status: assigned
Component: Core (Mail) | Version: 1.11
Severity: Normal | Resolution:
Keywords: mail, bcc | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Josh Schneier):
I have a cursory implementation of your solution which is simple enough.
My hesitation is that this and the other opened issue seems more like
users wanting to ensure that their code is doing precisely what they are
telling it to do and then not realizing that BCC is not included in the
actual MIME text which is what we are printing
([https://github.com/mattupstate/flask-mail/pull/119 I speak from
experience]). Or that they want to be able to access it and expect to see
''everything'' since these backends are explicitly for development.
How about we add the hook and document BCC explicitly or that the default
implementations return the MIME text?
The no-BCC-in-MIME is very much part of the black box that is the email
spec which we shouldn't be reproducing in the docs but it is confusing
when encountered in this context.
--
Ticket URL: <https://code.djangoproject.com/ticket/28598#comment:10>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.8d5822a1a6b7e85c39abac910d765119%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
