Can Send Email, But can't Receive Email

Rel82me

Active Member
Feb 20, 2016
26
0
51
Toronto
cPanel Access Level
Root Administrator
Hey Friends, it's been a bad week with power outages.. Had to recover cPanel from a backup, but am having problems with receive mail.

[[email protected] ~]# curl portquiz.net:25
Port test successful!
Your IP: 206.248.138.180

traceroute to mail.aosystemsgroup.com (192.168.1.140), 30 hops max, 60 byte packets
1 host001.aosystemsgroup.com (192.168.1.140) 0.036 ms 0.015 ms 0.014 ms

Any suggestions?
 

quietFinn

Well-Known Member
Feb 4, 2006
1,668
341
438
Finland
cPanel Access Level
Root Administrator
traceroute to mail.aosystemsgroup.com (192.168.1.140), 30 hops max, 60 byte packets
1 host001.aosystemsgroup.com (192.168.1.140) 0.036 ms 0.015 ms 0.014 ms

Any suggestions?
192.168.1.140 is in a Private IP range ( 192.168. 0.0 - 192.168. 255.255 ), it's not possible to connect to a Private IP from internet.
 

HostNoc

Well-Known Member
Feb 20, 2020
153
38
28
Ontario
cPanel Access Level
Root Administrator
Hi

I can see that there is multiple MX record set against your domain

;; ANSWER SECTION:
portquiz.net. 600 IN MX 10 mx3.mail.ovh.net.
portquiz.net. 600 IN MX 1 mx4.mail.ovh.net.

Please correct your MX record so your email should work

Regards
SAM
HostNoc
 

Rel82me

Active Member
Feb 20, 2016
26
0
51
Toronto
cPanel Access Level
Root Administrator
192.168.1.140 is in a Private IP range ( 192.168. 0.0 - 192.168. 255.255 ), it's not possible to connect to a Private IP from internet.
My tracert results:

C:\Windows\System32>tracert mail.aosystemsgroup.com

Tracing route to aosystemsgroup.com [192.168.1.140]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms aosystemsgroup1.com [192.168.1.140]

Trace complete.

C:\Windows\System32>

I do recall that we added "aosystemsgroup1.com" someplace on the routing device for testing....Still no inbound email.

Wish support at cPanel go a little further with the help.
 

cPanelWilliam

Administrator
Staff member
Mar 13, 2018
108
17
93
Houston
cPanel Access Level
Root Administrator
Hello! I agree with @quietFinn , at first glance I'm seeing that the MX record for aosystemsgroup.com resolves to an internal IP address (192.168.1.140):

http://leafdns.com/index.cgi?testid=9D9B1909&lock

As a general rule, you should avoid using internal IP addresses within DNS as external servers would not be able to connect to the internal IP. You can use the DNS Zone Manager in WHM to edit your MX record to resolve this. As an example, you could create a new A record that resolves to your server's external IP such as mailserver.aosystemsgroup.com resolving to 206.248.138.180, then you can set the MX record to mailserver.aosystemsgroup.com. This is assuming that your server's external IP is 206.248.138.180.