Django-anymail

Latest version: v10.3

Safety actively analyzes 629564 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 8 of 10

0.7

Not secure
----

*2016-12-30*

Breaking changes
~~~~~~~~~~~~~~~~

* Fix a long-standing bug validating email addresses. If an address has a display name
containing a comma or parentheses, RFC-5322 *requires* double-quotes around the
display name (`'"Widgets, Inc." <widgetsexample.com>'`). Anymail now raises a new
`AnymailInvalidAddress` error for misquoted display names and other malformed
addresses. (Previously, it silently truncated the address, leading to obscure
exceptions or unexpected behavior. If you were unintentionally relying on that buggy
behavior, this may be a breaking change. See `44`_.) In general, it's safest to
always use double-quotes around all display names.

Features
~~~~~~~~

* **Postmark:** Support Postmark's new message delivery event in Anymail normalized
tracking webhook. (Update your Postmark config to enable the new event. See
`docs <https://anymail.dev/en/stable/esps/postmark/#status-tracking-webhooks>`__.)
* Handle virtually all uses of Django lazy translation strings as EmailMessage
properties. (In earlier releases, these could sometimes lead to obscure exceptions
or unexpected behavior with some ESPs. See `34`_.)
* **Mandrill:** Simplify and document two-phase process for setting up
Mandrill webhooks
(`docs <https://anymail.dev/en/stable/esps/mandrill/#status-tracking-webhooks>`__).

0.6.1

Not secure
------

*2016-11-01*

Fixes
~~~~~

* **Mailgun, Mandrill:** Support older Python 2.7.x versions in webhook validation
(`39`_; thanks `sebbacon`_).
* **Postmark:** Handle older-style 'Reply-To' in EmailMessage `headers` (`41`_).

0.6

Not secure
----

*2016-10-25*

Breaking changes
~~~~~~~~~~~~~~~~

* **SendGrid:** Fix missing html or text template body when using `template_id` with
an empty Django EmailMessage body. In the (extremely-unlikely) case you were relying
on the earlier quirky behavior to *not* send your saved html or text template, you
may want to verify that your SendGrid templates have matching html and text.
(`docs <https://anymail.dev/en/stable/esps/sendgrid/#batch-sending-merge-and-esp-templates>`__
-- also see `32`_.)

Features
~~~~~~~~

* **Postmark:** Add support for `track_clicks`
(`docs <https://anymail.dev/en/stable/esps/postmark/#limitations-and-quirks>`__)
* Initialize AnymailMessage.anymail_status to empty status, rather than None;
clarify docs around `anymail_status` availability
(`docs <https://anymail.dev/en/stable/sending/anymail_additions/#esp-send-status>`__)

0.5

Not secure
----

*2016-08-22*

Features
~~~~~~~~

* **Mailgun:** Add MAILGUN_SENDER_DOMAIN setting.
(`docs <https://anymail.dev/en/stable/esps/mailgun/#mailgun-sender-domain>`__)

0.4.2

Not secure
------

*2016-06-24*

Fixes
~~~~~

* **SparkPost:** Fix API error "Both content object and template_id are specified"
when using `template_id` (`24`_).

0.4.1

Not secure
------

*2016-06-23*

Features
~~~~~~~~

* **SparkPost:** Add support for this ESP.
(`docs <https://anymail.dev/en/stable/esps/sparkpost/>`__)
* Test with Django 1.10 beta
* Requests-based backends (all but SparkPost) now raise AnymailRequestsAPIError
for any requests.RequestException, for consistency and proper fail_silently behavior.
(The exception will also be a subclass of the original RequestException, so no
changes are required to existing code looking for specific requests failures.)

Page 8 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.