E-mails are not sent from my Linux hosting, but I get them from third parties

leobibiano

• September 07, 2020 14:32

I installed WHM / cPanel on an EC2 instance of Amazon AWS, I did all the configuration according to the

• 

  keat63

  • September 08, 2020 07:51

  Until an expert comes along. DNS could take a while to propagate. You will probably require RDNS config setting up. Also MXToolbox.com has lots of tools which may give some pointers.

  0
• 

  cPanelLauren

  • September 08, 2020 21:32

  They do sometimes require that you contact them to open port 25. You can find out what happened to the email a couple of ways though. 1. From cPanel go to cPanel>>Email>>Track Delivery 2. From the command line check /var/log/exim_mainlog
  

  0
• 

  leobibiano

  • September 09, 2020 11:34

  Until an expert comes along. DNS could take a while to propagate. You will probably require RDNS config setting up. Also MXToolbox.com has lots of tools which may give some pointers.

  
  Thanks for the tip! There were configuration problems in the DNS, thanks to your tip I managed to solve. However, I was unable to solve the problem of sending emails.

  0
• 

  leobibiano

  • September 09, 2020 11:45

  They do sometimes require that you contact them to open port 25. You can find out what happened to the email a couple of ways though. 1. From cPanel go to cPanel>>Email>>Track Delivery 2. From the command line check /var/log/exim_mainlog
  

  
  Thanks for the feedback! I checked my server's settings regarding port 25, it's open. I believe that is not the problem. Is there anything else that may be preventing these emails from being delivered? Attached here is the result of the consultation that you instructed me to do.

  0
• 

  leobibiano

  • September 09, 2020 12:27

  I found the commands below: /usr/sbin/exim_tidydb -t 1d /var/spool/exim retry > /dev/null /usr/sbin/exim_tidydb -t 1d /var/spool/exim reject > /dev/null /usr/sbin/exim_tidydb -t 1d /var/spool/exim wait-remote_smtp > /dev/null /scripts/courierup -- force /scripts/eximup --force However, they are from old topics (mid-2012). I found explanations stating that they no longer work. I also found other people advising me to use this below: cd /var/spool/exim/db rm -f retry retry.lockfile rm -f wait-remote_smtp wait-remote_smtp.lockfile service exim restart I tried to use all the codes informed above, but without success, the e-mails are still undeliverable.

  0
• 

  keat63

  • September 09, 2020 13:16

  Do you have access to whm terminal ? Can you actually ping hotmail.com CTRL + C to quit the ping I guess if you can receive but not send, then connection to Hotmail is not the actual issue ?

  0
• 

  leobibiano

  • September 09, 2020 13:30

  Do you have access to whm terminal ? Can you actually ping hotmail.com CTRL + C to quit the ping I guess if you can receive but not send, then connection to Hotmail is not the actual issue ?

  
  I ran the code you asked for. PING hotmail.com (204.79.197.212) 56(84) bytes of data. 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=1 ttl=114 time=2.81 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=2 ttl=114 time=2.50 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=3 ttl=114 time=2.41 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=4 ttl=114 time=2.74 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=5 ttl=114 time=2.30 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=6 ttl=114 time=2.65 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=7 ttl=114 time=3.06 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=8 ttl=114 time=2.64 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=9 ttl=114 time=2.63 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=10 ttl=114 time=2.35 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=11 ttl=114 time=2.56 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=12 ttl=114 time=2.31 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=13 ttl=114 time=2.69 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=14 ttl=114 time=2.54 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=15 ttl=114 time=2.59 ms 64 bytes from a-0010.a-msedge.net (204.79.197.212): icmp_seq=16 ttl=114 time=2.75 ms ^C --- hotmail.com ping statistics --- 16 packets transmitted, 16 received, 0% packet loss, time 15018ms rtt min/avg/max/mdev = 2.308/2.601/3.069/0.201 ms

  0
• 

  leobibiano

  • September 09, 2020 13:35

  I saw some people saying that port 25 of the new AWS EC2 instances is being filtered. I found in the support area a topic that explains a little about this:

  0
• 

  leobibiano

  • September 09, 2020 15:04

  Finally, solved! The problem was in the limitation of AWS. If you'd like to proceed with assigning a reverse DNS record to the Elastic IP, the first step would be to configure the A record for the domain to match the desired PTR record on your side. Please follow the instructions at the link below to create the A record:

  0

Please sign in to leave a comment.