• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Require SMTPS on Dovecot

fmdeveloper

New Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian v18.0.79_build1800260720.04
Currently running Dovecot on Ubuntu 22.04.5 LTS. The cyber insurance company is flagging the server for running "Email Service without SSL/TLS." The server is set up to send through a specific IP, and the IP being flagged is a site IP. Is there any way to either a) block the site IP from responding to port 25, or b) require all SMTP traffic to be over SSL/TLS? SSL/TLS is enabled on the service.

Thanks in advance.
 
Dovecot is use for IMAP/POP3. For SMTP the default service is usually Postfix but it's possible you are using Qmail. You can check under Services Management for SMTP Server.

In either case, by default, Postfix should be using TLS on port 25 when communicating but to enforce it to only do that requires manual configuration iirc. Not sure about Qmail since I've never used it before.
 
Dovecot is use for IMAP/POP3. For SMTP the default service is usually Postfix but it's possible you are using Qmail. You can check under Services Management for SMTP Server.

In either case, by default, Postfix should be using TLS on port 25 when communicating but to enforce it to only do that requires manual configuration iirc. Not sure about Qmail since I've never used it before.
Using Postfix. I'll see if I can find a guide on enforcing TLS on Postfix.
 
Here's what I did.

sudo nano /etc/postfix/main.cf

Change:
smtpd_tls_security_level = encrypt

I had issues with delivery after that, so I had to disable the line:

#content_filter = smtp-amavis:[127.0.0.1]:10024

The error I was getting was:

Must issue a STARTTLS command first at (eval 121) line 1283
***
Does anyone know why Amavis is throwing that error with this configuration?
 
We don't use Amavis at all, but maybe (you can run your own verification process to check) Amavis is throwing that error, because setting smtpd_tls_security_level = encrypt in your main.cf file, enforces mandatory TLS globally across the entire Postfix system doesn't it? Therefore, this restriction would apply to local internal services, including the loop back interface where Amavis passes its filtered mail back to Postfix. So when Amavis handles your email & attempts to inject it back into Postfix (port 10025?) the Postfix smtpd service on that port, would demand encryption first, but... isn't the local loop back traffic between Amavis and Postfix unencrypted by default? If yes, that, would make Amavis fail to comply & crash with error messages. Assuming this is so (to be verified by yourself) you would just need to explicitly tell Postfix to disable mandatory TLS for internal Amavis loops to fix it... There's a lot of online posts (fixes) on this subject, if, this is indeed, the case.
 
Back
Top