d00p
commented
1 year ago Froxlor is using a self-signed certificate for email/IMAP, rather than issuing certificates via Let's Encrypt on a per-domain basis as expected.
Sorry we dont meet your expectations, nowhere do we mentioned that an e-mail per-domain certificate config is being provided. As ssl as well as Let's Encrypt are options which can be enabled and disabled as desired, we cannot safely include corresponding certificate directives (also at configuration time, there might not even be a certificate generated at all).
The mailservices are meant be to be used with the system-hostname you've specified in the installation process and the corresponding configs can be adjusted as you like, we just provide a working "base".
If you want/need a per-domain-ssl-certificate for postfix and dovecot you can do that if you want to.
Long story short: not a bug, intended behaviour/configuration
Describe the bug
Froxlor is using a self-signed certificate for email/IMAP, rather than issuing certificates via Let's Encrypt on a per-domain basis as expected. This behavior is inconsistent with the SSL certificate issuance for my web domains, which seems to work correctly.
System information
Froxlor version: 2.0.20 Web server: NGINX POP/IMAP server: Dovecot OS/Version: Ubuntu/22.04
To Reproduce
Configure Froxlor with multiple domains. Enable Let's Encrypt for automatic SSL certificate issuance. Configure mail services (Dovecot/Postfix) for IMAP. Observe that all IMAP connections use the same self-signed certificate, regardless of domain. Expected behavior Each domain should have its own SSL certificate issued by Let's Encrypt, which should be used for securing IMAP connections.
Additional context I suspect this might be a configuration issue within Froxlor, where it's not correctly setting up Let's Encrypt for per-domain certificate issuance for email/IMAP. This issue could potentially impact SMTP as well.