Exim4 does not receive emails

roneycs · April 21, 2020, 6:18pm

I’m using
Hestia Control Panel: v1.1.1
Operating System: Debian 10.3 (x86_64)

I did several searches on the forum and google, but I couldn’t find any solution to my problem.

I used http://mxtoolbox.com to check the MX (No errors)

My problem:
I access the Roundcube and can send emails as usual
when I reply to these emails outside my server (example gmail) the email does not arrive.

Can you help me?

Raphael · April 21, 2020, 6:50pm

I’m sorry, but you wrote this already, also you got a detailed answer from @falzo, which I add again below:

Enviar e-mails para o gmail

hard to say from distance as it entirely depends on your setup, especially domain provider, dns-server etc.
sadly we can’t cover this here in terms of support, as this is most likely not hestia related and we expect you to be able to handle basic management/administration task on your own - like the way you would need to without hestia

however, before dealing with gmail, how about you setup your domain and a single mail account on your hestia server first. then use a local mail client or even the webmail to check if mail is working at all .
if not check the via one of the bigger online page that help with testing mail setups (mxtoolbox f.i.) …

only after you have your inbox running on your server start connecting it to gmail - I guess that way would make it more easy, esp. for troubleshooting

roneycs · April 21, 2020, 11:50pm

I apologize for insisting on this help topic.

I did a shipping test by wordpress, it is authenticated and sends emails.
I tested using telnet on the server CLI, the email is also sent

Is there any way to reconfigure exim4?
I don’t know what else I can do.

Raphael · April 22, 2020, 5:04am

Exim4 works already out of the box, there is no need to reconfigure.

Please follow the advice of @falzo for debuging your issue, start with an easy domain setup, verify that you xan send and receive emails, have proper records and communication - then proceed with the next step. But as he already properly wrote, we can’t help out here - we support if you have hestia related issues.

falzo · April 22, 2020, 7:50am

have you made sure your dns settings are correct?
have you accidentically blocked yourself incoming on port 25 with the firewall settings or forgotten to open that port on your providers firewall?
check your logfiles. do you see incoming connections from gmail getting rejected? do you see incoming connections at all?

mails don’t get lost at all, so if it doesn’t arrive in your inbox, what does the ‘not delivered’ message say? after 24h you’d at least should get a ‘deferred’ message or something alike…

I have to agree with @Raphael , this are basic server management task you should be able to manage yourself - hestia is intended to make setup and reoccuring tasks easier, however it’s not there to simply skip learning you still need to have everything around it setup correctly and know what you are doing - we can’t help with that.

if this sounds rude or disappointing I apologize. however, we really have no intention of nurturing the thought that hestia is a beginners product

realjumy · April 22, 2020, 7:55am

I agree with @falzo, it seems a problem with the DNS. Are you sure that the DNS are only configured in Hestia and there is nothinG conflicting in the company providing you the domain?

roneycs · April 22, 2020, 1:58pm

@realjumy @falzo Thanks for the replies

My domain is pointing to cloudflare by NS.

In Cloudflare I have the DNS mail entries for the server’s ip
I also have the MX entry pointing to the DNS mail entry

Doing a simple connection test with mxtoolbox.com it does not show an error

CloudFlare

I did a test of SMTPTest by mxtools and it is returning this to me.
https://mxtoolbox.com/SuperTool.aspx?action=mx%3Amelatoninavix.com&run=toolpage#

220 45.56.112.235 [609 ms]
EHLO keeper-us-east-1b.mxtoolbox.com
250-45.56.112.235 Hello keeper-us-east-1b.mxtoolbox.com [52.55.244.91]
250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-AUTH PLAIN LOGIN
250-CHUNKING
250-STARTTLS
250 HELP [609 ms]
MAIL FROM:<[email protected]>
250 OK [616 ms]
RCPT TO:<[email protected]>
**550 relay not permitted [728 ms]**

A test was carried out on the ipok.com.br website with SMTP AUTH Banner

Firewall HestiacP

LOG Exim Mainlog

root@fw:/var/log/exim4# cat mainlog
2020-04-22 12:12:49 1jRH3R-0000Ta-I2 <= [email protected] H=mail-il1-f182.google.com [209.85.166.182] P=esmtps X=TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128 CV=no SNI="mail.melatoninavix.com" K S=2960 DKIM=gmail.com id=CAP8M9mE3Dh7-HP=9Wce_JYwzGVinduWRSeVOhTr+oQouncm4XA@mail.gmail.com
2020-04-22 12:12:49 1jRH3R-0000Ta-I2 => sistema <[email protected]> R=localuser_fwd_only T=devnull
2020-04-22 12:12:49 1jRH3R-0000Ta-I2 Completed
2020-04-22 12:18:34 1jRH90-0000a2-31 <= [email protected] H=mail-il1-f176.google.com [209.85.166.176] P=esmtps X=TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128 CV=no SNI="mail.melatoninavix.com" K S=2968 DKIM=gmail.com id=CAP8M9mHsHaph18KpjVn-4aDyqq5YSjXxP5FCyD1-K9ZdSb1VCw@mail.gmail.com
2020-04-22 12:18:34 1jRH90-0000a2-31 => sistema <[email protected]> R=localuser_fwd_only T=devnull
2020-04-22 12:18:34 1jRH90-0000a2-31 Completed
2020-04-22 12:19:13 Start queue run: pid=2241
2020-04-22 12:19:13 1jR2AZ-0000DL-6q Message is frozen
2020-04-22 12:19:13 1jQyWV-0000Cm-Lz Message is frozen
2020-04-22 12:19:13 End queue run: pid=2241
2020-04-22 12:34:00 1jRHNw-0000sG-GD <= [email protected] H=mail-qk1-f181.google.com [209.85.222.181] P=esmtps X=TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128 CV=no SNI="mail.melatoninavix.com" K S=3035 DKIM=gmail.com id=CAP8M9mFUZMVQ6Ogj7rxh=cMjQ76BZ1BWdk5B5ysOJ4VGz0MEgA@mail.gmail.com
2020-04-22 12:34:00 1jRHNw-0000sG-GD => sistema <[email protected]> R=localuser_fwd_only T=devnull
2020-04-22 12:34:00 1jRHNw-0000sG-GD Completed

realjumy · April 22, 2020, 8:26pm

I might be wrong, but you should configure the DNS with Hestia, wait a day for the DNS to propagate, and then use CloudFlare. Starting from a Hestia’s default settings, Cloudflare should detect your DNS configuration and import it.

Try like that and check again (maybe you will have to delete your domain from Cloudflare first).

Just remember:

Always do backup of all configurations and system
The DNS take long to update, so you should wait when you start using Hestia’s DNS and then wait again before configuring Cloudflare again.
I can be wrong

Good luck!

falzo · April 22, 2020, 10:20pm

really?

2020-04-22 12:12:49 1jRH3R-0000Ta-I2 => sistema [email protected] R=localuser_fwd_only T=devnull

sorry man, but obviously you setup your mail account that you are trying to send something to with a forward and to not keep a local copy.
so every mail comes in, gets forwarded (maybe) and saved in /dev/null aka deleted.

of course they won’t appear in your inbox then.

falzo · April 22, 2020, 10:22pm

PS: and probably because the forward then fails (if you forward back to gmail, it’s most likely just rejected because it’s a loop) the message ends up in the frozen queue, because it has nowhere else to go to.

roneycs · April 22, 2020, 10:46pm

Thanks for the reply @falzo @realjumy

I am not using any type of email forwarding.
Follow the hestiacp settings

roneycs · April 22, 2020, 10:47pm

Thanks for the answer.

I didn’t check any option not to keep a copy, how do I change it?

falzo · April 22, 2020, 10:56pm

your logfile definitely says otherwise. also your initial question about catchall and forwarding suggest, that you tried quite some things before…

whatever you did change or not, something got messed up. probably best to remove the mail-account and the mail domain completely and then step-by-step add it again.

you could also try to simply set up another mail account that might not be borked already - just for testing purposes

however, your exim4 mailserver clearly receives messages. it just tries to forward them and deletes them right after. that’s a configuration issue caused by whatever else you might have already tried to fix it or achieve your initial goal to forward stuff. did you do some stuff on the console or add aliases manually to the exim config or something like that?

good thing though: at least your dns entries seems to be working as intended