[Django] #34782: Explicit support for In-Reply-To / References in EmailMessage

5 views
Skip to first unread message

Django

unread,
Aug 17, 2023, 12:59:46 PM8/17/23
to django-...@googlegroups.com
#34782: Explicit support for In-Reply-To / References in EmailMessage
----------------------------------------------+------------------------
Reporter: dgilmanAIDENTIFIED | Owner: nobody
Type: New feature | Status: new
Component: Core (Mail) | Version: dev
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
----------------------------------------------+------------------------
If you want email clients to thread a response you need to set the In-
Reply-To and References headers in the email with the Message-ID of the
email you're responding to.

Right now, with the EmailMessage class, you can set both directly via the
headers= kwarg. However, maybe it is worth an explicit kwarg, like it
already has with cc, bcc and reply-to, to save the user the hassle of
looking up the relevant RFCs and figuring out what needs to be done. It is
a little bit of a weird case in that you have to set two different headers
to what is usually the same value.

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

Django

unread,
Aug 17, 2023, 1:24:23 PM8/17/23
to django-...@googlegroups.com
#34782: Explicit support for In-Reply-To / References in EmailMessage
------------------------------+--------------------------------------
Reporter: David Gilman | Owner: nobody
Type: New feature | Status: closed

Component: Core (Mail) | Version: dev
Severity: Normal | Resolution: wontfix

Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):

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


Comment:

Thanks for the ticket, however, `headers` is the right place to add `in-
reply-to`, we don't want to add extra kwargs for all available headers.
This API is generally frozen.

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

Reply all
Reply to author
Forward
0 new messages