I reported a deliverability problem to Outlook and they said that this IP is "Not qualified for mitigation", because "These IP(s) have previously received mitigations from deliverability support, and have failed to maintain patterns within our guidelines"ĭoes this mean, that I cannot send emails to them with Mailgun for as long as I am using a shared IP address? Or is there something that can be done?ĥ.7.1 Unfortunately, messages from weren't sent. So I emailed Mailgun Dear MailGun,Īll outgoing emails are being blocked by (Outlook, Hotmail, etc.), on the shared IP xxx.xx.xxx.xxx. They responded that mitigation was not possible due to repeated violations of their policies, and so on. Then I attempted to contact Microsoft, asking them to remove the blocked IP from their block list - the form to do that is under this link. Please contact your Internet service provider since part of their network is on our block list (S3140). This was the error message in Mailgun logs 5.7.1 Unfortunately, messages from weren't sent. The Microsoft email domains not working and doing the blocking were at least, , msn.com and .ĭetails on how the Mailgun emails were unblocked Also, I’ve set up a “ Zapier automation” which integrates with Mailgun to notify of any future blocks. The spam problem is solved over time as Outlook users mark emails as not junk.
Although emails were delivered straight away, Outlook was marking the emails as spam and moving them to the junk folder. They were very helpful and quickly moved my Mailgun emails to another IP address, which wasn’t blocked.
The solution was to email Mailgun and explain to them what had happened. What happened was that an account on the same shared Mailgun IP had sent a lot of emails to Outlook which had caused them to add the IP to their block list.
I am doing my best to follow along and learn as I go.My solution to the problem when Outlook, Hotmail and a bunch of other email domains from Microsoft blacklisted my Mailgun IP and blocked all emails. This is one area of my server where my knowledge is (at least) slightly lacking. Once again thank you for the patience and assistance. Is this something that I should do and if so is there anything I should look (to ensure it is set correctly) at before performing this function? Reading the description this looks to perform a clean up of SPF and DKIM on any accounts that were built pre v62. I notice that under WHM - DNS Functions there is an option called Enable DKIM/SPF Globally. In the zone for the actual domain that is bouncing I see all of those (for that domain) plus the following.ĭ. 1) Is this under WHM - Edit a DNS zone? Is the zone for the server the zone I want to look at?