![]() X-Forefront-Antispam-Repor t: CIP:23.1.4.9 CTRY:HK IPV:C AL IPV:NLI EFV:NLI S FV:SPM ![]() Smtp.mailfrom= m om ĭkim=none (message not signed) header.d=none Received-SPF: Fail (: domain of does notĭesignate 23.1.4.9 as permitted sender) receiver=protection.outloo k.com Ĭlient-ip=23.1.4.9 helo=ntoso. Email from to Īuthentication-Results: spf=fail (sender IP is 23.1.4.9) Note: 23.1.4.9 is the public IP address of the on-premise hybrid Exchange 2010 server connector to Exchange Online.Ĭase 1. On-premises mailboxes do not have this problem only mailboxes migrated to Office 365.Īn illustration of the problem with mail flow and details: The problem is when external users sends emails to an Office 365 mailbox in the organization (mail flow: External -> Mail Gateway -> on-premise mail servers -> EOP -> Office 365), EOP performs an SPF lookup and hard/soft failing messages with the external facing IP address of the Mail Gateway from which it received the mail. MX records are pointing at the on-premises as we haven't completed migrating all mailboxes from on-premise to Exchange Online.
0 Comments
Leave a Reply. |