Skip to main content

The one and only django app to receive & send mail with templates and multiple configurations.

Project description

Django Mail Admin

.. image::

.. image::

.. image::

The one and only django app to receive & send mail with templates and multiple configurations.


.. image::
.. image::


* Everything django-mailbox has
* Everything django-post-office has
* Database configurations - activate an outbox to send from, activate a mailbox to receive from
* Templates
* Translatable
* Mailings - using send_many() or 'cc' and 'bcc' or even recipients - all of those accept comma-separated lists of emails


* `django >= 1.9 <>`_
* `django-jsonfield <>`_


The full documentation is at


**Q**: What versions of Django/Python are supported?
**A**: Take a look at

Install django mail admin::

pip install django_mail_admin

Add it to your `INSTALLED_APPS`:

.. code-block:: python


* Run ``migrate``::

python migrate django_mail_admin

* Set ``django_mail_admin.backends.CustomEmailBackend`` as your ``EMAIL_BACKEND`` in django's ````::

EMAIL_BACKEND = 'django_mail_admin.backends.CustomEmailBackend'

* Set cron/Celery/RQ job to send/receive email, e.g. ::

* * * * * (cd $PROJECT; python send_queued_mail --processes=1 >> $PROJECT/cron_mail.log 2>&1)
* * * * * (cd $PROJECT; python get_new_mail >> $PROJECT/cron_mail_receive.log 2>&1)
0 1 * * * (cd $PROJECT; python cleanup_mail --days=30 >> $PROJECT/cron_mail_cleanup.log 2>&1)

.. note::

Once you have entered a mailbox to receive emails, you can easily verify that you
have properly configured your mailbox by either:

* From the Django Admin, using the 'Get New Mail' action from the action
dropdown on the Mailbox changelist
* *Or* from a shell opened to your project's directory, using the
``get_new_mail`` management command by running::

python get_new_mail

If you have also configured the Outbox, you can verify that it is working, e.g. ::

from django_mail_admin import mail, models

'', # List of email addresses also accepted
subject='My email',
message='Hi there!',,
html_message='Hi <strong>there</strong>!',

Custom Email Backends

By default, ``django_mail_admin`` uses custom Email Backends that looks up for Outbox models in database. If you want to
use a different backend, you can do so by configuring ``BACKENDS``, though you will not be able to use Outboxes and will have to set EMAIL_HOST etc. in django's ````.

For example if you want to use `django-ses <>`_::

'default': 'django_mail_admin.backends.CustomEmailBackend',
'smtp': 'django.core.mail.backends.smtp.EmailBackend',
'ses': 'django_ses.SESBackend',

You can then choose what backend you want to use when sending mail:

.. code-block:: python

# If you omit `backend_alias` argument, `default` will be used

# If you want to send using `ses` backend

Optional requirements

1. `django_admin_row_actions` for some useful actions in the admin interface
2. `requests` & social_django for Gmail


**Q**: Why did you write this?

**A**: In order to get both email sending & receiving you'll have to install post_office AND django_mailbox.
Even if you do, you'll have to work on admin interface for it to look prettier, somehow link replies properly etc.
So I've decided merging those two and clearing the mess in between them as well as adding some other useful features.

**Q**: Why did you remove support for Python 2?

**A**: Because f*ck python2. Really, it's been 9 (NINE!) years since it came out. Go ahead and check out

**Q**: Why is it named django_mail_admin, what does it have to do with admin ?

**A**: Well, the first version of this package (which was living just in a really large was used for easy mail management using standard Django admin interface.

**Q**: What languages are available?

**A**: Currently there's Russian and English languages available. Feel free to add yours:


source <YOURVIRTUALENV>/bin/activate
python makemessages -l YOUR_LOCALE -i venv
python compilemessages -l YOUR_LOCALE

**Q**: Why did you delete support for multi-lingual templates?

**A**: Well, we have django-model-translations for that. You can easily fork this app and override EmailTemplate model (models/ accordingly.
I think there's no need for such an overhead in a mail-related app.

**Q**: I don't want my outgoing emails to be queued for sending after saving them in the admin interface, what do i do?

**A**: Just override OutgoingEmailAdmin's save_model method.

**Q**: Can i get in touch with you? I want a new feature to be implemented/bug fixed!

**A**: Feel free to reach me out using issues and pull requests, I'll review them all and answer when I can.

Running Tests

Does the code actually work?


source <YOURVIRTUALENV>/bin/activate
(myenv) $ pip install tox
(myenv) $ tox


Tools used in rendering this package:

* Cookiecutter_
* `cookiecutter-djangopackage`_

.. _Cookiecutter:
.. _`cookiecutter-djangopackage`:


0.1.3 (2018-06-02)

* Added additional params to cleanup_email command

0.1.2 (2017-12-29)

* Added migrations.

0.1.1 (2017-12-29)

* Added docs, added locale, fixed bugs
* Fixed reply detection
* Added get_new_mail management command

0.1.0 (2017-12-29)

* First release on PyPI.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date
django_mail_admin-0.1.3-py2.py3-none-any.whl (50.1 kB) Copy SHA256 hash SHA256 Wheel 3.6
django_mail_admin-0.1.3.tar.gz (36.1 kB) Copy SHA256 hash SHA256 Source None

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN SignalFx SignalFx Supporter DigiCert DigiCert EV certificate StatusPage StatusPage Status page