Received-SPF: TempError (protection.outlook.com: error in processing during lookup of "domain-name":

%3CLINGO-SUB%20id%3D%22lingo-sub-1801696%22%20slang%3D%22en-US%22%3EReceived-SPF%3A%20TempError%20(protection.outlook.com%3A%20error%20in%20processing%20during%20lookup%20of%20%22domain-name%22%3A%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1801696%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22%22%3EI%20have%20encountered%20an%20issue%20I%20believe%20is%20extremely%20widespread%20(albeit%20intermittent)%20affecting%20deliverability%20to%20hotmail.com%20%2F%20outlook.com%20from%20.AU%20Domains.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDuring%20the%20past%20few%20days%2C%20I%20have%20performed%20extensive%20testing%20to%20validate%20the%20issue%20which%20initially%20I%20thought%20was%20isolated%20to%20a%20single%20one%20of%20our%20.com.au%20domains.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20since%20managed%20to%20replicate%20the%20issue%20across%20%26gt%3B5%20different%20domains%20ending%20in%20.au%20such%20as%20.com.au%2C%20.net.au%2C%20and%20.edu.au.%20I%20have%20tested%20this%20across%20multiple%20Mail%20platforms%20such%20as%20Amazon%20accounts%20(SES)%2C%20G%20Suite%20for%20business%20web%20interface%2C%20an%20internal%20SMTP%20relay%20which%20outbounds%20via%20Proofpoint%20and%20also%20from%20an%20O365%20tenant.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tested%20a%20single%20email%20with%20multiple%20recipients%20to%20platforms%20such%20as%20Gmail%2C%20Yahoo%20and%20Hotmail%20in%20which%20Hotmail%20is%20the%20only%20recipient%20which%20reports%20an%20SPF%20TempError%2C%20DNS%20Timeout.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20posted%20a%20portion%20of%20the%20email%20headers%20received%20in%20hotmail%2C%20being%20sent%20via%20multiple%20platforms%2C%20servers%2C%20subnets%20which%20have%20all%20failed.%20I%20have%20obfuscated%20the%20domain%20name%20for%20privacy%20reasons.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20a%20huge%20issue%2C%20not%20only%20for%20us%2C%20but%20for%20anyone%20sending%20mail%20to%20Hotmail%20from%20an%20.AU%20domain.%20I%20have%20not%20been%20able%20to%20make%20any%20other%20TLD%20fail%20as%20of%20yet.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20does%20one%20make%20Microsoft%20aware%20of%20a%20fairly%20significant%20and%20widespread%20issue%20affecting%20multiple%20end%20users%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHaving%20spoken%20with%20AWS%20regarding%20this%20issue%20(I%20initially%20thought%20the%20issue%20was%20isolated%20to%20domains%20hosted%20in%20Route53%2C%20they%20concur%20that%20the%20issue%20lies%20solely%20with%20the%20receiving%20mail%20platform%20being%20hotmail.com%2Foutlook.live.com)%20At%20a%20guess%20I%20would%20say%20Microsoft%20is%20intermittently%20having%20an%20issue%20performing%20DNS%20lookups%20of%20TLD's%20ending%20in%20.AU%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAuthentication-Results%3A%20spf%3Dtemperror%20(sender%20IP%20is%20180.189.28.115)%20smtp.mailfrom%3Ddomainname%3B%20hotmail.com%3B%20dkim%3Dpass%20(signature%20was%20verified)%20header.d%3D%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%3E%3Bhotmail.com%3B%20dmarc%3Dpass%20action%3Dnone%20header.from%3D%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%3E%3Bcompauth%3Dpass%20reason%3D100%20Received-SPF%3A%20TempError%20(protection.outlook.com%3A%20error%20in%20processing%20during%20lookup%20of%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%20DNS%20Timeout)%20Received%3A%20from%20au-smtp-delivery-115.mimecast.com%20(180.189.28.115)%20by%20BN3NAM01FT032.mail.protection.outlook.com%20(10.152.67.233)%20with%20Microsoft%20SMTP%20Server%20(version%3DTLS1_2%2C%20cipher%3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)%20id%2015.20.3477.23%20via%20Frontend%20Transport%3B%20Thu%2C%2015%20Oct%202020%2007%3A07%3A36%20%2B0000%20X-IncomingTopHeaderMarker%3A%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAuthentication-Results%3A%20spf%3Dtemperror%20(sender%20IP%20is%2023.251.230.203)%20smtp.mailfrom%3Ddomainname%3B%20hotmail.com%3B%20dkim%3Dpass%20(signature%20was%20verified)%20header.d%3D%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%3E%3Bhotmail.com%3B%20dmarc%3Dpass%20action%3Dnone%20header.from%3D%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%20class%3D%22%22%3E%3Bcompauth%3Dpass%20reason%3D100%20Received-SPF%3A%20TempError%20(protection.outlook.com%3A%20error%20in%20processing%20during%20lookup%20of%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%20DNS%20Timeout)%20Received%3A%20from%20e230-203.smtp-out.amazonses.com%20(23.251.230.203)%20by%20DM6NAM12FT050.mail.protection.outlook.com%20(10.13.178.215)%20with%20Microsoft%20SMTP%20Server%20(version%3DTLS1_2%2C%20cipher%3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384)%20id%2015.20.3499.7%20via%20Frontend%20Transport%3B%20Thu%2C%2015%20Oct%202020%2006%3A43%3A30%20%2B0000%20X-IncomingTopHeaderMarker%3A%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAuthentication-Results%3A%20spf%3Dtemperror%20(sender%20IP%20is%2069.169.232.10)%20smtp.mailfrom%3Ddomainname%3B%20hotmail.com%3B%20dkim%3Dpass%20(signature%20was%20verified)%20header.d%3D%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%3E%3Bhotmail.com%3B%20dmarc%3Dtemperror%20action%3Dnone%20header.from%3D%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%3E%3B%20Received-SPF%3A%20TempError%20(protection.outlook.com%3A%20error%20in%20processing%20during%20lookup%20of%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%20DNS%20Timeout)%20Received%3A%20from%20b232-10.smtp-out.ap-southeast-2.amazonses.com%20(69.169.232.10)%20by%20VI1EUR06FT050.mail.protection.outlook.com%20(10.13.7.32)%20with%20Microsoft%20SMTP%20Server%20(version%3DTLS1_2%2C%20cipher%3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384)%20id%2015.20.3477.21%20via%20Frontend%20Transport%3B%20Wed%2C%2014%20Oct%202020%2002%3A10%3A39%20%2B0000%20X-IncomingTopHeaderMarker%3A%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAuthentication-Results%3A%20spf%3Dtemperror%20(sender%20IP%20is%20148.163.148.88)%20smtp.mailfrom%3Ddomainname%3B%20hotmail.com%3B%20dkim%3Dpass%20(signature%20was%20verified)%20header.d%3D%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%3E%3Bhotmail.com%3B%20dmarc%3Dbestguesspass%20action%3Dnone%20header.from%3D%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%3E%3Bcompauth%3Dpass%20reason%3D109%20Received-SPF%3A%20TempError%20(protection.outlook.com%3A%20error%20in%20processing%20during%20lookup%20of%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%20DNS%20Timeout)%20Received%3A%20from%20mx0a-0020df01.pphosted.com%20(148.163.148.88)%20by%20VI1EUR06FT044.mail.protection.outlook.com%20(10.13.6.117)%20with%20Microsoft%20SMTP%20Server%20(version%3DTLS1_2%2C%20cipher%3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)%20id%2015.20.3455.23%20via%20Frontend%20Transport%3B%20Fri%2C%209%20Oct%202020%2000%3A54%3A44%20%2B0000%20X-IncomingTopHeaderMarker%3A%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAuthentication-Results%3A%20spf%3Dtemperror%20(sender%20IP%20is%20209.85.166.48)%20smtp.mailfrom%3Ddomainname%3B%20hotmail.com%3B%20dkim%3Dtimeout%20(key%20query%20timeout)%20header.d%3D%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%3E%3Bhotmail.com%3B%20dmarc%3Dtemperror%20action%3Dnone%20header.from%3D%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%3E%3B%20Received-SPF%3A%20TempError%20(protection.outlook.com%3A%20error%20in%20processing%20during%20lookup%20of%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Edomainname%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%20DNS%20Timeout)%20Received%3A%20from%20mail-io1-f48.google.com%20(209.85.166.48)%20by%20BN7NAM10FT037.mail.protection.outlook.com%20(10.13.157.9)%20with%20Microsoft%20SMTP%20Server%20(version%3DTLS1_2%2C%20cipher%3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)%20id%2015.20.3455.25%20via%20Frontend%20Transport%3B%20Fri%2C%209%20Oct%202020%2001%3A01%3A58%20%2B0000%20X-IncomingTopHeaderMarker%3A%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20or%20insight%20here%20would%20be%20much%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1810709%22%20slang%3D%22en-US%22%3ERe%3A%20Received-SPF%3A%20TempError%20(protection.outlook.com%3A%20error%20in%20processing%20during%20lookup%20of%20%22doma%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1810709%22%20slang%3D%22en-US%22%3ESame%20problem%20here%2C%20RECIEVED-SPF%20DNS%20TIMEOUT%20for%20my%20domain%20any%20ideas%3F%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1810716%22%20slang%3D%22en-US%22%3ERe%3A%20Received-SPF%3A%20TempError%20(protection.outlook.com%3A%20error%20in%20processing%20during%20lookup%20of%20%22doma%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1810716%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F842994%22%20target%3D%22_blank%22%3E%40SaadI635%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20the%20testing%20I%20have%20done%2C%20this%20issue%20appears%20to%20lie%20on%20the%20Outlook.com%2FHotmail%20side.%20%26nbsp%3BThis%20can%20only%20be%20fixed%20by%20Microsoft.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20I%20mentioned%20in%20my%20initial%20post%2C%20I%20am%20able%20to%20send%20a%20single%20email%20with%20multiple%20recipients%20and%20the%20email%20will%20only%20fail%20SPF%20arriving%20at%20Outlook.com%2FHotmail%20due%20to%20a%20DNS%20Timeout.%20This%20would%20suggest%20the%20issue%20lies%20with%20how%20Microsoft%20are%20processing%20the%20message.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHopefully%20someone%20will%20take%20notice%20of%20this%20thread%20soon%20and%20investigate.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I have encountered an issue I believe is extremely widespread (albeit intermittent) affecting deliverability to hotmail.com / outlook.com from .AU Domains.

 

During the past few days, I have performed extensive testing to validate the issue which initially I thought was isolated to a single one of our .com.au domains.

 

I have since managed to replicate the issue across >5 different domains ending in .au such as .com.au, .net.au, and .edu.au. I have tested this across multiple Mail platforms such as Amazon accounts (SES), G Suite for business web interface, an internal SMTP relay which outbounds via Proofpoint and also from an O365 tenant.

 

I have tested a single email with multiple recipients to platforms such as Gmail, Yahoo and Hotmail in which Hotmail is the only recipient which reports an SPF TempError, DNS Timeout.

 

I have posted a portion of the email headers received in hotmail, being sent via multiple platforms, servers, subnets which have all failed. I have obfuscated the domain name for privacy reasons. 

 

This is a huge issue, not only for us, but for anyone sending mail to Hotmail from an .AU domain. I have not been able to make any other TLD fail as of yet.

 

How does one make Microsoft aware of a fairly significant and widespread issue affecting multiple end users?

 

Having spoken with AWS regarding this issue (I initially thought the issue was isolated to domains hosted in Route53, they concur that the issue lies solely with the receiving mail platform being hotmail.com/outlook.live.com) At a guess I would say Microsoft is intermittently having an issue performing DNS lookups of TLD's ending in .AU

 

Authentication-Results: spf=temperror (sender IP is 180.189.28.115) smtp.mailfrom=domainname; hotmail.com; dkim=pass (signature was verified) header.d=domainname;hotmail.com; dmarc=pass action=none header.from=domainname;compauth=pass reason=100 Received-SPF: TempError (protection.outlook.com: error in processing during lookup of domainname  DNS Timeout) Received: from au-smtp-delivery-115.mimecast.com (180.189.28.115) by BN3NAM01FT032.mail.protection.outlook.com (10.152.67.233) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.23 via Frontend Transport; Thu, 15 Oct 2020 07:07:36 +0000 X-IncomingTopHeaderMarker: 

 

Authentication-Results: spf=temperror (sender IP is 23.251.230.203) smtp.mailfrom=domainname; hotmail.com; dkim=pass (signature was verified) header.d=domainname;hotmail.com; dmarc=pass action=none header.from=domainname;compauth=pass reason=100 Received-SPF: TempError (protection.outlook.com: error in processing during lookup of domainname  DNS Timeout) Received: from e230-203.smtp-out.amazonses.com (23.251.230.203) by DM6NAM12FT050.mail.protection.outlook.com (10.13.178.215) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.3499.7 via Frontend Transport; Thu, 15 Oct 2020 06:43:30 +0000 X-IncomingTopHeaderMarker: 

 

Authentication-Results: spf=temperror (sender IP is 69.169.232.10) smtp.mailfrom=domainname; hotmail.com; dkim=pass (signature was verified) header.d=domainname;hotmail.com; dmarc=temperror action=none header.from=domainname; Received-SPF: TempError (protection.outlook.com: error in processing during lookup of domainname  DNS Timeout) Received: from b232-10.smtp-out.ap-southeast-2.amazonses.com (69.169.232.10) by VI1EUR06FT050.mail.protection.outlook.com (10.13.7.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.3477.21 via Frontend Transport; Wed, 14 Oct 2020 02:10:39 +0000 X-IncomingTopHeaderMarker: 

 

Authentication-Results: spf=temperror (sender IP is 148.163.148.88) smtp.mailfrom=domainname; hotmail.com; dkim=pass (signature was verified) header.d=domainname;hotmail.com; dmarc=bestguesspass action=none header.from=domainname;compauth=pass reason=109 Received-SPF: TempError (protection.outlook.com: error in processing during lookup of domainname  DNS Timeout) Received: from mx0a-0020df01.pphosted.com (148.163.148.88) by VI1EUR06FT044.mail.protection.outlook.com (10.13.6.117) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.23 via Frontend Transport; Fri, 9 Oct 2020 00:54:44 +0000 X-IncomingTopHeaderMarker: 

 

Authentication-Results: spf=temperror (sender IP is 209.85.166.48) smtp.mailfrom=domainname; hotmail.com; dkim=timeout (key query timeout) header.d=domainname;hotmail.com; dmarc=temperror action=none header.from=domainname; Received-SPF: TempError (protection.outlook.com: error in processing during lookup of domainname  DNS Timeout) Received: from mail-io1-f48.google.com (209.85.166.48) by BN7NAM10FT037.mail.protection.outlook.com (10.13.157.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.25 via Frontend Transport; Fri, 9 Oct 2020 01:01:58 +0000 X-IncomingTopHeaderMarker: 

 

Any help or insight here would be much appreciated.

5 Replies
Same problem here, RECIEVED-SPF DNS TIMEOUT for my domain any ideas??

Hi @SaadItani,

 

From the testing I have done, this issue appears to lie on the Outlook.com/Hotmail side.  This can only be fixed by Microsoft.

 

As I mentioned in my initial post, I am able to send a single email with multiple recipients and the email will only fail SPF arriving at Outlook.com/Hotmail due to a DNS Timeout. This would suggest the issue lies with how Microsoft are processing the message.

 

Hopefully someone will take notice of this thread soon and investigate. 

Are you perhaps able to tell me which TLD you are sending from ? Is it a .AU, COM.AU, .NET.AU or something else? @SaadItani 

@niaccarino1981 

Your not the only one who has this problem.
I use a .com domain,  with a german mail server and having the same problem.
This fix (https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_exchon-mso_o365b/spf-tempe...) is not working for me

Seems like a microsoft problem, but as always, they don't give a damm about small companies outside of the US. They only care about themselfs.

.edu.lb Aslo I want to note that its happening at random times and not for every email. Its been months happening and I contacted TLD NS servers for support and yet no fix.

Also we know that emails getting spf fails are entiteled with email subject: [Warning Unauthenticted User] and again it happens at random times and our end users are getting frustrated... 
we contacted Microsoft support and they said its from DNS side.