在 EOP 中创建安全发件人列表Create safe sender lists in EOP


改进的 Microsoft 365 安全中心现在可用。The improved Microsoft 365 security center is now available. 此新体验将 Defender for Endpoint、Defender for Office、365 Microsoft 365 Defender 等引入了 Microsoft 365 安全中心。This new experience brings Defender for Endpoint, Defender for Office 365, Microsoft 365 Defender, and more into the Microsoft 365 security center. 了解新增功能Learn what's new.

适用对象Applies to

如果你是在 Exchange Online 中拥有邮箱的 Microsoft 365 客户,或者没有 Exchange Online 邮箱的独立 Exchange Online Protection (EOP) 客户,EOP 提供了多种方式确保用户将接收来自受信任发件人的电子邮件。If you're a Microsoft 365 customer with mailboxes in Exchange Online or a standalone Exchange Online Protection (EOP) customer without Exchange Online mailboxes, EOP offers multiple ways of ensuring that users will receive email from trusted senders. 这些选项包括 Exchange 邮件流规则 (也称为传输规则) 、Outlook 安全发件人、IP 允许列表 (连接筛选) 以及反垃圾邮件策略中允许的发件人列表或允许的域列表。These options include Exchange mail flow rules (also known as transport rules), Outlook Safe Senders, the IP Allow List (connection filtering), and allowed sender lists or allowed domain lists in anti-spam policies. 您一起可以将这些选项视为安全 发件人列表Collectively, you can think of these options as safe sender lists.

以下列表中介绍了可用安全发件人列表,从最推荐到最不推荐的顺序:The available safe sender lists are described in the following list in order from most recommended to least recommended:

  1. 邮件流规则Mail flow rules
  2. Outlook 安全发件人Outlook Safe Senders
  3. IP 允许列表 (连接筛选) IP Allow List (connection filtering)
  4. 允许发件人列表或允许的域 (反垃圾邮件策略) Allowed sender lists or allowed domain lists (anti-spam policies)

邮件流规则允许最灵活地确保仅允许正确的邮件。Mail flow rules allow the most flexibility to ensure that only the right messages are allowed. 反垃圾邮件策略中允许的发件人和允许的域列表没有 IP 允许列表安全,因为发件人的电子邮件域很容易被欺骗。Allowed sender and allowed domain lists in anti-spam policies aren't as secure as the IP Allow List, because the sender's email domain is easily spoofed. 但是,IP 允许列表也带来风险,因为从该 IP地址发送的任何域的电子邮件将绕过垃圾邮件筛选。But, the IP Allow List also presents a risk, because email from any domain that's sent from that IP address will bypass spam filtering.


  • 请务必密切监视 使用 安全发件人列表对垃圾邮件筛选做出的任何例外。Be careful to closely monitor any exceptions that you make to spam filtering using safe sender lists.

  • 虽然您可以使用安全发件人列表帮助处理误报 (标记为错误) ,但您应考虑将安全发件人列表用作临时解决方案,如果可能,应避免使用安全发件人列表。While you can use safe sender lists to help with false positives (good email marked as bad), you should consider the use of safe sender lists as a temporary solution that should be avoided if possible. 我们不建议使用安全发件人列表管理误报,因为垃圾邮件筛选的例外可能会让组织遭受欺骗和其他攻击。We don't recommend managing false positives by using safe sender lists, because exceptions to spam filtering can open your organization to spoofing and other attacks. 如果您坚持使用安全发件人列表来管理误报,则需要保持谨慎,并随时向 Microsoft 报告邮件和文件主题。If you insist on using safe sender lists to manage false positives, you need to be vigilant and keep the topic Report messages and files to Microsoft at the ready.

  • 若要允许域发送未经身份验证的电子邮件 (绕过反欺骗保护) 但不绕过反垃圾邮件和反恶意软件检查,可以将其添加到 AllowedToSpoof 安全发件人列表中To allow a domain to send unauthenticated email (bypass anti-spoofing protection) but not bypass anti-spam and anti-malware checks, you can add it to the AllowedToSpoof safe sender list

  • EOP 和 Outlook 检查不同的邮件属性以确定邮件的发件人。EOP and Outlook inspect different message properties to determine the sender of the message. 有关详细信息,请参阅本文稍后 介绍的 批量电子邮件的注意事项部分。For more information, see the Considerations for bulk email section later in this article.

相比之下,您还可以使用阻止的发件人列表来阻止来自 特定来源的电子邮件In contrast, you also have several options to block email from specific sources using blocked sender lists. 有关详细信息,请参阅在 EOP 中创建阻止发件人列表For more information, see Create block sender lists in EOP.

Exchange Online 和独立 EOP 中的邮件流规则使用条件和例外来标识邮件,以及指定应针对这些邮件执行哪些操作的操作。Mail flow rules in Exchange Online and standalone EOP use conditions and exceptions to identify messages, and actions to specify what should be done to those messages. 有关详细信息,请参阅 Mail flow rules (transport rules) in Exchange OnlineFor more information, see Mail flow rules (transport rules) in Exchange Online.

以下示例假定您需要来自以下组织的电子邮件 contoso.com 跳过垃圾邮件筛选。The following example assumes you need email from contoso.com to skip spam filtering. 为此,请配置以下设置:To do this, configure the following settings:

  1. 条件****:发件人 > > contoso.com。Condition: The sender > domain is > contoso.com.

  2. 配置以下任一设置:Configure either of the following settings:

    • 邮件流规则条件****:邮件头 包含以下任何词语: > > 邮件头 名称: Authentication-Results > 邮件头值dmarc=passdmarc=bestguesspassMail flow rule condition: A message header > includes any of these words > Header name: Authentication-Results > Header value: dmarc=pass or dmarc=bestguesspass.

      此条件会检查发送电子邮件域的电子邮件身份验证状态,以确保发送域未遭到欺骗。This condition checks the email authentication status of the sending email domain to ensure that the sending domain is not being spoofed. 有关电子邮件身份验证详细信息,请参阅SPF、DKIMDMARC。 For more information about email authentication, see SPF, DKIM, and DMARC.

    • IP 允许列表:在连接筛选器策略中指定源 IP 地址或地址范围。IP Allow List: Specify the source IP address or address range in the connection filter policy.

      如果发送域不使用电子邮件身份验证,则使用此设置。Use this setting if the sending domain does not use email authentication. 当涉及 IP 允许列表中的源 IP 地址时,请尽可能严格。Be as restrictive as possible when it comes to the source IP addresses in the IP Allow List. 我们建议 IP 地址范围小于或小于 /24 (是更好的) 。We recommend an IP address range of /24 or less (less is better). 请勿使用属于使用者服务的 IP 地址 (例如,outlook.com) 共享基础结构。Do not use IP address ranges that belong to consumer services (for example, outlook.com) or shared infrastructures.


    • 切勿将仅发件人 域配置为 跳过垃圾邮件筛选的条件来配置邮件流规则。Never configure mail flow rules with only the sender domain as the condition to skip spam filtering. 这样做将显著增加攻击者欺骗发送域 (或模拟完整电子邮件地址) 、跳过所有垃圾邮件筛选并跳过发件人身份验证检查以便邮件到达收件人收件箱的可能性。Doing so will significantly increase the likelihood that attackers can spoof the sending domain (or impersonate the full email address), skip all spam filtering, and skip sender authentication checks so the message will arrive in the recipient's Inbox.

    • 不要将你拥有 (的域) 或热门 (,例如 microsoft.com) 规则中的条件。Do not use domains you own (also known as accepted domains) or popular domains (for example, microsoft.com) as conditions in mail flow rules. 这样做被视为高风险,因为它会为攻击者创造机会来发送电子邮件,否则会进行筛选。Doing so is considered high risk because it creates opportunities for attackers to send email that would otherwise be filtered.

    • 如果允许网络地址转换 (NAT) 网关后面的 IP 地址,则需要知道 NAT 池中涉及的服务器,才能知道 IP 允许列表的范围。If you allow an IP address that's behind a network address translation (NAT) gateway, you need to know the servers that are involved in the NAT pool in order to know the scope of your IP Allow List. IP 地址和 NAT 参与者可以更改。IP addresses and NAT participants can change. 作为标准维护程序的一部分,您需要定期检查 IP 允许列表条目。You need to periodically check your IP Allow List entries as part of your standard maintenance procedures.

  3. 可选条件Optional conditions:

    • 发件人 >是内部/外部 >组织外部:此条件是隐式的,但可以使用它来说明可能无法正确配置本地电子邮件服务器。The sender > is internal/external > Outside the organization: This condition is implicit, but it's OK to use it to account for on-premises email servers that might not be correctly configured.

    • 主题或正文 >subject 或 body 包含以下任何词语 >:如果可以通过主题行或邮件正文中的关键字或短语进一步限制邮件,可以使用这些词 <keywords> 作为条件。The subject or body > subject or body includes any of these words > <keywords>: If you can further restrict the messages by keywords or phrases in the subject line or message body, you can use those words as a condition.

  4. 操作:在规则中配置这两项操作:Action: Configure both of these actions in the rule:

    a.a. 修改邮件属性 >将垃圾邮件可信度设置为 (SCL) >绕过垃圾邮件筛选Modify the message properties > set the spam confidence level (SCL) > Bypass spam filtering.

    b.b. 修改邮件属性 >设置邮件头****:将邮件头 <CustomHeaderName> 设置为值 <CustomHeaderValue> 。Modify the message properties > set a message header: Set the message header <CustomHeaderName> to the value <CustomHeaderValue>.

    例如,X-ETR: Bypass spam filtering for authenticated sender 'contoso.com'For example, X-ETR: Bypass spam filtering for authenticated sender 'contoso.com'. 如果规则中具有多个域,可以根据需要自定义标头文本。If you have more than one domain in the rule, you can customize the header text as appropriate.

    当邮件由于邮件流规则而跳过垃圾邮件筛选时,值值将标记在 SFV:SKN X-Forefront-Antispam-Report 标头中。When a message skips spam filtering due to a mail flow rule, the value SFV:SKN value is stamped in the X-Forefront-Antispam-Report header. 如果邮件来自 IP 允许列表上的源,则也会 IPV:CAL 添加值。If the message is from a source that's on the IP Allow List, the value IPV:CAL is also added. 这些值可以帮助你进行疑难解答。These values can help you with troubleshooting.

EAC 中用于绕过垃圾邮件筛选的邮件流规则设置。

使用 Outlook 安全发件人Use Outlook Safe Senders


此方法会为攻击者将电子邮件成功发送到收件箱带来高风险,否则会进行筛选;但是,用户的安全发件人列表或安全域列表不会阻止筛选恶意软件或高可信度网络钓鱼邮件。This method creates a high risk of attackers successfully delivering email to the Inbox that would otherwise be filtered; however, the user's Safe Senders or Safe Domains lists don't prevent malware or high confidence phishing messages from being filtered.

用户或管理员可以将发件人电子邮件地址添加到邮箱中的"安全发件人"列表中,而不是组织设置。Instead of an organizational setting, users or admins can add the sender email addresses to the Safe Senders list in the mailbox. 有关说明,请参阅 在 Office 365 中配置 Exchange Online邮箱上的垃圾邮件设置。For instructions, see Configure junk email settings on Exchange Online mailboxes in Office 365. 在大多数情况下,这是不可取的,因为发件人将绕过筛选堆栈的某些部分。This is not desirable in most situations since senders will bypass parts of the filtering stack. 尽管您信任发件人,但发件人仍然可能会遭到入侵并发送恶意内容。Although you trust the sender, the sender can still be compromised and send malicious content. 最好让筛选器执行检查每封邮件所需的操作,然后在筛选器出错时向 Microsoft 报告误报 / 负数。It is best that you let our filters do what is needed to check every message and then report the false positive/negative to Microsoft if our filters got it wrong. 绕过筛选堆栈也会干扰 ZAPBypassing the filtering stack also interferes with ZAP.

当邮件由于用户的安全发件人列表而跳过垃圾邮件筛选时 ,X-Forefront-Antispam-Report 头字段将包含值 ,该值指示已绕过对垃圾邮件、欺骗和网络钓鱼的 SFV:SFE 筛选。When messages skip spam filtering due to a user's Safe Senders list, the X-Forefront-Antispam-Report header field will contain the value SFV:SFE, which indicates that filtering for spam, spoof, and phishing were bypassed.

使用 IP 允许列表Use the IP Allow List

如果您无法按前面所述使用邮件流规则,则下一个最佳选项是向连接筛选器策略中的 IP 允许列表添加源电子邮件服务器。If you can't use mail flow rules as previously described, the next best option is to add the source email server or servers to the IP Allow List in the connection filter policy. 有关详细信息,请参阅在 EOP 中配置连接筛选For details, see Configure connection filtering in EOP.


  • 将允许的 IP 地址数保持在最少,这一点很重要,因此尽可能避免使用整个 IP 地址范围。It's important that you keep the number of allowed IP addresses to a minimum, so avoid using entire IP address ranges whenever possible.

  • 请勿使用属于使用者服务的 IP 地址 (例如,outlook.com) 共享基础结构。Do not use IP address ranges that belong to consumer services (for example, outlook.com) or shared infrastructures.

  • 定期查看 IP 允许列表中的条目并删除不再需要的条目。Regularly review the entries in the IP Allow List and remove the entries that you no longer need.


如果不进行其他验证(如邮件流规则),来自 IP 允许列表中的源的电子邮件将跳过 SPF、DKIM、DMARC (垃圾邮件筛选和发件人身份验证) 检查。Without additional verification like mail flow rules, email from sources in the IP Allow List skips spam filtering and sender authentication (SPF, DKIM, DMARC) checks. 这将为攻击者将电子邮件成功发送到收件箱带来高风险,否则会进行筛选;但是,IP 允许列表不会阻止对恶意软件或高可信度网络钓鱼邮件进行筛选。This creates a high risk of attackers successfully delivering email to the Inbox that would otherwise be filtered; however, the IP Allow List doesn't prevent malware or high confidence phishing messages from being filtered.

使用允许的发件人列表或允许的域列表Use allowed sender lists or allowed domain lists

最不可取的选项是在反垃圾邮件策略中使用允许的发件人列表或允许的域列表。The least desirable option is to use the allowed sender list or allowed domain list in anti-spam policies. 如果可能,应避免使用此选项,因为发件人会绕过所有垃圾邮件、欺骗和网络钓鱼防护,并且使用 SPF、DKIM、DMARC (身份验证) 。You should avoid this option if at all possible because senders bypass all spam, spoof, and phishing protection, and sender authentication (SPF, DKIM, DMARC). 此方法最好仅用于临时测试。This method is best used for temporary testing only. 可以在在 EOP 中 配置反垃圾邮件策略主题中找到详细 步骤。The detailed steps can be found in Configure anti-spam policies in EOP topic.

这些列表的最大限制为大约 1000 个条目;但是,你只能向门户输入 30 个条目。The maximum limit for these lists is approximately 1000 entries; although, you will only be able to enter 30 entries into the portal. 必须使用 PowerShell 添加 30 多个条目。You must use PowerShell to add more than 30 entries.


  • 此方法会为攻击者将电子邮件成功发送到收件箱带来高风险,否则会进行筛选;但是,允许的发件人或允许的域列表不会阻止恶意软件或高可信度网络钓鱼邮件被筛选。This method creates a high risk of attackers successfully delivering email to the Inbox that would otherwise be filtered; however, the allowed senders or allowed domains lists don't prevent malware or high confidence phishing messages from being filtered.

  • 请勿使用你拥有 (的域,) 或热门 (,例如,microsoft.com) 允许的域列表中。Do not use domains you own (also known as accepted domains) or popular domains (for example, microsoft.com) in allowed domain lists.

批量电子邮件的注意事项Considerations for bulk email

标准 SMTP 电子邮件由 邮件信封 和邮件内容组成。A standard SMTP email message consists of a message envelope and message content. 邮件信封包含在 SMTP 服务器之间传输和传递邮件所需的信息。The message envelope contains information that's required for transmitting and delivering the message between SMTP servers. 邮件内容包含邮件头字段(统称为 邮件头)和邮件正文。The message content contains message header fields (collectively called the message header) and the message body. RFC 5321 中介绍了邮件信封,RFC 5322 中介绍了邮件头。The message envelope is described in RFC 5321, and the message header is described in RFC 5322. 收件人永远不会看到实际的邮件信封,因为它是由邮件传输过程生成的,实际上并不是邮件的一部分。Recipients never see the actual message envelope because it's generated by the message transmission process, and it isn't actually part of the message.

  • 地址 5321.MailFrom (MAIL FROM 地址、P1 发件人或信封发件人) 是在邮件的 SMTP 传输中使用的电子邮件地址。The 5321.MailFrom address (also known as the MAIL FROM address, P1 sender, or envelope sender) is the email address that's used in the SMTP transmission of the message. 虽然发件人可以指定不同的"返回路径"电子邮件地址 (但此电子邮件地址通常记录在邮件头的"返回路径") 。 This email address is typically recorded in the Return-Path header field in the message header (although it's possible for the sender to designate a different Return-Path email address). 如果邮件无法传递,则它是未送达报告的收件人 (NDR 或退回邮件) 。If the message can't be delivered, it's the recipient for the non-delivery report (also known as an NDR or bounce message).

  • The 5322.From (also known as the From address or P2 sender) is the email address in the From header field, and is the sender's email address that's displayed in email clients.The 5322.From (also known as the From address or P2 sender) is the email address in the From header field, and is the sender's email address that's displayed in email clients.

通常, 5321.MailFrom5322.From 地址在个人 (通信中) 。Frequently, the 5321.MailFrom and 5322.From addresses are the same (person-to-person communication). 但是,代表其他人发送电子邮件时,地址可以不同。However, when email is sent on behalf of someone else, the addresses can be different. 这通常发生在批量电子邮件中。This happens most often for bulk email messages.

例如,假设 Blue Yonder Airlines 已雇用 Margie's Travel 发送其电子邮件广告。For example, suppose that Blue Yonder Airlines has hired Margie's Travel to send out its email advertising. 在收件箱中收到的邮件具有以下属性:The message you receive in your Inbox has the following properties:

  • 地址 5321.MailFrom 为 blueyonder.airlines@margiestravel.com。The 5321.MailFrom address is blueyonder.airlines@margiestravel.com.

  • 5322.From 地址 blueyonder@news.blueyonderairlines.com,你将在 Outlook 中看到该地址。The 5322.From address is blueyonder@news.blueyonderairlines.com, which is what you'll see in Outlook.

EOP 中的反垃圾邮件策略中的安全发件人列表和安全域列表仅检查地址,这类似于使用该地址的 5322.From Outlook 安全 5322.From 发件人。Safe sender lists and safe domain lists in anti-spam policies in EOP inspect only the 5322.From addresses, this is similar to Outlook Safe Senders that uses the 5322.From address.

若要阻止筛选此邮件,可以执行以下步骤:To prevent this message from being filtered, you can take the following steps:

  • 添加 blueyonder@news.blueyonderairlines.com (Outlook 5322.From) 发件人的地址。Add blueyonder@news.blueyonderairlines.com (the 5322.From address) as an Outlook Safe Sender.

  • 将邮件流规则 与以下条件一同使用:查找 blueyonder@news.blueyonderairlines.com (、blueyonder.airlines@margiestravel.com (或) 5322.From 5321.MailFrom 的邮件。Use a mail flow rule with a condition that looks for messages from blueyonder@news.blueyonderairlines.com (the 5322.From address, blueyonder.airlines@margiestravel.com (the 5321.MailFrom), or both.

有关详细信息,请参阅在 EOP 中创建安全发件人列表For more information, see Create safe sender lists in EOP.