#26228: 500 Exceptions not logged if firewall blocks outgoing SMTP
---------------------------------+--------------------------------------
Reporter: ryanfox | Owner:
Type: Bug | Status: closed
Component: Error reporting | Version: 1.9
Severity: Normal | Resolution: needsinfo
Keywords: logging | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by ryanfox):
Replying to [comment:1 timgraham]:
> Is there a problem if the value of
[https://docs.djangoproject.com/en/stable/ref/settings/#email-timeout
settings.EMAIL_TIMEOUT] is less than the value of Gunicorn's timeout?
>
> I don't understand what change you're proposing.
I wasn't aware of that setting. At any rate, I was just wondering if it
would be possible to log to the unlikely-to-fail handlers (e.g. writing to
file) before logging to the possible-to-fail handlers (e.g. email). If
this isn't feasible, I guess there's nothing to be done for it, but I
thought it may be nice to safeguard against the contingency.
--
Ticket URL: <https://code.djangoproject.com/ticket/26228#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.726317e75fa6d1bc0331eb43d48cfddf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.