0

The domain of my website as an example is www.abc.cc. The IP of it is 1.1.1.1 as an example also. And, the IP of mail is different. It is as an example 2.2.2.2 and the problem is i can send an email through any email under this domain but I can not receive any email. How can i solve this problem?

Amd2030
  • 113
  • 2
  • Provide true names and IPs if you want people to help you. – Patrick Mevzek Sep 18 '17 at 03:14
  • More information is required, in particular: - What environment is your server running on? - in terms of testing, what have you tried? - Have you set up spf and/or dkim records? - Have you consulted any message tracking logs? - Do you have any security in place (firewalls etc.) that could stop incoming messages? – mattb Sep 16 '17 at 08:50
  • in term of testing: i only send a massge and then i get this massage: Delivery incomplete There was a temporary problem delivering your message to a@abc.cc. Gmail will retry for 47 more hours. You'll be notified if the delivery fails permanently. The response was: The recipient server did not accept our requests to connect. [abc.cc. 1.1.1.1: timed out] Final-Recipient: rfc822; a@abc.cc Action: delayed Status: 4.4.1 Diagnostic-Code: smtp; The recipient server did not accept our requests to connect – Amd2030 Sep 16 '17 at 08:54
  • Can you enter your actual domain name? If not, can you use MX Toolbox and reply with your output? https://mxtoolbox.com – mattb Sep 16 '17 at 08:59
  • What environment is your server running on? i don't know . it's not my server . Have you set up spf and/or dkim records? i change CNAME record of mail.abc.cc to A record as 2.2.2.2 and not working – Amd2030 Sep 16 '17 at 09:05
  • What are your MX records set at? Can you use the tool I mentioned and reply with output? You need more than just a CNAME and A record. – mattb Sep 16 '17 at 09:12
  • 0 mx record and smtp test for 1.1.1.1 is : SMTP Reverse DNS Resolution: Reverse DNS Resolution - No PTR Record found SMTP TLS: Warning - Does not support TLS. SMTP Server Disconnected: May be an open relay. – Amd2030 Sep 16 '17 at 09:29
  • smtp test for 2.2.2.2 is: SMTP Banner Check: Reverse DNS does not match SMTP Banner SMTP TLS Warning - Does not support TLS. SMTP Transaction Time 15.064 seconds - Not good! on Transaction Time SMTP Reverse DNS Mismatch OK - 2.2.2.2 resolves to rs104.nsresponse.com SMTP Valid Hostname OK - Reverse DNS is a valid Hostname SMTP Connection Time 0 seconds - Good on Connection time SMTP Open Relay OK - Not an open relay. – Amd2030 Sep 16 '17 at 09:29
  • Is there a reason you don't have an MX records set (unless of course I missed that)? It is possible to fallback to A records (see https://serverfault.com/a/470651/435758) but it's always best practice to have an MX records present. – mattb Sep 16 '17 at 10:05
  • I get mx record from cmd by this command nslookup -debug -q=mx abc.cc. MX preference = 10, mail exchanger = mx1.norelay.stc.com.sa ttl = 0 (0 secs) – Amd2030 Sep 16 '17 at 11:40
  • This does not provide an answer to the question. Once you have sufficient [reputation](https://serverfault.com/help/whats-reputation) you will be able to [comment on any post](https://serverfault.com/help/privileges/comment); instead, [provide answers that don't require clarification from the asker](https://meta.stackexchange.com/questions/214173/why-do-i-need-50-reputation-to-comment-what-can-i-do-instead). - [From Review](/review/low-quality-posts/340759) – kasperd Sep 19 '17 at 06:13

2 Answers2

0

Your question is unclear, but this error usually come from two possible source.

  • Your MX is not set correctly. The public DNS MX should point to 2.2.2.2. To test please use nslookup, set q=mx, domain.com, it should list your mx

  • Your router doesn't forward the port 25 to your server. (Incoming NAT rule in your router, 2.2.2.2 ==> ip of your server on port 25) To test try from home to telnet to your server, telnet public_ip 25, you should see the email server prompt.

Edit: After our comment, please put 2.2.2.2 as your MX, the host you currently have there is not valid

yagmoth555
  • 16,758
  • 4
  • 29
  • 50
0

My problem is solved by the following steps:

  1. edit MX record from abc.cc to mail.abc.cc
  2. add A record of mail.abc.cc to IP 2.2.2.2
  3. remove dmarc and disabled Dkim and SPF
  4. edit email routing to local mail exchanger
bummi
  • 162
  • 2
  • 2
  • 9
Amd2030
  • 113
  • 2