- Added
MAILER_EMAIL_LOG_MESSAGE_DATA
setting, thanks @eht16. - Added support for
psycopg3
forrunmailer_pg
, thanks @jsmits.
- Fixed rare crasher in runmailer_pg when notifications list is empty.
- Dropped Python 3.7 support.
- Added
runmailer_pg
- advanced sending method for sending emails without delay immediate, PostgreSQL only.
- Added admin action to send messages
- Added fix for email address that is a
NoneType
- Stopped testing on unsupported Python (<3.7) and Django (<2.2) versions
- Started testing on Python 3.11 and Django 4.1/4.2
- Added setting to limit the amount of retries for deferred messages
(
MAILER_EMAIL_MAX_RETRIES
), defaults toNone
(unlimited) (See Issue #161)
- Migrate models
id
fields toBigAutoField
. - Added
runmailer
management command. This command starts a loop that frequently checks the database for new emails. The wait time between checks can be controlled using theMAILER_EMPTY_QUEUE_SLEEP
setting.
- The
retry_deferred
andsend_mail
commands rely on the log level set in your django project now. The-c/--cron
option in those commands has been deprecated and the logic to configure log levels and the message format has been removed. - Changed logging to use module specific loggers to avoid interfering with other loggers.
- Added
MAILER_USE_FILE_LOCK
setting to allow disabling file based locking. - Added
-r
option topurge_mail_log
management command. Thanks julienc91 - Fixed deprecation warnings on Django 3.1
- Use cached DNS_NAME for performance
- Added ability to override the default error handler via the
MAILER_ERROR_HANDLER
settings key
- Fixed issue with migration that some people experienced (see PR 118)
Django 3.0 support
Dropped support for old Django versions (before 1.11)
Changed DB
priority
field to an integer, instead of text field container an integerMulti-process safety for sending emails via database row-level locking.
Previously, there was a file-system based lock to ensure that multiple processes were not attempting to send the mail queue, to stop multiple sending of the same email. However, this mechanism only works if all processes that might be attempting to do this are on the same machine with access to the same file-system.
Now, in addition to this file lock, we use transactions and row-level locking in the database when attempting to send a message, which guarantees that only one process can send the message. In addition, for databases that support
NOWAIT
withSELECT FOR UPDATE
, such as PostgreSQL, if multiple processes attempt to send the mail queue at the same time, the work should be distributed between them (rather than being done by only one process).A negative consequence is that SQLite support is degraded: due to the way it implements locking and our use of transactions when sending the email queue, you can get exceptions in other processes that are trying to add items to the queue. Use of SQLite with django-mailer is not recommended.
retry_deferred
command has also been updated to be simpler and work correctly for multiple processes.Dropped some backwards compat support for Django < 1.8. If you are upgrading from a version of Django before 1.8, you should install a version of django-mailer < 2.0, do
send_all
to flush the queue, then upgrade django-mailer to 2.0 or later.
- Official Django 2.1 and 2.2 support.
- Don't close DB connection in management commands. This is unnecessary with modern Django.
- Fixed packaging file permission problems.
- Added Japanese locale (thanks msk7777)
- Django 2.0 support.
- Fixed crasher with models
__str__
- Django 1.10 support.
- Fixed reprs for Message and MessageLog.
- More helpful admin for Message and MessageLog
- Handle exceptions from really old Django versions
Save the
Message-ID
header onMessage
explicitly to enable finding emails using this identifier.This includes a database schema migration.
- Deprecated calling
send_mail
andsend_html_mail
usingpriority
kwargs"high"
,"medium"
, and"low"
. Instead you should usePRIORITY_HIGH
,PRIORITY_MEDIUM
andPRIORITY_LOW
frommailer.models
. - Fixed bug with migrations for Django 1.7, which wanted to create a migration to 'fix' the EmailField length back down to 75 instead of 254.
Included migrations - for both South and Django 1.7 native migrations.
Note:
- If you use South, you will need at least South 1.0
- You will need to use '--fake' or '--fake-initial' on existing installations.
These migrations were supposed to be in 1.0.0 but were omitted due to a packaging error.
- Throttling of email sending
- Django 1.8 support
- Admin tweaks and improvements
- Various other fixes, especially from Renato Alves <[email protected]> - thank you!
- First PyPI version