Django-anymail

Latest version: v10.3

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

Scan your dependencies

Page 7 of 10

1.0.rc0

--------

*2017-09-09*

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

* **All backends:** The old *EspName*\ Backend names that were deprecated in v0.8 have
been removed. Attempting to use the old names will now fail, rather than issue a
DeprecationWarning. See the `v0.8`_ release notes.

Features
~~~~~~~~

* Anymail's Test EmailBackend is now
`documented <https://anymail.dev/en/stable/tips/test_backend/>`__
(and cleaned up)

0.11.1

Not secure
-------

*2017-07-24*

Fixes
~~~~~

* **Mailjet:** Correct settings docs.

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

Page 7 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.