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

   ### Apache Airflow version
   
   2.10.4
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   Currently airflow smtp email.py utils is not taking  ```user, password``` 
values from airflow.cfg/env variables, rather it gets ```user, password``` 
values from smtp connection 
https://github.com/apache/airflow/blob/main/airflow/utils/email.py#L245-L246
   
   ```
   AIRFLOW__EMAIL__EMAIL_BACKEND: airflow.utils.email.send_email_smtp
   AIRFLOW__SMTP__SMTP_HOST: host
   AIRFLOW__SMTP__SMTP_STARTTLS: true
   AIRFLOW__SMTP__SMTP_SSL: False
   AIRFLOW__SMTP__SMTP_USER: "user@domain"
   AIRFLOW__SMTP__SMTP_PASSWORD: 'pwd'
   AIRFLOW__SMTP__SMTP_PORT: 25
   AIRFLOW__SMTP__SMTP_MAIL_FROM: [email protected] 
   ```
   
   ### What you think should happen instead?
   
   In production its not realistic to manually supply smtp user password in 
connection, thus it would be ideal to consider to get ```user and password ``` 
from airflow.cfg in case they are supplied ``AIRFLOW__SMTP__SMTP_USER: 
"user@domain"  AIRFLOW__SMTP__SMTP_PASSWORD: 'pwd' ```.
   
   
   ### How to reproduce
   
   na
   
   ### Operating System
   
   na
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] 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