[
https://issues.apache.org/jira/browse/AIRFLOW-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747373#comment-16747373
]
ASF GitHub Bot commented on AIRFLOW-3628:
-----------------------------------------
yujiantao commented on pull request #4435: [AIRFLOW-3628] Add smtp_mime_from
URL: https://github.com/apache/airflow/pull/4435
Make sure you have checked _all_ steps below.
### Jira
- [ ] My PR addresses the following [Airflow
Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references
them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-3628
- In case you are fixing a typo in the documentation you can prepend your
commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
### Description
- [ ] Here are some details about my PR, including screenshots of any UI
changes:
In airflow alert email, the value of the from field is the source email
address, but sometimes we want to show the receiver where the alert is really
from. For example, the email was sent from [email protected], but we want to
show the receiver it was from "airflow", so that it is easy to distinguish it
from other messages. With this PR, we just need to set "smtp_mime_from =
"airflow" in airflow.cfg.
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
### Commits
- [ ] My commits all reference Jira issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [ ] In case of new functionality, my PR adds documentation that describes
how to use it.
- When adding new operators/hooks/sensors, the autoclass documentation
generation needs to be added.
- All the public functions and the classes in the PR contain docstrings
that explain what it does
### Code Quality
- [ ] Passes `flake8`
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> set MIME from in alert email
> ----------------------------
>
> Key: AIRFLOW-3628
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3628
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: yu jiantao
> Assignee: yu jiantao
> Priority: Major
>
> In airflow alert email, the value of the from field is the source email
> address, but sometimes we want to show the receiver where the alert is really
> from. For example, the email was sent from [email protected], but we want
> to show the receiver it was from "BDP-airflow", so that it is easy to
> distinguish it from other messages.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
