dosubot[bot] commented on issue #33815:
URL: https://github.com/apache/superset/issues/33815#issuecomment-2983761114

   <!-- Greeting -->
   Hi @clp007! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the 
superset team.
   
   <!-- Answer -->
   The most common reason for reports not sending emails in Superset 
(especially with docker-compose) is the ALERT_REPORTS_NOTIFICATION_DRY_RUN 
setting. In many Docker setups, this defaults to True, which means emails are 
never actually sent, but no error is shown. You have set it to False, which is 
correct—just make sure this is set in your actual superset_config.py or 
superset_config_docker.py and that the file is mounted or copied into your 
container as expected. If it's not picked up, Superset will silently stay in 
dry-run mode and not send emails, even though everything else looks fine 
([source](https://github.com/apache/superset/blob/a1cbd2578e24ed6c72024e1d1cf195846ace05d7/docker/pythonpath_dev/superset_config.py)).
   
   If dry-run is definitely off, the next most likely cause is SMTP 
misconfiguration. Superset needs working SMTP settings (SMTP_HOST, SMTP_PORT, 
SMTP_USER, SMTP_PASSWORD, SMTP_MAIL_FROM, etc). The default config points to 
localhost:25, which usually won’t work unless you have a local mail server 
running in your Docker network. You can test your SMTP settings with a simple 
Python script to confirm connectivity ([example and 
troubleshooting](https://github.com/apache/superset/discussions/31398)).
   
   Also, check that your Celery workers are running and connected, and that 
your network/firewall allows outbound SMTP connections. If you still don’t see 
errors, check the ReportExecutionLog table in your Superset database for hidden 
error messages.
   
   Let me know if you want a sample SMTP test script or more details on any of 
these steps.
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   <sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/37680e44-ee0c-4044-887f-0b0636fb3f16?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/37680e44-ee0c-4044-887f-0b0636fb3f16?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/37680e44-ee0c-4044-887f-0b0636fb3f16?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/37680e44-ee0c-4044-887f-0b0636fb3f16?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/37680e44-ee0c-4044-887f-0b0636fb3f16?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/37680e44-ee0c-4044-887f-0b0636fb3f16?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/37680e44-ee0c-4044-887f-0b0636fb3f16?feedback_type=other)</sup>&nbsp;&nbsp;[![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[!
 [Share on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/33815)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to