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

[leobibiano]

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

I created the first cPanel account through WHM, I pointed the domain all right. Domain access is working correctly.

So I created an e-mail through cPanel, accessed it through Webmail and shot my personal e-mail (hotmail). However, I did not receive the email.

I did a test then sending it from my personal (hotmail) to my hosting, and it arrived normally. So I came to the conclusion that the problem is with sending the email out and not receiving it from outside.

I also tried to send it to other emails (gmail, yahoo) and none of them arrived.

Does anyone know what can it be? Is it any configuration that I missed?

Thank you.

 

[keat63]

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.

 

[cPanelLauren]

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

 

[leobibiano]

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.

 

[leobibiano]

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.

 

[leobibiano]

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.

 

[keat63]

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 ?

 

[leobibiano]

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

 

[leobibiano]

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:

How do I remove the restriction on port 25 from my EC2 instance?

I will try to make the request that is guided in the topic. Then I'll come back to talk if this was the problem.

 

[leobibiano]

Finally, solved!

The problem was in the limitation of AWS.
I filled out the form to release e-mails. They sent me an email with some questions about why I wanted to email that account. I answered everything as they asked me, so I received the approval.

Honestly, I was upset with AWS for putting this type of limitation without informing the customer. It was very difficult to find that information.

Below is the email that the AWS team sent me:

---
Hello,

We approved your request for the removal of the EC2 email sending limitations on your Amazon Web Services account for the following regions [sa-east-1] ! If you requested removal of email sending limits on any other Amazon Elastic IPs, they've also been removed.

Because reverse DNS record entries are commonly considered in anti-spam filters, we recommend assigning a reverse DNS record to the Elastic IP address you use to send email to third parties. Please use the form located at this link to request a reverse DNS entry:
https://aws-portal.amazon.com/gp/aws/html-forms-controller/contactus/ec2-email-limit-rdns-request

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:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html

Please let us know if you have any questions.

Regards,
Amazon Web Services