SMTP not using mail settings when the Celery backend is used #451
Unanswered
computergeek125
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm a bit at a loss for this one.
When I try to send password reset emails, I can see errors that look like this in the log (and no mail is delivered):
If I run tcpdump when this is occuring, I can find: that its trying to talk to this server:
static.93.10.69.159.clients.your-server.de
- which appears to be the rDNS record of mediacms.io (which I remember was in the default configuration)If I run the debugging test from the docs page, the entire process works - I receive the test email.
However, if I modify the test script to look like this (reflecting the Celery backend instead of the default Django backend), the email fails again.
Extending that theory to the main config, if I set
EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'
in thelocal_settings.py
, emailing works, but (since I think this made it a synchronous action), pages that trigger email seem to take a bit longer to load.I feel like I've done something incredibly stupid while setting this up, but I'm not sure what part of the config would cause it to use default settings only when a certain backend is in use.
I am running 9e7a7a7
Beta Was this translation helpful? Give feedback.
All reactions