[Django] #23910: Multiple Email for Reply-To

[Django]

#23910: Multiple Email for Reply-To
-----------------------------+----------------------------
Reporter: zkanda | Owner: nobody
Type: New feature | Status: new
Component: Core (Mail) | Version: master
Severity: Normal | Keywords: email, headers
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
-----------------------------+----------------------------
It would be cool if I can just pass a list to Reply-To.

Right now I have something like this:
{{{
msg = EmailMultiAlternatives(
email_subject, body, email_from, [user.email],
headers={'Reply-To': ",".join([email.email for email in
organization.get_emails()])})
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/23910>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#23910: Add reply_to parameter to EmailMessage
--------------------------------+------------------------------------

Reporter: zkanda | Owner: nobody
Type: New feature | Status: new
Component: Core (Mail) | Version: master

Severity: Normal | Resolution:
Keywords: email, headers | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 1 | UI/UX: 0

--------------------------------+------------------------------------
Changes (by timgraham):

* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted

Comment:

I guess we could add `reply_to` as a parameter to `EmailMessage` and
`EmailMultiAlternatives` like we have for the other email fields.

--
Ticket URL: <https://code.djangoproject.com/ticket/23910#comment:1>

[Django]

#23910: Add reply_to parameter to EmailMessage
--------------------------------+------------------------------------

Reporter: zkanda | Owner: nobody
Type: New feature | Status: new
Component: Core (Mail) | Version: master

Severity: Normal | Resolution:
Keywords: email, headers | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 1 | UI/UX: 0

--------------------------------+------------------------------------

Comment (by martinblech):

Here's [https://github.com/django/django/pull/3624 PR #3624]

--
Ticket URL: <https://code.djangoproject.com/ticket/23910#comment:2>

[Django]

#23910: Add reply_to parameter to EmailMessage

-------------------------------------+-------------------------------------

Reporter: zkanda | Owner: nobody
Type: New feature | Status: new
Component: Core (Mail) | Version: master

Severity: Normal | Resolution:
Keywords: email, headers | Triage Stage: Ready for
Has patch: 1 | checkin
Needs tests: 0 | Needs documentation: 0
Easy pickings: 1 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by berkerpeksag):

* has_patch: 0 => 1
* stage: Accepted => Ready for checkin

Comment:

[https://github.com/django/django/pull/3624 PR #3624] LGTM.

--
Ticket URL: <https://code.djangoproject.com/ticket/23910#comment:3>

[Django]

#23910: Add reply_to parameter to EmailMessage
-------------------------------------+-------------------------------------

Reporter: zkanda | Owner: nobody
Type: New feature | Status: closed

Component: Core (Mail) | Version: master

Severity: Normal | Resolution: fixed

Keywords: email, headers | Triage Stage: Ready for
Has patch: 1 | checkin
Needs tests: 0 | Needs documentation: 0
Easy pickings: 1 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Tim Graham <timograham@…>):

* status: new => closed
* resolution: => fixed

Comment:

In [changeset:"e023ceb453c02e271d00f9ac25e154b7be712bb0"]:
{{{
#!CommitTicketReference repository=""
revision="e023ceb453c02e271d00f9ac25e154b7be712bb0"
Fixed #23910 -- Added reply_to parameter to EmailMessage

Thanks to Berker Peksag and Tim Graham for the review and suggestions.
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/23910#comment:4>