iRedMail — iRedMail Enterprise Edition (EE) v1.3.0 has been released.

Re: iRedMail Enterprise Edition (EE) v1.3.0 has been released.

null@example.com (ZhangHuangbin) — Mon, 26 May 2025 10:20:37 +0000

OK.
But for now, you have to replace cert files manually:

- Private key: /opt/iredmail/ssl/key.pem
- Cert: /opt/iredmail/ssl/cert.pem
- Full chain: /opt/iredmail/ssl/combined.pem

Better copy combined.pem to cert.pem directly. And EE uses just private key and full chain files since v1.3.0.

Re: iRedMail Enterprise Edition (EE) v1.3.0 has been released.

null@example.com (dalex) — Mon, 26 May 2025 09:16:32 +0000

Let's Encrypt is not the only certificate provider! User may have other paid source with validity of one or more years (no update every 2 months). Or may have a central Let's Encrypt issuer account, managing many domains at once.

Re: iRedMail Enterprise Edition (EE) v1.3.0 has been released.

null@example.com (ZhangHuangbin) — Mon, 26 May 2025 08:16:56 +0000

Understand now.
But why not use the Let's Encrypt one directly?

Re: iRedMail Enterprise Edition (EE) v1.3.0 has been released.

null@example.com (dalex) — Mon, 26 May 2025 06:31:08 +0000

Two [text boxes] to paste the CRT/KEY text, or two [select file to upload] boxes, so we can upload our domain certificate to the server.

Re: iRedMail Enterprise Edition (EE) v1.3.0 has been released.

null@example.com (ZhangHuangbin) — Mon, 26 May 2025 00:36:58 +0000

dalex wrote:

Two fields for the CRT/KEY entry followed by daemons restart.

Excuse me, what do you mean by "two fields"?

Re: iRedMail Enterprise Edition (EE) v1.3.0 has been released.

null@example.com (dalex) — Sun, 25 May 2025 08:29:22 +0000

SSL certificates:

What if we have our own certificates? Can you add a relevant section there:

Two fields for the CRT/KEY entry followed by daemons restart.

Thanks.

Re: iRedMail Enterprise Edition (EE) v1.3.0 has been released.

null@example.com (TiTo) — Fri, 23 May 2025 13:14:13 +0000

Of course, I performed the upgrade first, and only then proceeded with certificate management. In the support ticket, I already provided a detailed explanation starting from the moment of the upgrade onward.

I want to emphasize that I first completed the upgrade, received a message confirming that the deployment of the new version succeeded, and only after that did I proceed to manage SSL certificates.

Re: iRedMail Enterprise Edition (EE) v1.3.0 has been released.

null@example.com (ZhangHuangbin) — Fri, 23 May 2025 06:23:47 +0000

After upgraded the binary program (/usr/local/bin/iredmail), please login to EE web ui as global admin, then click "Upgrade" button to finish the upgrade. After that, SSL cert management will work as expected.

It's a mistake that Dovecot was configured to use /opt/iredmail/ssl/cert.pem instead of /opt/iredmail/ssl/combined.pem (full chain), and EE doesn't generate "cert.pem" with requested certificate. This is why this issue occurred.

Re: iRedMail Enterprise Edition (EE) v1.3.0 has been released.

null@example.com (TiTo) — Thu, 22 May 2025 21:01:37 +0000

Alright, I’ve identified the issue.

Previously, I had certificates generated via Certbot. However, after requesting new certificates through the iRedMail EE 1.3.0 web interface, two new certificate files were created:
ok: /opt/iredmail/ssl/key.pem [723.391µs]
ok: /opt/iredmail/ssl/combined.pem [753.437µs]
The Dovecot configuration (dovecot.conf) still referenced the old certificate path, which caused the TLS handshake to fail. I’ve now commented out the outdated ssl_cert line and replaced it with the correct path to the newly generated combined.pem:

## ssl_cert = ssl_cert = ssl_key = #ssl_ca =

After restarting Dovecot, everything is working as expected.

Re: iRedMail Enterprise Edition (EE) v1.3.0 has been released.

null@example.com (TiTo) — Thu, 22 May 2025 19:49:58 +0000

After upgrading to iRedMail EE version 1.3.0, I can no longer access IMAP through the Roundcube webmail interface
Pls. I need urgent help

May 22 21:39:08 xxxxxxxxxxxxxxxxxxx roundcube[1480]: IMAP Error: Login failed for xxxxxxxxxxxxxxxxxxx against 127.0.0.1 from xxxxxxxxxxxxxxxxxxx. Unable to negotiate TLS in /opt/www/round>
May 22 21:39:08 xxxxxxxxxxxxxxxxxxx dovecot[1384]: imap-login: Disconnected: Connection closed: SSL_accept() syscall failed: Invalid argument (no auth attempts in 0 secs): user=<>, rip=127.>
May 22 21:39:07 xxxxxxxxxxxxxxxxxxx dovecot[1384]: imap-login: Disconnected: Connection closed: SSL_accept() failed: error:0A000076:SSL routines::no suitable signature algorithm (no auth at>
May 22 21:39:07 xxxxxxxxxxxxxxxxxxx dovecot[1384]: imap-login: Disconnected: Connection closed: SSL_accept() failed: error:0A0000C1:SSL routines::no shared cipher (no auth attempts in 0 sec>

iRedMail Enterprise Edition (EE) v1.3.0 has been released.

null@example.com (ZhangHuangbin) — Thu, 22 May 2025 03:18:30 +0000

A Heartfelt Thank You to Our iRedAdmin-Pro and iRedMail Easy Customers

EE is our flagship product and it replaces iRedMail, iRedAdmin-Pro, and iRedMail Easy with a single binary. Easy to install, also offers one-click upgrades support. We strongly recommend deploying new servers with EE or migrating existing setups from iRedMail or iRedMail Easy to EE.
---

iRedMail Enterprise Edition (EE) v1.3.0 has been released, with SSL Cert Management. All customers are recommended to upgrade as soon as possible.

- Full list of changes: https://docs.iredmail.org/ee.changelog.html
- Upgrade: https://docs.iredmail.org/upgrade.ee.html
- Deploy a new server: https://docs.iredmail.org/install.ee.html
- Features and pricing: https://www.iredmail.org/ee.html

## Migration Guides

- Migrate from a server deployed with the downloadable iRedMail installer:
https://docs.iredmail.org/iredmail.to.ee.html

- Migrate from a server deployed with iRedMail Easy:
https://docs.iredmail.org/easy.to.ee.html

Best regards,
The iRedMail Team