-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Add a list of no-reply sender addresses #13367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This would add a (not complete) list of sender addresses that are currently used by Microsoft services. This list might be useful for people to know when dealing with delivery issues. It might also help to even prevent delivery issues in the first place as by knowing the sender address in advance, proper handling can be ensured by the admin team until the service is supported using the centralized setting, or a client might not want to use the centralized setting for whatever reason.
|
Learn Build status updates of commit 0b299c5: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 28519d8: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit b8a8fd8: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 107868e: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Closing the PR as GitHub account of the submitter not found. |
But I'm here. @jpawlowski, it exists. |
This would add a (not complete) list of sender addresses that are currently used by Microsoft services.
This list might be useful for people to know when dealing with delivery issues. It might also help to even prevent delivery issues in the first place as by knowing the sender address in advance, proper handling can be ensured by the admin team until the service is supported using the centralized setting, or a client might not want to use the centralized setting for whatever reason.