Cannot receive email

Someone

New member
Joined
Oct 11, 2019
Messages
3
This is my first time using DirectAdmin and must say it is pretty cool. If I remember correctly I have reinstalled DirectAdmin 3/4 times just to make my mail server for receiving email working. Until now it still doesn't work as expected.

I have done a search on this forum to solve this issue, but none of the work for me.

Sent emails from my Gmail account to the one I created on DirectAdmin panel, the emails never arrived. I have looked at /var/log/exim/mainlog and couldn't find anything suspicious related to inbound email.
Code:
2019-10-12 23:04:55 1iJJiT-0006i3-W0 H=alt4.gmail-smtp-in.l.google.com [173.194.214.27] Connection timed out
2019-10-12 23:04:55 1iJJiT-0006i3-W0 == myemail@gmail.com R=lookuphost T=remote_smtp defer (110): Connection timed out
2019-10-12 23:12:36 cwd=/ 3 args: /usr/sbin/exim -bd -q1h
2019-10-12 23:12:36 exim 4.92.3 daemon started: pid=28472, -q1h, listening for SMTP on port 25 (IPv4) port 587 (IPv4) and for SMTPS on port 465 (IPv4)
2019-10-12 23:12:36 cwd=/var/spool/exim 2 args: /usr/sbin/exim -qG
As far as I know port 25 is blocked by ISP. I guess it has nothing to do with receiving email, right?

It is installed on Debian 9.
Domain: supplieralattulis.com
 

Richard G

Verified User
Joined
Jul 6, 2008
Messages
4,221
Location
Maastricht
As far as I know port 25 is blocked by ISP. I guess it has nothing to do with receiving email, right?
If you run your server at home, yes for sure it does. All incoming mail traffic to the server is coming in via port 25.

But for users to send mail it's no problem, they can use port 587 or 465.
On your domain port 25 is working so no problem there.

I've checked, you've got a DNS nameserver issue. There's really something wrong with your nameservers which is causing isues.
Also there is no RDNS to your hostname, which you really should make.
 

Someone

New member
Joined
Oct 11, 2019
Messages
3
The problem solved now. I created a ticket to ask the provider if they block port 25. Now they have whitelisted my service.

Thanks!
 

Richard G

Verified User
Joined
Jul 6, 2008
Messages
4,221
Location
Maastricht
You're welcome. DNS seems fixed now too except this.

If this is your host or uplink, tell them to fix it:
SOA Serial Number Format is Invalid
ns1.dnsowl.com reported Serial 1571009978 : Suggested serial format year was 1571 which is before 1970.
it's not really an issue, but it's not according to RFC's.
 

Someone

New member
Joined
Oct 11, 2019
Messages
3
Hi Richard,

It is fixed now. I'm using another domain.
Code:
Your SOA serial number is: 2019101301. This appears to be in the recommended format of YYYYMMDDnn.
Thanks.
 
Top