Django EmailLog Backend
Simple email backend for Django that writes messages to logger instead of sending them to a SMTP server.
Installation
Installation is easy using pip
pip install django-emaillog-backend
Usage
To ensure that all emails sent using the send_mail function of Django are sent to a log you must add the following line to your settings.py file:
EMAIL_BACKEND = 'django_emaillog_backend.backends.LoggerBackend'
You can specify the logger to which the logs will be sent adding it to the settings.py file
EMAIL_LOGGER_NAME = 'your_logger_name'
For example, you can create a custom logger to test the correct behaviour of sending mails as follow:
# Add a custom logger to test mails
LOGGING = {
'version': 1,
'disable_existing_loggers': False,
'formatters': {
...
},
'handlers': {
...
},
'loggers': {
...
'email_logger': {
'handlers': ['your_handler'],
'propagate': True,
'level': 'DEBUG',
},
}
}
# Configure the email backend
EMAIL_BACKEND = 'django_emaillog_backend.backends.LoggerBackend'
EMAIL_LOGGER_NAME = 'email_logger'
The default logger for django-emaillog-backend is the global Django logger called 'django'.
It is also possible to choose the severity level of messages sent to the logger adding the following to your settings.py file:
EMAIL_LOGGER_LEVEL = logger_level
EMAIL_LOGGER_LEVEL expects an integer. We recommend using the severity levels of the logging module:
logging.DEBUG (10)
logging.INFO (20)
logging.WARNING (30)
logging.ERROR (40)
logging.CRITICAL (50)
For example:
import logging
EMAIL_LOGGER_LEVEL = logging.INFO
The default log level is INFO.
Metadata
Release files for django-emaillog-backend 0.1.2
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-emaillog-backend-0.1.2.tar.gz | 4.1 kB | Without provenance | Details for django-emaillog-backend-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_emaillog_backend-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for django_emaillog_backend-0.1.2-py3-none-any.whl |
Total release size: 8.3 kB
Release files / django-emaillog-backend-0.1.2.tar.gz
| Download URL | django-emaillog-backend-0.1.2.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
623ec317e64db7ac05ee7b94b399ab81fbe37dc700121197b29d74cf1bb26e4a
|
|
BLAKE2b-256 checksum How to use checksums |
52544c5b4472347c36e9b54e21ffe5da6128787a824822966685763ce2f9214d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.4
|
Release files / django_emaillog_backend-0.1.2-py3-none-any.whl
| Download URL | django_emaillog_backend-0.1.2-py3-none-any.whl |
|---|---|
| Size | 4.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1ce48630c00829ff3721945aa4273dbdd04b2ae9b9d23bd396c22b99a5bd9f8c
|
|
BLAKE2b-256 checksum How to use checksums |
f5abb63f1c1553df86ec2abaff06f06b4bdbdb51ef500bd53a10356a07044dcf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.4
|
Security for django-emaillog-backend 0.1.2
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.