Django-anymail

Latest version: v12.0

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

Scan your dependencies

Page 8 of 10

0.11

Not secure
-----

*2017-07-13*

Features
~~~~~~~~

* **Mailjet:** Add support for this ESP. Thanks to `Lekensteyn`_ and `calvin`_.
(`Docs <https://anymail.dev/en/stable/esps/mailjet/>`__)
* In webhook handlers, AnymailTrackingEvent.metadata now defaults to `{}`, and
.tags defaults to `[]`, if the ESP does not supply these fields with the event.
(See `67`_.)

0.10

Not secure
-----

*2017-05-22*

Features
~~~~~~~~

* **Mailgun, SparkPost:** Support multiple from addresses, as a comma-separated
`from_email` string. (*Not* a list of strings, like the recipient fields.)
RFC-5322 allows multiple from email addresses, and these two ESPs support it.
Though as a practical matter, multiple from emails are either ignored or treated
as a spam signal by receiving mail handlers. (See `60`_.)

Fixes
~~~~~

* Fix crash sending forwarded email messages as attachments. (See `59`_.)
* **Mailgun:** Fix webhook crash on bounces from some receiving mail handlers.
(See `62`_.)
* Improve recipient-parsing error messages and consistency with Django's SMTP
backend. In particular, Django (and now Anymail) allows multiple, comma-separated
email addresses in a single recipient string.

0.9

Not secure
----

*2017-04-04*

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

* **Mandrill, Postmark:** Normalize soft-bounce webhook events to event_type
'bounced' (rather than 'deferred').

Features
~~~~~~~~

* Officially support released Django 1.11, including under Python 3.6.


.. _release_0_8:

0.8

Not secure
----

*2017-02-02*

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

* **All backends:** Rename all Anymail backends to just `EmailBackend`, matching
Django's naming convention. E.g., you should update:
`EMAIL_BACKEND = "anymail.backends.mailgun.MailgunBackend" old`
to: `EMAIL_BACKEND = "anymail.backends.mailgun.EmailBackend" new`

The old names still work, but will issue a DeprecationWarning and will be removed
in some future release (Apologies for this change; the old naming was a holdover
from Djrill, and I wanted to establish consistency with other Django EmailBackends
before Anymail 1.0. See `49`_.)

* **SendGrid:** Update SendGrid backend to their newer Web API v3. This should be a
transparent change for most projects. Exceptions: if you use SendGrid
username/password auth, Anymail's `esp_extra` with "x-smtpapi", or multiple Reply-To
addresses, please review the
`porting notes <https://anymail.dev/en/v3.0/esps/sendgrid/#sendgrid-v3-upgrade>`__.

The SendGrid v2 EmailBackend
`remains available <https://anymail.dev/en/v3.0/esps/sendgrid/#sendgrid-v2-backend>`__
if you prefer it, but is no longer the default.

.. SendGrid v2 backend removed after Anymail v3.0; links frozen to that doc version

Features
~~~~~~~~

* Test on Django 1.11 prerelease, including under Python 3.6.

Fixes
~~~~~

* **Mandrill:** Fix bug in webhook signature validation when using basic auth via the
WEBHOOK_AUTHORIZATION setting. (If you were using the MANDRILL_WEBHOOK_URL setting
to work around this problem, you should be able to remove it. See `48`_.)

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`_).

Page 8 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.