Incomplete SPF record for O365?

%3CLINGO-SUB%20id%3D%22lingo-sub-1408175%22%20slang%3D%22en-US%22%3EIncomplete%20SPF%20record%20for%20O365%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1408175%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20an%20odd%20email%20SPF%20issue.%26nbsp%3B%20I'm%20receiving%20email%20from%20an%20organisation%20with%20O365%20hosted%20mailboxes%20to%20an%20organisation%20not%20hosted%20in%20O365.%26nbsp%3B%20The%20non-O365%20organisation%20is%20correctly%20rejecting%20quite%20a%20lot%20of%20the%20O365%20organisations%20email%20due%20to%20an%20SPF%20fail.%26nbsp%3B%20The%20SPF%20record%20for%20the%20O365%20organisation%20correctly%20references%20spf.protection.outlook.com%20but%20the%20emails%20being%20rejected%20are%20coming%20from%20Microsoft%20owned%20IP%20addresses%20that%20are%20outside%20the%20range%20of%20the%20addresses%20listed%20for%26nbsp%3Bspf.protection.outlook.com.%26nbsp%3B%20The%20common%20theme%20is%20the%20SPF%20rejected%20emails%20all%20appear%20to%20be%20affecting%20O365%20mailboxes%20that%20have%20an%20auto-forward%20to%20the%20non-O365%20organisation.%26nbsp%3B%20I%20initially%20thought%20it%20was%20an%20issue%20with%20Sender%20Rewriting%20Scheme%2C%20but%20the%20fact%20remains%20that%20email%20is%20coming%20from%20a%20Microsoft%20ip%20address%20outside%20the%20range%20defined%20by%26nbsp%3Bspf.protection.outlook.com.%26nbsp%3B%20An%20example%20of%20one%20of%20the%20ip%20addresses%20that%20suffers%20the%20SPF%20fail%26nbsp%3B%20is%2040.95.64.60%20(%3CA%20href%3D%22https%3A%2F%2Fmxtoolbox.com%2FSuperTool.aspx%3Faction%3Dmx%253asoprasteria.com%26amp%3Brun%3Dtoolpage%23%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Email-vi1eur05rlyn2067.outbound.protection.outlook.com%3C%2FA%3E).%26nbsp%3B%20Other%20email%2C%20not%20autoforwarded%20but%20just%20sent%20from%20the%20O365%20organisation%2C%20is%20accepted%20as%20it%20is%20sent%20from%20MS%20ip%20addresses%20inside%20the%20range%20defined%20by%20spf.protection.outlook.com.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20what%20I%20can%20tell%2C%20this%20means%20the%20O365%20SPF%20range%20is%20not%20covering%20the%20full%20range%20of%20IP%20addresses%20that%20O365%20sends%20email%20from%2C%20which%20ought%20to%20be%20corrected%20by%20Microsoft.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20thoughts%20welcome.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%20V.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1408175%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1409401%22%20slang%3D%22en-US%22%3ERe%3A%20Incomplete%20SPF%20record%20for%20O365%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1409401%22%20slang%3D%22en-US%22%3EYou%20are%20correct%20-%20that%20is%20a%20problem!%20You%20will%20need%20to%20open%20a%20support%20case%20to%20have%20Microsoft%20fix%20that%20(this%20forum%20won't%20get%20you%20there).%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Highlighted
Visitor

I've an odd email SPF issue.  I'm receiving email from an organisation with O365 hosted mailboxes to an organisation not hosted in O365.  The non-O365 organisation is correctly rejecting quite a lot of the O365 organisations email due to an SPF fail.  The SPF record for the O365 organisation correctly references spf.protection.outlook.com but the emails being rejected are coming from Microsoft owned IP addresses that are outside the range of the addresses listed for spf.protection.outlook.com.  The common theme is the SPF rejected emails all appear to be affecting O365 mailboxes that have an auto-forward to the non-O365 organisation.  I initially thought it was an issue with Sender Rewriting Scheme, but the fact remains that email is coming from a Microsoft ip address outside the range defined by spf.protection.outlook.com.  An example of one of the ip addresses that suffers the SPF fail  is 40.95.64.60 (mail-vi1eur05rlyn2067.outbound.protection.outlook.com).  Other email, not autoforwarded but just sent from the O365 organisation, is accepted as it is sent from MS ip addresses inside the range defined by spf.protection.outlook.com.

 

From what I can tell, this means the O365 SPF range is not covering the full range of IP addresses that O365 sends email from, which ought to be corrected by Microsoft.  

 

Any thoughts welcome.

 

Regards, V.

1 Reply
Highlighted
You are correct - that is a problem! You will need to open a support case to have Microsoft fix that (this forum won't get you there).