Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update django-anymail to 0.11.1 #279

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

pyup-bot
Copy link
Collaborator

There's a new version of django-anymail available.
You are currently using 0.4.2. I have updated it to 0.11.1

These links might come in handy: PyPI | Changelog | Repo

Changelog

0.11.1

  • Mailjet: Correct settings docs.

0.11

New features

  • New ESP: Mailjet. Thanks to Lekensteyn and calvin. (Docs)

Other changes

  • 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

New 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.)

Other changes

  • 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

Breaking changes

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

Other changes

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

0.8

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.

The SendGrid v2 EmailBackend remains available if you prefer it, but is no longer the default.

Other changes

  • 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.)
  • Test on Django 1.11 prerelease, including under Python 3.6.

0.7

New 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.)
  • 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.)

Other changes

  • [possibly-breaking] 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. See 44.) In general, it's safest to always use double-quotes around all display names.
  • Mandrill: Simplify and document two-phase process for setting up Mandrill webhooks. (docs)

0.6.1

Bug fixes

  • Mailgun and 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

New features

  • Postmark: Add support for track_clicks (docs)

Other changes

  • Initialize AnymailMessage.anymail_status to empty status, rather than None; clarify docs around anymail_status availability (docs)
  • [possibly-breaking] 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 -- also see 32.)

0.5

New features

  • Mailgun: Add MAILGUN_SENDER_DOMAIN setting
    docs

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖

@codecov-io
Copy link

codecov-io commented Jul 24, 2017

Codecov Report

Merging #279 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #279   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           5      5           
  Lines          64     64           
=====================================
  Hits           64     64

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 104a0ef...84dc1bc. Read the comment docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants