#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 Carlton Gibson):
> I wonder if adding .format_message() isn't a case of YAGNI or over
engineering.
Well, I guess most people won't need it, but that this ticket exists
suggest some will. Adding a hook to allow subclassing at least allows
those people to address their issue.
(Just saying in the docs that "BCCs won't be included" isn't great IMO: it
offers me no way forward.)
> ... it will double up ...
I wouldn't worry about this. If people want to do some set operations in
their subclass to get **just** the BCCs then they're welcome to.
All we're doing is providing the hook.
> Currently write_message also includes '*' * 79...
I'd leave that where it is. If someone wants to override `write_message()`
as well then they're welcome.
--
Ticket URL: <https://code.djangoproject.com/ticket/28598#comment:6>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.572a1a7079050945b31fd4e6fc7857a9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
