Mails not working since last update?

[mvlover]

Hello,

My myVesta instance was updated automatically to myVesta 0.9.9-0-1 Build date: 05-Jun-2023. Nice job by the way for the CMS work for admin/user board!

I was waiting for a verification code by mail for a service and it was not coming. I try to send an email to another email box in another server: mail not received.

So on a domain on the instance, I can't receive and send email? No error appeared when sending the email in roundcube?

I don't see error in last lines of mail.log file.

It was working correctly the days before. I have mails in box the days before.

Thank you in advance for help.

mVlover

[myVesta]

Do you see any error in

Code: Select all

cat /var/log/exim4/mainlog

?


What do you get if you type

Code: Select all

systemctl status exim4

?

[mvlover]

Not easy to find things in this file, so much flood.

Code: Select all

cat /var/log/exim4/mainlog


I see the lines when I try to send an email:
2023-06-08 12:47:20 H=localhost (host.domain.com) [127.0.0.1] Warning: Sender rate [limitlog]: log / email / [email protected] / 1.0 / 1h
2023-06-08 12:47:20 1q7InA-00B0aC-Dy <= [email protected] H=localhost (host.domain.com) [127.0.0.1] P=esmtpa A=dovecot_login:[email protected] S=600 id=4a753abe0c50c1efa12d8184f6a1663f@@domaininmyvesta.com
2023-06-08 12:47:21 1q7InA-00B0aC-Dy H=domainwhereisendtheemail.com [67.227.xxx.xx] Connection refused
2023-06-08 12:47:21 1q7InA-00B0aC-Dy == [email protected] R=dnslookup T=remote_smtp defer (111): Connection refused

and lot of flood messages of this type:

Code: Select all

2023-06-08 12:45:16 1q6MFb-008ZHt-Pf Message is frozen
2023-06-08 12:45:16 1q70Ut-00A8z2-MG == [email protected] <[email protected]> R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host for 'gmail.com'

and thousand of user trying to connect to mailbox which does'nt exist on the server
74000 lines in the file since 00:00:05

Code: Select all

2023-06-08 00:00:05 1q76of-00AOBU-MO U=root Warning: Sender rate [limitlog]: log / account /  / 10.5 / 1h

Code: Select all

systemctl status exim4
exim4.service - LSB: exim Mail Transport Agent
     Loaded: loaded (/etc/init.d/exim4; generated)
     Active: active (running) since Mon 2023-06-05 06:45:10 EDT; 3 days ago
       Docs: man:systemd-sysv-generator(8)
    Process: 1883868 ExecStart=/etc/init.d/exim4 start (code=exited, status=0/SUCCESS)
      Tasks: 10 (limit: 9510)
     Memory: 34.5M
        CPU: 37min 41.468s
     CGroup: /system.slice/exim4.service
             ├─1884117 /usr/sbin/exim4 -bd -q30m
             ├─2676578 /usr/sbin/exim4 -bd -q30m
             ├─2676779 /usr/sbin/exim4 -bd -q30m
             ├─2676802 /usr/sbin/exim4 -bd -q30m
             ├─2676809 /usr/sbin/exim4 -bd -q30m
             ├─2676820 /usr/sbin/exim4 -bd -q30m
             ├─2676830 /usr/sbin/exim4 -bd -q30m
             ├─2676849 /usr/sbin/exim4 -bd -q30m
             ├─2676853 /usr/sbin/exim4 -bd -q30m
             └─2676854 /usr/sbin/exim4 -bd -q30m

Jun 05 06:45:10 host.domain.com systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 05 06:45:10 host.domain.com  systemd[1]: exim4.service: Found left-over process 1883865 (exim4) in control group while starting unit. Ignoring.
Jun 05 06:45:10 host.domain.com systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 05 06:45:10 host.domain.com  systemd[1]: Starting LSB: exim Mail Transport Agent...
Jun 05 06:45:10 host.domain.com  exim4[1883868]: Starting MTA: exim4.
Jun 05 06:45:10 host.domain.com  systemd[1]: Started LSB: exim Mail Transport Agent.

Don't see any incoming mail from the service I was waiting an email.

[mvlover]

EDIT: "Don't see any incoming mail from the service I was waiting an email." => In reject log file in found the line...

2023-06-08 12:38:26 H=o2.outbound-sg.digitalocean.com [168.245.49.182] X=TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128 CV=no F=<[email protected]> rejected RCPT <[email protected]>: Rejected because 168.245.49.182 is in a black list at bl.spamcop.net

Mail system which generates code for connection of digitalocean in black list??

[mvlover]

On this instance, I have also CSF installed. In the new GUI, I don't see anymore the link to the admin section of CSF.
I think the black list at bl.spamcop.net of some domains is due to some configuration of CSF. I will disable it for test. I will keep you informed.

[myVesta]

You can send me on private message your server credentials (root ssh) and what domain is not receiving emails, i will check.

[mvlover]

UPDATE

Mails are working since the desactivation of CSF. I think it's due to some configuration and the default firewall seems to have be reloaded when there was the myvestacp update (?). I will try to improve the configuration.

For those who don't know how to display the page of CSF:

https://hostname.com:8083/list/csf/

Thank you for you help.

Your message telling me where exim4 log where helped me.

[myVesta]

Firewall is not reloaded during update, I'm 100% sure.
But Exim conf got 2 patches, and we restarted Exim during update.

https://github.com/myvesta/vesta/blob/0 ... nst#L28L47

[Stevekali1]

EDIT: "Don't see any incoming mail from the service I was waiting an email." Passenger car with driver cdg to Rouen => In reject log file in found the line...

2023-06-08 12:38:26 H=o2.outbound-sg.digitalocean.com [168.245.49.182] X=TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128 CV=no F=<[email protected]> rejected RCPT <[email protected]>: Rejected because 168.245.49.182 is in a black list at bl.spamcop.net

Mail system which generates code for connection of digitalocean in black list??

I think you can try another more convenient method, but hey, that's just my opinion. THANKS