#34167: Set a reasonable default for EMAIL_TIMEOUT
-------------------------------------+-------------------------------------
Reporter: Federico Capoano | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Mail) | Version: 4.1
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by Federico Capoano:
Old description:
> For the record, I started a discussion here: https://groups.google.com/g
> /django-developers/c/XZbKeM8fVxU/m/jp0h8U4tBgAJ
New description:
Why there's no default for EMAIL_TIMEOUT?
Applications built in Django can potentially stall indefinitely if email
sending starts to hang (eg: if the SMTP server is overloaded), when this
happens, since there's no timeout, there's also no error being logged, so
it's very hard and time consuming to debug.
Wouldn't it be better to set a timeout? Some high value like 2 minutes
which wouldn't really make sense to wait any longer, so at least if and
when this happens, developers will find error traces in the logs and
quickly understand where the problem is coming from, instead of spending
hours to debug it like I did in the past week.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/34167#comment:3>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/010701849a53343a-31e6fc0b-7826-4db0-ad5f-49dd25344db3-000000%40eu-central-1.amazonses.com.
