Skip to content

Commit 0ce02d3

Browse files
authored
Merge branch 'public' into patch-1
2 parents 7ee95e6 + 099a827 commit 0ce02d3

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

defender-office-365/outbound-spam-high-risk-delivery-pool-about.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -72,8 +72,6 @@ The forwarded or relayed message should meet one of the following criteria to av
7272
- SPF passes when the message comes to Microsoft 365.
7373
- DKIM on the sender domain passes when the message comes to Microsoft 365.
7474

75-
You can tell that a message was sent via the relay pool by looking at the outbound server IP (the relay pool is in the 40.95.0.0/16 range).
76-
7775
In cases where we can authenticate the sender, we use Sender Rewriting Scheme (SRS) to help the recipient email system know that the forwarded message is from a trusted source. You can read more about how that works and what you can do to help make sure the sending domain passes authentication in [Sender Rewriting Scheme (SRS) in Office 365](/office365/troubleshoot/antispam/sender-rewriting-scheme).
7876

7977
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](email-authentication-dkim-configure.md).

0 commit comments

Comments
 (0)