I have a domain for example https://example.com website setup on a DO VPS. I have configured the VPS to be the primary MX for the domain and configure what I believe is an appropriate SPF record for it. The VPS is running postfix and can send and receive email for the domain. I can receive email fine to multiple other domains.
I also note that a similar question has been asked before but the work-a-round was performed by the person adding the email address to the safe senders list using outlook.com web interface. This is unsuitable for my purposes because the emails need to arrive at outlook.com or hotmail.com mailboxes without intervening.
Has anyone got any information that could allow me to get to the bottom of why hotmail / outlook.com aggressively blocks valid email while hiding behind many pages of policy documents that don’t enlighten me as to why I have an IP address designated as “Not qualified for mitigation”.
I have attempted to engage with Microsoft regarding how to go about getting it working but if anyone has any experience with getting a Droplet to email directly to mx*.hotmail.com MX servers and have the email accepted I would love to hear from you.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
I found this in the microsoft support forum. The page looks very similar to the sender.office.com page linked above, but requests many more fields. Perhaps this is the updated version of the same service. https://support.microsoft.com/en-us/getsupport?oaspworkflow=start_1.0.0.0&wfname=capsub&productkey=edfsmsbl3&locale=en-us&ccsid=635639051175184163
I’m having a hard time as well. New emails are not bounced, nor do I get an error message in my mail log. Funny thing is, replying to an email sent from a hotmail account DOES work. So I had a look at the differences in headers. The only field was:
in-reply-to: <AMSPR05MB1163A06679EE051280F0EF78EE20@AMSPR05MB116.eurprd05.prod.outlook.com>
This resulted in the following DMARC report:
<policy_published>
<domain>engeen.nl</domain>
<adkim>r</adkim>
<aspf>r</aspf>
<p>none</p>
<sp>none</sp>
<pct>100</pct>
</policy_published>
<record>
<row>
<source_ip>188.166.43.30</source_ip>
<count>3</count>
<policy_evaluated>
<disposition>none</disposition>
<dkim>pass</dkim>
<spf>pass</spf>
</policy_evaluated>
</row>
<identifiers>
<header_from>engeen.nl</header_from>
</identifiers>
<auth_results>
<spf>
<domain>engeen.nl</domain>
<result>pass</result>
</spf>
<dkim>
<domain>engeen.nl</domain>
<result>pass</result>
</dkim>
</auth_results>
</record>
I have no idea what do try next… Does anyone know of an affordable relay as an alternative?
Any news? I’m in the same situation. Configured SPF records, dkim keys and only problems with hotmail, live or outlook accounts. My ip is not blacklisted, but doesn’t send enough mails to have any reputation and when talk to outlook support, they returned: “ip not qualified for mitigation” Any suggestion? usually change ip of droplet works? Big corporations with nonsense politics are really a pain…
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.