zachliu opened a new issue #21878: URL: https://github.com/apache/airflow/issues/21878
### Apache Airflow version 2.2.4 (latest released) ### What happened After setting up alert emails using AWS SES as instructed [here](https://airflow.apache.org/docs/apache-airflow/stable/howto/email-config.html#send-email-using-aws-ses), I received the following error message: ``` Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/airflow/models/taskinstance.py", line 2103, in email_alert send_email(self.task.email, subject, html_content) File "/usr/local/lib/python3.8/site-packages/airflow/utils/email.py", line 57, in send_email return backend( TypeError: send_email() got multiple values for argument 'from_email' ``` ### What you expected to happen the `send_email` method in https://github.com/apache/airflow/blob/d94fa378305957358b910cfb1fe7cb14bc793804/airflow/providers/amazon/aws/utils/emailer.py#L25-L37 doesn't match the invocation of the `backend` method in https://github.com/apache/airflow/blob/ee9049c0566b2539a247687de05f9cffa008f871/airflow/utils/email.py#L57-L70 in the former (provider-amazon), the `from_email` is the first positional argument. However in the latter (main airflow), `from_email` is misplaced as a keyword argument. ### How to reproduce 1. Use `Airflow 2.2.4` with `providers-amazon/3.0.0` 2. Observe the log from a failed DAG ### Operating System Amazon Linux 2 ### Versions of Apache Airflow Providers apache-airflow-providers-amazon 3.0.0 ### Deployment Other Docker-based deployment ### Deployment details _No response_ ### 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]
