chulkilee opened a new issue, #40226:
URL: https://github.com/apache/airflow/issues/40226

   ### What do you see as an issue?
   
   [Email 
Configuration](https://airflow.apache.org/docs/apache-airflow/stable/howto/email-config.html)
 mentions
   
   > To configure SMTP settings, checkout the 
[SMTP](https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#config-smtp)
 section in the standard configuration. If you do not want to store the SMTP 
credentials in the config or in the environment variables, you can create a 
connection called smtp_default of Email type, or choose a custom connection 
name and set the email_conn_id with its name in the configuration & store SMTP 
username-password in it. Other SMTP settings like host, port etc always gets 
picked up from the configuration only. The connection can be of any type (for 
example ‘HTTP connection’).
   
   However, [SMTP 
Connection](https://airflow.apache.org/docs/apache-airflow-providers-smtp/1.0.0/connections/smtp.html)
 does not mention that such limitation.
   
   As a result, even SMTP connection test passes, the connection cannot be used 
in DAG failture notification. This is quite counter-intuitive, confusing, and 
misleading for users expecting STMP connection holds all information for all 
cases.
   
   See https://github.com/apache/airflow/issues/37442 for example.
   
   ### Solving the problem
   
   Either Airflow notification picks up all other attributes (other than 
credentials), or SMTP connection doc and UI should mention the limitation.
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to