#37161: Implement a system check for no default MAILERS configuration
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Bader
| Eddine Benhirt
Type: New feature | Status: assigned
Component: Core (Mail) | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mike Edmunds):
* needs_better_patch: 0 => 1
Comment:
Thanks, Natalia. I agree with everything you said.
Replying to [comment:15 Natalia Bidart]:
> […] For that reason, I would support a check only when `MAILERS` is
explicitly defined by the project. At that point, Django can reasonably
assume the project intends to use the email framework and validate the
configuration accordingly. In particular, warning when `MAILERS` is
defined but does not contain a `"default"` alias seems reasonable to me.
[…]
Once the current PR is updated to reflect this, I think it will be ready.
--
Ticket URL: <https://code.djangoproject.com/ticket/37161#comment:18>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019ecd1fe154-43fba243-e929-4721-9b15-ffd9c78c291f-000000%40eu-central-1.amazonses.com.
