-
Notifications
You must be signed in to change notification settings - Fork 13.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
celeryconfig.py #29556
Comments
To resolve the issue where emails cannot be sent according to your configuration in # smtp server configuration
EMAIL_NOTIFICATIONS = True # Enable email notifications
SMTP_HOST = "your_smtp_host"
SMTP_STARTTLS = True
SMTP_SSL = False
SMTP_USER = "your_smtp_user"
SMTP_PORT = 587 # or the port your SMTP server uses
SMTP_PASSWORD = "your_smtp_password"
SMTP_MAIL_FROM = "[email protected]"
SMTP_SSL_SERVER_AUTH = False
ENABLE_CHUNK_ENCODING = False
# Optional: Customize email headers
def email_header_mutator(msg, **kwargs):
# Example: Add a custom header
msg["X-Custom-Header"] = "CustomValue"
return msg
EMAIL_HEADER_MUTATOR = email_header_mutator Make sure to replace the placeholder values ( Additionally, ensure that The If you continue to experience issues, you can refer to the |
It might help if you can provide a more complete Issue title, and provide any errors (server side or client side) that you see. Most of us can't read the screenshots, so if you can help us understand what those illustrate, that'd be helpful. Lastly, it might help to throw your config file at the bots in the |
Bug description
superset_config.py.zip
This is my profile, and according to this configuration, the email cannot be sent
How to reproduce the bug
Screenshots/recordings
No response
Superset version
4.0.1
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: