As i don't see any reason why we should ignore the bcc field, it must be a
bug.
--
Ticket URL: <https://code.djangoproject.com/ticket/25341>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => assigned
* owner: nobody => blaze33
* needs_docs: => 0
* needs_tests: => 0
* needs_better_patch: => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/25341#comment:1>
Comment (by blaze33):
Pull request with code and tests:
https://github.com/django/django/pull/5225
--
Ticket URL: <https://code.djangoproject.com/ticket/25341#comment:2>
* status: assigned => closed
* resolution: => invalid
Comment:
Oooops, sorry, I was working with EmailMessage to generate Gmail drafts
where you need to define a Bcc header to save the bcc recipients in the
draft and that got me confused because obviously you don't want to send
such a thing as a Bcc header!
--
Ticket URL: <https://code.djangoproject.com/ticket/25341#comment:3>
* status: closed => new
* resolution: invalid =>
Comment:
Maybe I am missing something, but I don't see that this bug has been
fixed, not in the 1.x.x, 2.x.x, or 3.x.x branch. The bcc parameter of
EmailMessage is still being ignored.
--
Ticket URL: <https://code.djangoproject.com/ticket/25341#comment:4>
* status: new => closed
* has_patch: 1 => 0
* resolution: => duplicate
Comment:
Bcc addresses works completely fine (see
[https://code.djangoproject.com/ticket/18582#comment:3 comment]), please
don't reopen old tickets unless you can provide something new to the
problem. If you're talking about displaying Bcc addresses in the console
then #28598 is still open.
Duplicate of #18582.
--
Ticket URL: <https://code.djangoproject.com/ticket/25341#comment:5>
Comment (by Muesliflyer):
My bad.
--
Ticket URL: <https://code.djangoproject.com/ticket/25341#comment:6>