Pinax is an open-source platform built on the Django Web Framework. It is an ecosystem of reusable Django apps, themes, and starter project templates. This collection can be found at http://pinaxproject.com.
This app was developed as part of the Pinax ecosystem but is just a Django app and can be used independently of other Pinax apps.
django-mailer is a reusable Django app for queuing the sending of email.
It works by storing email in the database for later sending.
Keep in mind that file attachments are also temporarily stored in the database, which means if you are sending files larger than several hundred KB in size, you are likely to run into database limitations on how large your query can be. If this happens, you'll either need to fall back to using Django's default mail backend, or increase your database limits (a procedure that depends on which database you are using).
- Django >= 1.11
- Databases: django-mailer supports all databases that Django supports, with the following notes:
- SQLite: you may experience 'database is locked' errors if the
send_mailcommand runs when anything else is attempting to put items on the queue. For this reason SQLite is not recommended for use with django-mailer.
- SQLite: you may experience 'database is locked' errors if the
Simple usage instructions:
In settings.py:
INSTALLED_APPS = [
...
"mailer",
...
]
EMAIL_BACKEND = "mailer.backend.DbBackend"
Run database migrations to set up the needed database tables.
Then send email in the normal way, as per the Django email docs, and they will be added to the queue.
To actually send the messages on the queue, add this to a cron job file or equivalent:
* * * * * (/path/to/your/python /path/to/your/manage.py send_mail >> ~/cron_mail.log 2>&1) 0,20,40 * * * * (/path/to/your/python /path/to/your/manage.py retry_deferred >> ~/cron_mail_deferred.log 2>&1)
To prevent from the database filling up with the message log, you should clean it up every once in a while.
To remove successful log entries older than a week, add this to a cron job file or equivalent:
0 0 * * * (/path/to/your/python /path/to/your/manage.py purge_mail_log 7 >> ~/cron_mail_purge.log 2>&1)
See usage.rst in the docs for more advanced use cases - https://github.com/pinax/django-mailer/blob/master/docs/usage.rst#usage.
The Pinax documentation is available at http://pinaxproject.com/pinax/.
See CONTRIBUTING.rst for information about contributing patches to django-mailer.
See this blog post http://blog.pinaxproject.com/2016/02/26/recap-february-pinax-hangout/ including a video, or our How to Contribute (http://pinaxproject.com/pinax/how_to_contribute/) section for an overview on how contributing to Pinax works. For concrete contribution ideas, please see our Ways to Contribute/What We Need Help With (http://pinaxproject.com/pinax/ways_to_contribute/) section.
In case of any questions we recommend you join our Pinax Slack team (http://slack.pinaxproject.com) and ping us there instead of creating an issue on GitHub. Creating issues on GitHub is of course also valid but we are usually able to help you faster if you ping us in Slack.
We also highly recommend reading our Open Source and Self-Care blog post (http://blog.pinaxproject.com/2016/01/19/open-source-and-self-care/).
In order to foster a kind, inclusive, and harassment-free community, the Pinax Project has a code of conduct, which can be found here http://pinaxproject.com/pinax/code_of_conduct/. We ask you to treat everyone as a smart human programmer that shares an interest in Python, Django, and Pinax with you.
For updates and news regarding the Pinax Project, please follow us on Twitter at @pinaxproject and check out our blog http://blog.pinaxproject.com.