Anymail lets you send and receive email in Django using your choice of transactional email service providers (ESPs). It extends the standard django.core.mail with many common ESP-added features, providing a consistent API that avoids locking your code to one specific ESP (and making it easier to change ESPs later if needed).
Anymail currently supports these ESPs:
Amazon SES
Brevo (formerly SendinBlue)
MailerSend
Mailgun (Sinch transactional email)
Mailjet (Sinch transactional email)
Mailtrap
Mandrill (MailChimp transactional email)
Postal (self-hosted ESP)
Postmark (ActiveCampaign transactional email)
Resend
Scaleway TEM
SendGrid (Twilio transactional email; no longer tested)
SparkPost (Bird transactional email)
Unisender Go
Anymail includes:
Integration of each ESP’s sending APIs into Django’s built-in email package, including support for HTML, attachments, extra headers, and other standard email features
Extensions to expose common ESP-added functionality, like tags, metadata, and tracking, with code that’s portable between ESPs
Simplified inline images for HTML email
Full support for Unicode characters everywhere they’re allowed in email (with workarounds where possible for ESPs that don’t quite get it right)
Normalized sent-message status and tracking notification, by connecting your ESP’s webhooks to Django signals
“Batch transactional” sends using your ESP’s merge and template features
Inbound message support, to receive email through your ESP’s webhooks, with simplified, portable access to attachments and other inbound content
Anymail maintains compatibility with all Django versions that are in mainstream or extended support, plus (usually) a few older Django versions, and is extensively tested on all Python versions supported by Django. (Even-older Django versions may still be covered by an Anymail extended support release; consult the changelog for details.)
Anymail releases follow semantic versioning. The package is released under the BSD license.
Resources
Full documentation: https://anymail.dev/en/v15.2/
Help and troubleshooting: https://anymail.dev/en/v15.2/help/
Package on PyPI: https://pypi.org/project/django-anymail/
Project on Github: https://github.com/anymail/django-anymail
Changelog: https://anymail.dev/en/v15.2/changelog/
Anymail 1-2-3
Here’s how to send a message. This example uses Mailgun, but you can substitute Amazon SES or Mailjet or Postmark or SparkPost or any other supported ESP where you see “mailgun”:
Install Anymail from PyPI:
$ pip install "django-anymail[mailgun]"(The [mailgun] part installs any additional packages needed for that ESP. Mailgun doesn’t have any, but some other ESPs do.)
Edit your project’s settings.py. In Django 6.1 or later:
INSTALLED_APPS = [ # ... "anymail", # ... ] MAILERS = { "default": { # Change "mailgun" to "amazon_ses" or "mailtrap" or another ESP "BACKEND": "anymail.backends.mailgun.EmailBackend", "OPTIONS": { # The exact options here depend on your ESP... "api_key": "<your Mailgun key>", "sender_domain": "mg.example.com", # your Mailgun domain, if needed }, }, } DEFAULT_FROM_EMAIL = "you@example.com" # if you don't already have this in settings SERVER_EMAIL = "your-server@example.com" # ditto (default from-email for Django errors)In Django 6.0 or earlier, replace MAILERS with EMAIL_BACKEND and ANYMAIL:
# Instead of MAILERS: EMAIL_BACKEND = "anymail.backends.mailgun.EmailBackend" ANYMAIL = { "MAILGUN_API_KEY": "<your Mailgun key>", "MAILGUN_SENDER_DOMAIN": 'mg.example.com', }Now the regular Django email functions will send through your chosen ESP:
from django.core.mail import send_mail send_mail("It works!", "This will get sent through Mailgun", "Anymail Sender <from@example.com>", ["to@example.com"])You could send an HTML message, complete with an inline image, custom tags and metadata:
from django.core.mail import EmailMultiAlternatives from anymail.message import attach_inline_image_file msg = EmailMultiAlternatives( subject="Please activate your account", body="Click to activate your account: https://example.com/activate", from_email="Example <admin@example.com>", to=["New User <user1@example.com>", "account.manager@example.com"], reply_to=["Helpdesk <support@example.com>"]) # Include an inline image in the html: logo_cid = attach_inline_image_file(msg, "/path/to/logo.jpg") html = """<img alt="Logo" src="cid:{logo_cid}"> <p>Please <a href="https://example.com/activate">activate</a> your account</p>""".format(logo_cid=logo_cid) msg.attach_alternative(html, "text/html") # Optional Anymail extensions: msg.metadata = {"user_id": "8675309", "experiment_variation": 1} msg.tags = ["activation", "onboarding"] msg.track_clicks = True # Send it: msg.send()
See the full documentation for more features and options, including receiving messages and tracking sent message status.
Thanks
Anymail wouldn’t exist without the work of many code contributors and countless others who have taken time to track down bugs, report issues and participate in discussions. Thank you!
Special thanks to Anymail’s sponsors for their financial support.
Anymail is an independent project not affiliated with any email service provider. Sponsorship is not meant to imply endorsement.
Release files for django-anymail 15.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_anymail-15.2.tar.gz | 110.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_anymail-15.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 261.3 kB
Release files / django_anymail-15.2.tar.gz
| Download URL | django_anymail-15.2.tar.gz |
|---|---|
| Size | 110.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
65b26b1c99e6a09051b71b012ac4dfdd75a33aeb057315944dd9fb872cae57cf
|
|
BLAKE2b-256 checksum How to use checksums |
0bf97fb704db13b2de283d51f1524861e37a87d1e4c345068c90dd578047404f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 5, 2026.
Transparency logRelease files / django_anymail-15.2-py3-none-any.whl
| Download URL | django_anymail-15.2-py3-none-any.whl |
|---|---|
| Size | 150.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
866ed547e9d3110210e6fad343a2311eead55dbd4d544195fb628d06ae25d737
|
|
BLAKE2b-256 checksum How to use checksums |
bc5afe84e7afa8297f86b95b0120e3e635d045719d217fbca321cf56d363286e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 5, 2026.
Transparency log