Email Server being blocked by Outlook.com despite having compliant spf and dkim records

Question

Hello.

I am having a frustrating problem with delivering email to outlook.com accounts from one of our email servers.

The email domain in question is -- starcodesystems.net

It appears outlook.com is simply ignoring well established RFC's for DKIM and SPF compliant records, and on top of that they fail to provide an easy method of resolving the issue of rejected emails.

SPF record - pass.

DKIM record - pass

Blacklist check - 0 out of 99 known lists - pass

So, what's the problem here? I don't know. Other emails are delivered straight to the JUNK mail folder where you can leave them there or change them to 'Not Junk' status.

Please review the following linked information, and please provide me with some kind of remedy to this ongoing problem many people seem to be experiencing at this time, or at the very least...a time frame for resolving this issue.

Thanks, and regards...

Stephen.

The error code provided by outlook.com on their failure to accept is --

Error Type: SMTP
   Remote server (65.54.188.72) issued an error.
   hMailServer sent: MAIL FROM:<******@starcodesystems.net>
   Remote server replied: 550 SC-001 (BAY004-MC1F24)However, checking with senderbase.org...there is no problem.http://www.senderbase.org/lookup/?search_string=178.238.226.215Checking with Hurricane Electric Internet Services...there is no problem.http://bgp.he.net/ip/178.238.226.215#_ipinfoAnd with SPF Policy testing from vamsoft.com the result is 'PASS'http://vamsoft.com/support/tools/spf-policy-tester+2 msSPF check starting.IP: 178.238.226.215Sender: ******@starcodesystems.netDomain: starcodesystems.netEHLO/HELO domain: 192.168.88.104+0 msRetrieving DNS TXT record for "starcodesystems.net".+177 msTXT record found.Line #1: "v=spf1 mx a ip4:178.238.226.215/32 a:mail.starcodesystems.net -all"+0 msStarting SPF policy evaluation.Policy: "v=spf1 mx a ip4:178.238.226.215/32 a:mail.starcodesystems.net -all"+0 msThe policy passed syntax validation.+0 msEvaluating SPF mechanisms.+0 msEvaluating mechanism "mx".Qualifier: "pass"+0 msNo domain argument is present, using the current domain: "starcodesystems.net".+0 msRetrieving DNS MX record for "starcodesystems.net".+44 msMX record found.Answer #1: "10,mail.starcodesystems.net"+0 msRetrieving DNS A record for "mail.starcodesystems.net".+42 msA record found.Answer #1: "178.238.226.215"+0 msMatch with the IP address "178.238.226.215".+0 msThe mechanism matched with the "pass" qualifier.+0 msFinished evaluating SPF mechanisms.+0 msFinished SPF policy evaluation.+0 msPolicy evaluation finished with SPF "pass".
                
                TEST SUMMARYThe evaluation completed in 265 ms, with 0 error and 0 warning.Result: SPF passThe policy designates the argument IP as permitted sender.

Answer 1

Hello.

Thank you. I appreciate that.

The problem has been resolved.

In this case, a whois of the IP address being blocked does not resolve to my email server domain, but to Contabo VPS providers.

They are the ones who had to request the IP address be de-listed from the outlook.com blocklist.

I contacted their support services, explained the problem and within two hours they got a reply from Microsoft delisting the IP address. I am now able to send email to outlook.com with no problems whatsoever.

I live, I learn.

Thanks and regards

Stephen.

Answer 2

Stephen

This is a peer to peer site staffed mostly by volunteers who have little or no contact to MS.  We have no access to the accounts or database so all I.we can do is to point you in the right direction.

In my day job I handle these for breakfast but without access here I can do nothing.

Good luck

Answer 3

Yes, I have filled that form out already.

The point I am trying to make, is if you have met the RFC requirements for SPF and DKIM records, and they pass online third party checks, why block delivery?

Perhaps Microsoft is blocking based on 'reputation', but this online censorship and not what the internet is about.

You cannot presume everyone is guilty until proven innocent. That's an unwelcomed aberration...

Stephen.

Answer 4

Can we assume you have filled out one of  these forms?

https://support.live.com/eform.aspx?productKey=edfsmsbl3&ct=eformts&scrx=1

https://support.microsoft.com/en-us/getsupport?oaspworkflow=start_1.0.0.0&wfname=capsub&productkey=edfsmsbl3&locale=en-us&ccsid=635611717755428181&wa=wsignin1.0

https://support.microsoft.com/en-us/getsupport?oaspworkflow=start_1.0.0.0&wfname=capsub&productkey=edfsmsbl3&locale=en-us&ccsid=635806049111602712