finds.dev

vintasoftware/django-templated-email

Django module to easily send templated emails using django templates, or using a transactional mail provider (mailchimp, silverpop, etc.)

View on GitHub

★ 780PythonMITupdated Sep 2025

// the take

A thin wrapper around Django's templating and EmailMessage that lets you render an email's subject/text/HTML parts from one template file instead of wiring three separate pieces together by hand. Useful for anyone already on Django who doesn't want to pull in a full transactional-email SDK just to send templated mail, and it plugs into Anymail if you do want provider features like tags or tracking.

The backend abstraction is genuinely useful — vanilla_django for plain SMTP/console backends, or swap in Anymail's EmailMessage classes via a settings flag to get provider-specific features without changing call sites. The {% block subject/plain/html %} template convention with auto-plaintext-from-HTML (via html2text) removes a lot of the boilerplate of maintaining parallel text/HTML copies by hand. The CBV mixin (TemplatedEmailFormViewMixin) is a practical touch for the common "send confirmation email after a form submits" pattern. It's still actively maintained — Django 5.1 and Python 3.13 support, GitHub Actions CI with coverage, last push September 2025.

The "view email on the web" feature stores a full copy of every rendered email in the database with no built-in cleanup, retention, or pagination — the docs literally say "you are responsible for managing it," which means unbounded table growth is on you from day one. InlineImage attachments get uploaded to your media storage on every send too, same unmanaged-growth problem, and any InlineImage you put in the context gets attached even if the template never references it, which is an easy way to silently balloon email size. There's no async/queue integration out of the box — sending is synchronous against whatever Django mail backend you configure, so retries, backoff, and failure handling are entirely on you (the docs just suggest overriding a method to "use a celery task," not actually providing one). Fundamentally it's a templating convenience layer, not an email infrastructure layer — deliverability, rate limiting, and bounce handling are all out of scope, so it solves a small problem well but won't save you from needing a real ESP integration for anything production-grade.

We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
780
Forks
134
Language
Python
License
MIT
Last commit
29 Sep 2025

// nearby

If django-templated-email isn't quite it.

All repos →