Support Django 1.8 reply_to param.

This commit is contained in:
medmunds
2015-02-25 16:30:02 -08:00
parent 8ab36d2cd0
commit bbc2e06091
4 changed files with 45 additions and 2 deletions

View File

@@ -4,6 +4,10 @@ Release Notes
Version 1.4 (development):
* Django 1.8 alpha support
* Support new Django 1.8 EmailMessage reply_to param.
(Specifying a :ref:`Reply-To header <message-headers>`
still works, with any version of Django,
and will override the reply_to param if you use both.)
Version 1.3:

View File

@@ -76,13 +76,27 @@ Some notes and limitations:
.. versionchanged:: 0.4
Special handling for embedded images
.. _message-headers:
**Headers**
Djrill accepts additional headers and passes them along to Mandrill.
Djrill accepts additional headers and passes them along to Mandrill:
.. code-block:: python
msg = EmailMessage( ...
headers={'Reply-To': "reply@example.com", 'List-Unsubscribe': "..."}
)
.. versionchanged:: 0.9
In earlier versions, Djrill only allowed ``Reply-To`` and ``X-*`` headers,
matching previous Mandrill API restrictions.
.. versionchanged:: 1.4
Djrill also supports the `reply_to` param added to
:class:`~django.core.mail.EmailMessage` in Django 1.8.
(If you provide *both* a 'Reply-To' header and the `reply_to` param,
the header will take precedence.)
.. _mandrill-send-support: