Anymail releases follow semantic versioning. Among other things, this means that minor updates (1.x to 1.y) should always be backwards-compatible, and breaking changes will always increment the major version number (1.x to 2.0).
- Postmark: Fix API error when sending with template to single recipient. (Thanks to @jc-ee for finding and fixing the issue.)
- SendGrid: Allow non-batch template send to multiple recipients when
merge_global_datais set without
merge_data. (Broken in v6.0. Thanks to @vgrebenschikov for the bug report.)
DEBUG_API_REQUESTSsetting to dump raw ESP API requests, which can assist in debugging or reporting problems to ESPs. (See docs. This setting has was quietly added in Anymail v4.3, and is now officially documented.)
- Sendinblue: Now supports file attachments on template sends, when using their new template language. (Sendinblue removed this API limitation on 2020-02-18; the change works with Anymail v7.0 and later. Thanks to @sebashwa for noting the API change and updating Anymail’s docs.)
- Test against released Django 3.0.
- SendGrid: Document unpredictable behavior in the SendGrid API that can cause text attachments to be sent with the wrong character set. (See docs under “Wrong character set on text attachments.” Thanks to @nuschk and @swrobel for helping track down the issue and reporting it to SendGrid.)
- Docs: Fix a number of typos and some outdated information. (Thanks @alee and @Honza-m.)
Sendinblue templates: Support Sendinblue’s new (ESP stored) Django templates and new API for template sending. This removes most of the odd limitations in the older (now-deprecated) SendinBlue template send API, but involves two breaking changes:
- You must convert
each old Sendinblue template to the new language as you upgrade to Anymail v7.0, or
certain features may be silently ignored on template sends (notably
reply_toand recipient display names).
- Sendinblue’s API no longer supports sending attachments when using templates. [Note: Sendinblue removed this API limitation on 2020-02-18.]
- You must convert each old Sendinblue template to the new language as you upgrade to Anymail v7.0, or certain features may be silently ignored on template sends (notably
- Mailgun: Disable Anymail’s workaround for a Requests/urllib3 issue with non-ASCII attachment filenames when a newer version of urllib3–which fixes the problem–is installed. (Workaround was added in Anymail v4.3; fix appears in urllib3 v1.25.)
- Mailgun: Add new
MAILGUN_WEBHOOK_SIGNING_KEYsetting for verifying tracking and inbound webhook calls. Mailgun’s webhook signing key can become different from your
MAILGUN_API_KEYif you have ever rotated either key. See docs. (More in #153. Thanks to @dominik-lekse for reporting the problem and Mailgun’s @mbk-ok for identifying the cause.)
message.anymail_status.recipients[email]no longer lowercases the recipient’s email address. For consistency with other ESPs, it now uses the recipient email with whatever case was used in the sent message. If your code is doing something like
message.anymail_status.recipients[email.lower()], you should remove the
SendGrid: In batch sends, Anymail’s SendGrid backend now assigns a separate
message_idfor each “to” recipient, rather than sharing a single id for all recipients. This improves accuracy of tracking and statistics (and matches the behavior of many other ESPs).
If your code uses batch sending (merge_data with multiple to-addresses) and checks
message.anymail_status.message_idafter sending, that value will now be a set of ids. You can obtain each recipient’s individual message_id with
message.anymail_status.recipients[to_email].message_id. See docs.
- Mailgun: Better error message for invalid sender domains (that caused a cryptic “Mailgun API response 200: OK Mailgun Magnificent API” error in earlier releases).
- Postmark: Don’t error if a message is sent with only Cc and/or Bcc recipients
(but no To addresses). Also,
message.anymail_status.recipients[email]now includes send status for Cc and Bcc recipients. (Thanks to @ailionx for reporting the error.)
- SendGrid: With legacy templates, stop (ab)using “sections” for merge_global_data. This avoids potential conflicts with a template’s own use of SendGrid section tags.
- Mailgun: Anymail’s status tracking webhooks now report Mailgun “temporary failure”
events as Anymail’s normalized “deferred”
event_type. (Previously they were reported as “bounced”, lumping them in with permanent failures.) The new behavior is consistent with how Anymail handles other ESP’s tracking notifications. In the unlikely case your code depended on “temporary failure” showing up as “bounced” you will need to update it. (Thanks @costela.)
- Postmark: Allow either template alias (string) or numeric template id for
template_idwhen sending with Postmark templates.
- Mailgun: Improve error reporting when an inbound route is accidentally pointed at Anymail’s tracking webhook url or vice versa.
- Treat MIME attachments that have a Content-ID but no explicit Content-Disposition header as inline, matching the behavior of many email clients. For maximum compatibility, you should always set both (or use Anymail’s inline helper functions). (Thanks @costela.)
- Mailgun: Raise
AnymailUnsupportedFeatureerror when attempting to send an attachment without a filename (or inline attachment without a Content-ID), because Mailgun silently drops these attachments from the sent message. (See docs. Thanks @costela for identifying this undocumented Mailgun API limitation.)
- Mailgun: Fix problem where attachments with non-ASCII filenames would be lost. (Works around Requests/urllib3 issue encoding multipart/form-data filenames in a way that isn’t RFC 7578 compliant. Thanks to @decibyte for catching the problem.)
- Add (undocumented) DEBUG_API_REQUESTS Anymail setting. When enabled, prints raw API request and response during send. Currently implemented only for Requests-based backends (all but Amazon SES and SparkPost). Because this can expose API keys and other sensitive info in log files, it should not be used in production.
- Postmark: Support per-recipient template
merge_dataand batch sending. (Batch sending can be used with or without a template. See docs.)
- Postmark: When using
template_id, ignore empty subject and body. (Postmark issues an error if Django’s default empty strings are used with template sends.)
- Drop support for Django versions older than Django 1.11. (For compatibility back to Django 1.8, stay on the Anymail v3.0 extended support branch.)
- SendGrid: Remove the legacy SendGrid v2 EmailBackend.
(Anymail’s default since v0.8 has been SendGrid’s newer v3 API.)
If your settings.py
EMAIL_BACKENDstill references “sendgrid_v2,” you must upgrade to v3.
- Mailgun: Add support for new Mailgun webhooks. (Mailgun’s original “legacy webhook” format is also still supported. See docs.)
- Mailgun: Document how to use new European region. (This works in earlier Anymail versions, too.)
- Postmark: Add support for Anymail’s normalized
metadatain sending and webhooks.
- Avoid problems with Gmail blocking messages that have inline attachments, when sent
from a machine whose local hostname ends in .com. Change Anymail’s
attach_inline_image()default Content-ID domain to the literal text “inline” (rather than Python’s default of the local hostname), to work around a limitation of some ESP APIs that don’t permit distinct content ID and attachment filenames (Mailgun, Mailjet, Mandrill and SparkPost). See #112 for more details.
- Amazon SES: Work around an Amazon SES bug that can corrupt non-ASCII message bodies if you are using SES’s open or click tracking. (See #115 for more details. Thanks to @varche1 for isolating the specific conditions that trigger the bug.)
- Maintain changelog in the repository itself (rather than in GitHub release notes).
- Test against released versions of Python 3.7 and Django 2.1.
This is an extended support release. Anymail v3.x will receive security updates and fixes for any breaking ESP API changes through at least April, 2019.
- Drop support for Python 3.3 (see #99).
- SendGrid: Fix a problem where Anymail’s status tracking webhooks didn’t always
receive the same
event.message_idas the sent
message.anymail_status.message_id, due to unpredictable behavior by SendGrid’s API. Anymail now generates a UUID for each sent message and attaches it as a SendGrid custom arg named anymail_id. For most users, this change should be transparent. But it could be a breaking change if you are relying on a specific message_id format, or relying on message_id matching the Message-ID mail header or SendGrid’s “smtp-id” event field. (More details in the docs; also see #108.) Thanks to @joshkersey for the report and the fix.
- Support Django 2.1 prerelease.
- Mailjet: Fix tracking webhooks to work correctly when Mailjet “group events” option is disabled (see #106).
- This will be the last Anymail release to support Django 1.8, 1.9, and 1.10 (see #110).
- This will be the last Anymail release to support the legacy SendGrid v2 EmailBackend (see #111). (SendGrid’s newer v3 API has been the default since Anymail v0.8.)
If these deprecations affect you and you cannot upgrade, set your requirements to
django-anymail~=3.0 (a “compatible release” specifier, equivalent to
- Fix a breaking change accidentally introduced in v2.1: The boto3 package is no longer required if you aren’t using Amazon SES.
NOTE: v2.1 accidentally introduced a breaking change: enabling Anymail webhooks
include('anymail.urls') causes an error if boto3 is not installed, even if you
aren’t using Amazon SES. This is fixed in v2.2.
- Amazon SES: Add support for this ESP (docs).
- SparkPost: Add SPARKPOST_API_URL setting to support SparkPost EU and SparkPost Enterprise (docs).
- Postmark: Update for Postmark “modular webhooks.” This should not impact client code. (Also, older versions of Anymail will still work correctly with Postmark’s webhook changes.)
- Inbound: Fix several issues with inbound messages, particularly around non-ASCII headers and body content. Add workarounds for some limitations in older Python email packages.
- Drop support for deprecated WEBHOOK_AUTHORIZATION setting. If you are using webhooks and still have this Anymail setting, you must rename it to WEBHOOK_SECRET. See the v1.4 release notes.
- Handle Reply-To, From, and To in EmailMessage
extra_headersthe same as Django’s SMTP EmailBackend if supported by your ESP, otherwise raise an unsupported feature error. Fixes the SparkPost backend to be consistent with other backends if both
reply_toare set on the same message. If you are setting a message’s
headers["To"](neither is common), the new behavior is likely a breaking change. See docs and #91.
- Treat EmailMessage
extra_headerskeys as case-insensitive in all backends, for consistency with each other (and email specs). If you are specifying duplicate headers whose names differ only in case, this may be a breaking change. See docs.
- Update setup.py metadata, clean up implementation. (Hadn’t really been touched since original Djrill version.)
- Prep for Python 3.7.
- Fix a low severity security issue affecting Anymail v0.2–v1.3: rename setting WEBHOOK_AUTHORIZATION to WEBHOOK_SECRET to prevent inclusion in Django error reporting. (CVE-2018-1000089)
Django error reporting includes the value of your Anymail WEBHOOK_AUTHORIZATION setting. In a properly-configured deployment, this should not be cause for concern. But if you have somehow exposed your Django error reports (e.g., by mis-deploying with DEBUG=True or by sending error reports through insecure channels), anyone who gains access to those reports could discover your webhook shared secret. An attacker could use this to post fabricated or malicious Anymail tracking/inbound events to your app, if you are using those Anymail features.
The fix renames Anymail’s webhook shared secret setting so that Django’s error reporting mechanism will sanitize it.
If you are using Anymail’s event tracking and/or inbound webhooks, you should upgrade to this release and change “WEBHOOK_AUTHORIZATION” to “WEBHOOK_SECRET” in the ANYMAIL section of your settings.py. You may also want to rotate the shared secret value, particularly if you have ever exposed your Django error reports to untrusted individuals.
If you are only using Anymail’s EmailBackends for sending email and have not set up Anymail’s webhooks, this issue does not affect you.
The old WEBHOOK_AUTHORIZATION setting is still allowed in this release, but will issue a system-check warning when running most Django management commands. It will be removed completely in a near-future release, as a breaking change.
Thanks to Charlie DeTar (@yourcelf) for responsibly reporting this security issue through private channels.
- v1.3 includes the v1.2.1 security fix released at the same time. Please review the v1.2.1 release notes, below, if you are using Anymail’s tracking webhooks.
- Inbound handling: Add normalized inbound message event, signal, and webhooks for all supported ESPs. (See new Receiving mail docs.) This hasn’t been through much real-world testing yet; bug reports and feedback are very welcome.
- API network timeouts: For Requests-based backends (all but SparkPost), use a default timeout of 30 seconds for all ESP API calls, to avoid stalling forever on a bad connection. Add a REQUESTS_TIMEOUT Anymail setting to override. (See #80.)
- Test backend improvements: Generate unique tracking
message_idwhen using the test backend; add console backend for use in development. (See #85.)
- Fix a moderate severity security issue affecting Anymail v0.2–v1.2: prevent timing attack on WEBHOOK_AUTHORIZATION secret. (CVE-2018-6596)
If you are using Anymail’s tracking webhooks, you should upgrade to this release, and you may want to rotate to a new WEBHOOK_AUTHORIZATION shared secret (see docs). You should definitely change your webhook auth if your logs indicate attempted exploit.
(If you are only sending email using an Anymail EmailBackend, and have not set up Anymail’s event tracking webhooks, this issue does not affect you.)
Anymail’s webhook validation was vulnerable to a timing attack. A remote attacker could use this to obtain your WEBHOOK_AUTHORIZATION shared secret, potentially allowing them to post fabricated or malicious email tracking events to your app.
There have not been any reports of attempted exploit. (The vulnerability was discovered through code review.) Attempts would be visible in HTTP logs as a very large number of 400 responses on Anymail’s webhook urls (by default “/anymail/esp_name/tracking/”), and in Python error monitoring as a very large number of AnymailWebhookValidationFailure exceptions.
- Rework Anymail’s ParsedEmail class and rename to EmailAddress to align it with similar functionality in the Python 3.6 email package, in preparation for future inbound support. ParsedEmail was not documented for use outside Anymail’s internals (so this change does not bump the semver major version), but if you were using it in an undocumented way you will need to update your code.
It’s official: Anymail is no longer “pre-1.0.” The API has been stable for many months, and there’s no reason not to use Anymail in production.
- There are no new breaking changes in the 1.0 release, but a breaking change introduced several months ago in v0.8 is now strictly enforced. If you still have an EMAIL_BACKEND setting that looks like “anymail.backends.*espname*.EspNameBackend”, you’ll need to change it to just “anymail.backends.*espname*.EmailBackend”. (Earlier versions had issued a DeprecationWarning. See the v0.8 release notes.)
- All backends: The old EspNameBackend 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.
- Mailgun, SparkPost: Support multiple from addresses, as a comma-separated
from_emailstring. (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.)
- 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.
- Mandrill, Postmark: Normalize soft-bounce webhook events to event_type ‘bounced’ (rather than ‘deferred’).
- Officially support released Django 1.11, including under Python 3.6.
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" # oldto:
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_extrawith “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.
- Test on Django 1.11 prerelease, including under Python 3.6.
- 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." <email@example.com>'). Anymail now raises a new
AnymailInvalidAddresserror 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.
- 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.)
- Mandrill: Simplify and document two-phase process for setting up Mandrill webhooks (docs).
- SendGrid: Fix missing html or text template body when using
template_idwith 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.)
- SparkPost: Add support for this ESP. (docs)
- 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.)
- Add support for ESP stored templates and batch sending/merge. Exact capabilities vary widely by ESP – be sure to read the notes for your ESP. (docs)
- Add pre_send and post_send signals. docs
- Mandrill: add support for esp_extra; deprecate Mandrill-specific message attributes left over from Djrill. See migrating from Djrill.
- Mailgun: eliminate automatic JSON encoding of complex metadata values like lists and dicts. (Was based on misreading of Mailgun docs; behavior now matches metadata handling for all other ESPs.)
- Mandrill: remove obsolete wehook views and signal inherited from Djrill. See Djrill migration notes if you were relying on that code.
- Add support for ESP event-tracking webhooks, including normalized AnymailTrackingEvent. (docs)
- Allow get_connection kwargs overrides of most settings for individual backend instances. Can be useful for, e.g., working with multiple SendGrid subusers. (docs)
- SendGrid: Add SENDGRID_GENERATE_MESSAGE_ID setting to control workarounds for ensuring unique tracking ID on SendGrid messages/events (default enabled). docs
- SendGrid: improve handling of ‘filters’ in esp_extra, making it easier to mix custom SendGrid app filter settings with Anymail normalized message options.
- Drop pre-Django 1.8 test code. (Wasn’t being used, as Anymail requires Django 1.8+.)
- Mandrill: note limited support in docs (because integration tests no longer available).
Although this is an early release, it provides functional Django EmailBackends and passes integration tests with all supported ESPs (Mailgun, Mandrill, Postmark, SendGrid).
It has (obviously) not yet undergone extensive real-world testing, and you are encouraged to monitor it carefully if you choose to use it in production. Please report bugs and problems here in GitHub.
- Postmark: Add support for this ESP.
- SendGrid: Add support for username/password auth.
- Simplified install: no need to name the ESP (
pip install django-anymail– not
- SendGrid: Add support for this ESP.
- Add attach_inline_image_file helper
- Change inline-attachment handling to look for
Content-Disposition: inline, and to preserve filenames where supported by the ESP.