Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: mail.mpec.mielec.pl
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Without any information about your system we (the community) don't know either. Your cert was last renewed in July https://crt.sh/?q=mail.mpec.mielec.pl
Sorry, I'm a new IT in the company, and the previous one didn't tell me how to do it, and today the email stopped working because of this certificate.
The mail server is Ubuntu 18.04.6 LTS and the domain server is Windows Server 2012 R2.
If the W2K12 isn't using port 80, you could have the FG firewall direct the incoming HTTP requests directly to the Ubuntu system.
There it could run an ACME client and obtain/manage the required mail cert.
Who is the firewall admin?
Not so sure about that. If I connect to your SMTP server on mail.mpec.mielec.pl:25 with STARTTLS, I'm getting a verification problem, because your Fortigate seems to be sending an untrusted certificate, not the one from Let's Encrypt:
0 s:C = US, ST = Undefined, L = Undefined, O = MPEC Sp. z o.o. w Mielcu, CN = mail.mpec.mielec.pl
i:C = US, ST = California, L = Sunnyvale, O = Fortinet, OU = Certificate Authority, CN = Fortinet Untrusted CA, emailAddress = support@fortinet.com
Same goes for the "submission" port on port 587 and SMTPS on port 465, where the latter is by the way improperly configured. Port 465 is the SMTP port with implicit TLS (so NO STARTTLS, but TLS from the beginning), but your port 465 is responding just like port 25/587.
And your Fortigate on HTTPS port 443 is serving a self-signed cert: