-
Notifications
You must be signed in to change notification settings - Fork 157
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update high-risk-delivery-pool-for-outbound-messages.md
- Loading branch information
1 parent
0f308e2
commit 5bfe21c
Showing
1 changed file
with
2 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -78,3 +78,5 @@ In cases where we can authenticate the sender, we use Sender Rewriting Scheme (S | |
For DKIM to work, make sure you enable DKIM for sending domain. For example, fabrikam.com is part of contoso.com and is defined in the accepted domains of the organization. If the message sender is [email protected], DKIM needs to be enabled for fabrikam.com. you can read on how to enable at [Use DKIM to validate outbound email sent from your custom domain](use-dkim-to-validate-outbound-email.md). | ||
|
||
To add a custom domains follow the steps in [Add a domain to Microsoft 365](../../admin/setup/add-domain.md). | ||
|
||
If MX record for your domain is pointed to a 3rd party or on-premises server, you should utilize Enhanced Filtering to ensure the SPF validation is correct for inbound email to avoid sending email through relay pool. |