Solved Not able to receive email

P

PeterVeldhuis

Verified User
Joined
Jan 18, 2024
Messages
37
Location
Apeldoorn
Hi guys, I'm in the middle of migration from 1 tot another environment - left over with email, but not yet able got it to work to receive emails. Sending is fine.
I find below errors in exim/mainlog.
1710951013849.png

In order to try and fix this a previous error I've set "hostlist relay hosts" in comment (as per https://forum.directadmin.com/threads/directadmin-v1-646-has-been-released.67671/page-3)
1710951075638.png

But it doesn't resolve it yet.
Would you please able to help and quide me?
 
"Not able to receive email" is a little vague. Is the server not able to receive email or are you not able to download email from your server?
 
Looks like the setup of your mailserver is okay

Network Tools: DNS,IP,Email

DNS and Network troubleshooting and diagnostic tools integrated into one sweet interface.
mxtoolbox.com mxtoolbox.com

But your server name is host.ilonashairstyling.nl (?)
What you can try is going to CustomBuild, update Exim and LEGO and see what happens (?)


By the way, your blacklisted by SORBS SPAM (not relevant to the issue)

Also your ip 5.157.82.80 returns mail.ilonashairstyling.nl and nog host.ilonashairstyling.nl
 
PeterVeldhuis said:
I find below errors in exim/mainlog.
Click to expand...
ericosman said:
Looks like the setup of your mailserver is okay
Click to expand...
I highly bout that.

I found this:
failed to open /etc/virtual/pophosts etc.
Click to expand...
That file is not used for very long, since version 1.646

Version 1.646 | Directadmin Docs

DirectAdmin Knowledge Base
docs.directadmin.com

So what version of DA are you running?
And which versions of Exim.conf and exim.pl?

You could try to "touch" (create) that pophosts file, probably need to chown it to mail.mail in order to work. But that is just a workaround. Exim shouldn't look at it anymore.

I agree with @ericosman that it's better to not use kind of reserved names (like mail or ftp or mail) for the server's fqdn hostname as that can cause issues at a certain point. And never ever use a cname for that.

Because it looks like the cname is pointing to host.ilonashairstyling.nl as rDNS/PTR record or something which is a correct FQDN hostname.
So I would suggest to remove the cname and change your hostname to that hostname and don't use mail anymore and remove the cname.
 
Thank you all for your comments. Unfortunatelly I was sick for last 2 weeks and was not able to reply earlier. I will look into your recommendations and come back later this week.
 
Most likely the same virus I'm having here the last 1,5 week almost. Heavy flew is going around in our country also.
Get wel soon! Or in dutch... Beterschap!
 
Richard G said:
So what version of DA are you running?
Click to expand...
1.662
Richard G said:
And which versions of Exim.conf and exim.pl?
Click to expand...
Exim.conf:
SpamBlocker.exim.conf.2.1.1-release #
# 05-Jun-2007
(This looks a little old to me - in another post of 2017 I saw a 2.1.2 version, but probably also that is old)

But in CustomBuild I see:
1713982253145.png

Exim.pl:
1713981191933.png

1713981355197.png

Security: New exim.pl with improved filtering

Hello, I've added some extra filtering to the /etc/exim.pl versions to improve security with posted data. The versions that have been updated are: 16 -> 16 http://files.directadmin.com/services/exim.pl.16 17 -> 17 http://files.directadmin.com/services/exim.pl.17 23 -> 24...
forum.directadmin.com forum.directadmin.com


Richard G said:
You could try to "touch" (create) that pophosts file, probably need to chown it to mail.mail in order to work. But that is just a workaround. Exim shouldn't look at it anymore.

I agree with @ericosman that it's better to not use kind of reserved names (like mail or ftp or mail) for the server's fqdn hostname as that can cause issues at a certain point. And never ever use a cname for that.
Click to expand...
I found your post: https://forum.directadmin.com/threa...e-your-servers-hostname-in-directadmin.70371/

The hostname = host.ilonashairstyling.nl.

The DNS-record was setup, but there was no cert. I've now created that.

Richard G said:
Because it looks like the cname is pointing to host.ilonashairstyling.nl as rDNS/PTR record or something which is a correct FQDN hostname.
So I would suggest to remove the cname and change your hostname to that hostname and don't use mail anymore and remove the cname.
Click to expand...

I removed CNAME-record for mail.ilonashairstyling.nl.

I did send test emails:
1. outbound -- working fine
2. inbound -- don't see anything anywhere
 
Last edited:
you have some DNS en rDNS issues anyway

Reverse Entries for MX records

WARNING: Found mail servers with inconsistent reverse DNS entries. You should fix them if you are using those servers to send email.

ServerIPPTR (Reverse)IPs
host.ilonashairstyling.nl.5.157.82.80mail.ilonashairstyling.nl.?
All mail servers should have a reverse DNS (PTR) entry for each IP address (RFC 1912). Missing reverse DNS entries will make many mail servers to reject your e-mails or mark them as SPAM.
All IP's reverse DNS entries should resolve back to IP address (IP → PTR → IP). Many mail servers are configured to reject e-mails from IPs with inconsistent reverse DNS configuration.

Name Servers Have A Records

FAIL: We found name servers without A records.
  • be.ns.vip.nl. → 185.94.228.197
  • dns.resolver.domains. → 185.109.216.162
  • ns1.235.76.162. → ?
  • ns2.235.76.162. → ?
  • usa.ns.vip.nl. → 92.63.173.176
To reach your name servers via IPv4 an A record is needed for each name server.
 
PeterVeldhuis said:
Exim.conf:
SpamBlocker.exim.conf.2.1.1-release #
# 05-Jun-2007
Click to expand...
Yes that is way too old. I wonder why this isn't updated. This is the default standard exim.conf file of way in the beginning indeed.

Check your /usr/local/directadmin/custombuild/options.conf file.
Check that at least these 2 are set to yes:
Code: 
# Mail Settings
exim=yes
eximconf=yes

If any of them is set to no then after changing build the one which needs adjusting for example:
Code: 
./build update
./build exim
./build exim_conf
will rebuild both. And then you should have new exim.conf version.

I hope you have at least also a current Exim?
Should be like 4.97.1 #2.
 
Active8 said:
you have some DNS en rDNS issues anyway

Reverse Entries for MX records

WARNING: Found mail servers with inconsistent reverse DNS entries. You should fix them if you are using those servers to send email.

ServerIPPTR (Reverse)IPs
host.ilonashairstyling.nl.5.157.82.80mail.ilonashairstyling.nl.?
All mail servers should have a reverse DNS (PTR) entry for each IP address (RFC 1912). Missing reverse DNS entries will make many mail servers to reject your e-mails or mark them as SPAM.
All IP's reverse DNS entries should resolve back to IP address (IP → PTR → IP). Many mail servers are configured to reject e-mails from IPs with inconsistent reverse DNS configuration.

Name Servers Have A Records

FAIL: We found name servers without A records.
  • be.ns.vip.nl. → 185.94.228.197
  • dns.resolver.domains. → 185.109.216.162
  • ns1.235.76.162. → ?
  • ns2.235.76.162. → ?
  • usa.ns.vip.nl. → 92.63.173.176
To reach your name servers via IPv4 an A record is needed for each name server.
Click to expand...
hi - I removed ns1 en ns2 from DNS records. And I changed the PT to be host.ilonashairstyling.nl.
 
Richard G said:
Yes that is way too old. I wonder why this isn't updated. This is the default standard exim.conf file of way in the beginning indeed.

Check your /usr/local/directadmin/custombuild/options.conf file.
Check that at least these 2 are set to yes:
Code: 
# Mail Settings
exim=yes
eximconf=yes
Click to expand...

They were set to NO. I changed them
1714067805342.png

Richard G said:
If any of them is set to no then after changing build the one which needs adjusting for example:
Code: 
./build update
./build exim
./build exim_conf
will rebuild both. And then you should have new exim.conf version.

I hope you have at least also a current Exim?
Should be like 4.97.1 #2.
Click to expand...

After running both builds I see:
1714069620455.png

I've re-run tests:
- outbound: works still perfect!
- inbound: works perfect now!!


Thank you all for your help!
 

Attachments

  • 1714069162918.png
    1714069162918.png
    2.8 KB · Views: 1
You're welcome.
Glad to see things are working now.

I would however advise to enable blockcracking and easy spamfighter too, because they are really helpful to fight spam. ;)
 
You must log in or register to reply here.
Back
Top