For up-to-date information and comments, search the EE Community or start a new topic. |
14-06-2021 01:09 PM
A number of emails (Outlook.com) addressed to me have not been arriving.
On checking with my DNS provider (Namesilo), I have found the following error message:
5.7.1 Unfortunately, messages from [107.170.11.17] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3150).
I would be grateful if you would help me to troubleshoot this.
Solved! See the answer below or view the solution in context.
14-06-2021 03:18 PM
I solved the issue by updating my MX records, courtesy of DNS provider.
14-06-2021 01:40 PM - edited 14-06-2021 01:41 PM
Hi @nsihwa ,
A look up suggests the issue is with a mail server under emailowl.com and the company you wish to speak to about this is "Digital Ocean".
https://www.lookip.net/ip/107.170.11.17
Technical details
IP address | 107.170.11.17 |
Address type | Public |
Protocol version | IPv4 |
Network class | Class A |
Conversions | 1806306065 (decimal / iplong) 6baa0b11 (hex / base 16) |
Reverse DNS | 17.11.170.107.in-addr.arpa |
Hostname | mx1.emailowl.com |
Reverse lookup | mx1.emailowl.com |
ISP | Digital Ocean |
Company | Digital Ocean |
14-06-2021 02:00 PM
Thank you.
14-06-2021 02:02 PM - edited 14-06-2021 02:24 PM
@mikeliuk : Sorry, you're right! I just grabbed the wrong IP from your post & it happened to be in reverse. Shoulda kept to OP's post.
14-06-2021 02:10 PM
I really don't see why it's telling you to consult your ISP when the issue is with the sender's IP.
To get round this issue try switching your DNS provider to 1 of these public DNS pairs:
OpenDNS : 208.67.222.222 & 208.67.220.220 Google DNS: 8.8.8.8 & 8.8.4.4
Cloudflare DNS 1.1.1.1 & 1.0.0.1
14-06-2021 02:12 PM - edited 14-06-2021 02:13 PM
The IPv4 address beginning 17 is being read backwards.
See "reverse lookup zone": https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-subnetted-reverse-...
This assumes the OP reported the original IPv4 address correctly.
14-06-2021 03:18 PM
I solved the issue by updating my MX records, courtesy of DNS provider.