-----------
Django module to easily send emails using django templates stored on database.
From box you can use it with django-celery for send background messages.
Also you have opportunity create reports from logs by mail categories and slug.
That app very simple to install and use on your projects.
Installation:
-------------
1. Using pip:
.. code-block:: bash
$ pip install django-db-mailer
2. Add the ``dbmail`` application to ``INSTALLED_APPS`` in your settings file (usually ``settings.py``)
3. Sync database (``./manage.py syncdb``)
Usage examples
--------------
.. code-block:: python
from dbmail.models import MailTemplate
from dbmail import send_db_mail
# New dbmail template
MailTemplate.objects.create(
name="Site welcome template",
subject="Welcome",
message="Welcome to our site. We are glad to see you.",
slug="welcome",
is_html=False,
)
# Send message with created template
send_db_mail(
# slug was defined on db template
slug='welcome',
# recipient can be list, or separated with comma or simple string
# 'user1@example.com' or 'user1@example.com, user2@example.com' or ['user1@example.com', 'user2@example.com']
recipient='user1@example.com',
# All *args params will be accessible on template context
{
'username': request.user.username,
'full_name': request.user.get_full_name(),
'signup_date': request.user.date_joined
},
# You can access to all model fields. For m2m and fk fields, you should use module_name
MyModel.objects.get(pk=1),
# Optional kwargs:
# from_email='from@example.com'
# cc=['cc@example.com'],
# bcc=['bcc@example.com'],
# user=User.objects.get(pk=1),
# from_email='bcc@example.com',
# attachments=[(filename, content, mimetype)],
# headers={'Custom-Header':'Some value'},
)
Local demo installation
-----------------------
.. code-block:: bash
$ sudo apt-get install virtualenvwrapper
$ mkvirtualenv django-db-mailer
$ git clone https://github.com/gotlium/django-db-mailer.git
$ cd django-db-mailer
$ python setup.py develop
$ cd demo
$ pip install -r requirements.txt
$ python manage.py syncdb
$ python manage.py migrate
$ python manage.py runserver
Screenshots
-----------
.. image:: /screenshots/template_edit.jpg
.. image:: /screenshots/templates_changelist.jpg
.. image:: /screenshots/template_log_changelist.jpg
.. image:: /screenshots/template_log_view.jpg
Compatibility:
-------------
* Python: 2.6, 2.7
* Django: 1.4, 1.5, 1.6
Metadata
Release files for django-db-mailer 1.0
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 |
|---|---|---|---|---|
| django-db-mailer-1.0.tar.gz | 19.1 kB | Without provenance | Details for django-db-mailer-1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_db_mailer-1.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for django_db_mailer-1.0-py2.py3-none-any.whl |
Total release size: 36.0 kB
Release files / django-db-mailer-1.0.tar.gz
| Download URL | django-db-mailer-1.0.tar.gz |
|---|---|
| Size | 19.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b91e682bd9528186d5c21a5ef518d37d2b419729da7677dc86d20021f065e7a
|
|
BLAKE2b-256 checksum How to use checksums |
a10d0599bc20c57a9fe19e8197c94bd4d9073aacd4e80bf75678a2dce3847079
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / django_db_mailer-1.0-py2.py3-none-any.whl
| Download URL | django_db_mailer-1.0-py2.py3-none-any.whl |
|---|---|
| Size | 16.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
e727a939ff59cbfc999d5cc7a953b43bcc056ae5f3bb87c1bb46f095b0f78089
|
|
BLAKE2b-256 checksum How to use checksums |
3ebdfeb41eeb2b719318ebc078e88deb1a92ddfcd148636f531af7ed116198c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-db-mailer 1.0
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.