Djrill integrates the Mandrill transactional email service into Django.
This is a fork of the inactive brack3t’s Djrill.
In general, Djrill “just works” with Django’s built-in django.core.mail package. It includes:
Support for HTML, attachments, extra headers, and other features of Django’s built-in email
Mandrill-specific extensions like tags, metadata, tracking, and MailChimp templates
Optional support for Mandrill inbound email and other webhook notifications, via Django signals
Djrill is released under the BSD license. It is tested against Django 4.0-5.2. Djrill uses semantic versioning.
Resources
Full documentation: https://djrill.readthedocs.io/en/latest/
Package on PyPI: https://pypi.python.org/pypi/djrill-fork
Project on Github: https://github.com/Yupeek/Djrill
Djrill 1-2-3
Install Djrill from PyPI:
$ pip install djrill-forkEdit your project’s settings.py:
INSTALLED_APPS = ( ... "djrill" ) MANDRILL_API_KEY = "<your Mandrill key>" EMAIL_BACKEND = "djrill.mail.backends.djrill.DjrillBackend" DEFAULT_FROM_EMAIL = "you@example.com" # if you don't already have this in settingsNow the regular Django email functions will send through Mandrill:
from django.core.mail import send_mail send_mail("It works!", "This will get sent through Mandrill", "Djrill Sender <djrill@example.com>", ["to@example.com"])You could send an HTML message, complete with custom Mandrill tags and metadata:
from django.core.mail import EmailMultiAlternatives msg = EmailMultiAlternatives( subject="Djrill Message", body="This is the text email body", from_email="Djrill Sender <djrill@example.com>", to=["Recipient One <someone@example.com>", "another.person@example.com"], headers={'Reply-To': "Service <support@example.com>"} # optional extra headers ) msg.attach_alternative("<p>This is the HTML email body</p>", "text/html") # Optional Mandrill-specific extensions: msg.tags = ["one tag", "two tag", "red tag", "blue tag"] msg.metadata = {'user_id': "8675309"} # Send it: msg.send()
See the full documentation for more features and options.
Metadata
Release files for djrill-fork 2.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| djrill_fork-2.2.1.tar.gz | 15.9 kB | Without provenance | Details for djrill_fork-2.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| djrill_fork-2.2.1-py3-none-any.whl | Python 3 | none | any | Details for djrill_fork-2.2.1-py3-none-any.whl |
Total release size: 31.4 kB
Release files / djrill_fork-2.2.1.tar.gz
| Download URL | djrill_fork-2.2.1.tar.gz |
|---|---|
| Size | 15.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
856c7604abbaef28841ffae51b8890db77ece2d0d9e74549294e44bfe7547acb
|
|
BLAKE2b-256 checksum How to use checksums |
131e2fdb0f5b70ae18a600bda5a1aa44062e1d4c6cd8d23eceebeedec97d63cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.2
|
Release files / djrill_fork-2.2.1-py3-none-any.whl
| Download URL | djrill_fork-2.2.1-py3-none-any.whl |
|---|---|
| Size | 15.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
646e5c14508c1d429dcceb2fdc1f0de71b6fac3aa599fb965edeae49d4a0e491
|
|
BLAKE2b-256 checksum How to use checksums |
a94520192a6983421a2d07e5c41e65a58be6d6bb5d0b22bfed1dfad44cd83978
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.2
|
Security for djrill-fork 2.2.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.