Store mails with waiting and active queues and send them asynchronously
Python Makefile Shell
Latest commit 6047c87 Feb 2, 2015 @thoas Update README.rst
Failed to load latest commit information.
docs Add basic docs directory for rtd Jan 5, 2013
rq_mail Bump to 0.1.3 Sep 13, 2013
test_project Add test_project/ to the root, add Makefile Sep 26, 2012
.gitignore Add basic docs directory for rtd Jan 5, 2013
README.rst Update README.rst Feb 2, 2015
requirements.txt WIP: initial commit Sep 19, 2012 Add README to Sep 26, 2012



This project is not maintained anymore, it doesn't support latest changes from rq

django-rq-mail is a simple Python library based on rq to store emails sent by Django and process them in the background with workers.

As django-rq-mail is based on rq, it's entirely backed by Redis.


django-rq-mail adds new elements to enjoy Sorted Sets from Redis.

For the purpose of django-rq-mail, it implements the concept of WaitingQueue which delays the processing of a job with a timestamp.

The default behavior of rq is to process jobs via BLPOP which blocks the connection when there are no elements to pop from any of the given queues. With this behavior there is no way to delays the processing of a job and when it's failing rq pushs it in a failed queue. Of course, you can requeue this job later but there is no fallback mechanism.

In django-rq-mail you can define fallback steps (in seconds) to retry a job until it's not failing. When a job has been tested on each steps we reintroduce the default behavior of rq on pushing it in the failed queue.

Each steps will create a waiting queue and when a job is failing we take the current timestamp with the delta to retry it in the future.

This mechanism is possible with ZADD which adds a serialized job in the queue with a score and ZREVRANGEBYSCORE to return all the elements in the sorted set with a score between max (current timestamp) and min.

As you may understood, we have dropped the default blocking behavior to replace it by a daemon which is running each seconds.


  1. Either check out the package from GitHub or it pull from a release via PyPI

    pip install django-rq-mail
  2. Add 'rq_mail' to your INSTALLED_APPS


to use the rq_mail command (via Django commandline) shipped by django-rq-mail.

This command is a minimal integration of rq into Django to launch the Dispatcher.


    EMAIL_BACKEND = 'rq_mail.backends.RqBackend'
  2. Define RQ_MAIL_EMAIL_BACKEND the backend used to send your emails, for example

    RQ_MAIL_EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'


RQ 0.3.3 uses standard Python's logging, this means you can easily configure rqworker's logging mechanism in django's For example:

    'version': 1,
    'disable_existing_loggers': False,
    'formatters': {
        'rq_console': {
            'format': '%(asctime)s %(message)s',
            'datefmt': '%H:%M:%S',
    'handlers': {
        'rq_console': {
            'level': 'DEBUG',
            'class': 'rq.utils.ColorizingStreamHandler',
            'formatter': 'rq_console',
            'exclude': ['%(asctime)s'],
    'loggers': {
        'rq.worker': {
            'handlers': ['rq_console'],
            'level': 'DEBUG'


Once you have installed it, you can run python rq_mail from your shell.



The prefix used to name all queues created by django-rq-mail.


The name of the main queue.


The email backend used to send emails when they are processed in the background.


The Redis host used to connect.


The Redis port used to connect.


The Redis database used to connect.


The Redis password used to connect.


The Redis url used to connect.


The Redis socket used to connect.


A simple list of timing to create waiting queues.

You can define as much steps as you want, each will be transformed to a queue. So if you define 10 steps, you will allow a message to fail 10 times until it will go in the failed queue.