1

Topic: iRedMail-1.8.10 has been released.

Dear all,

iRedMail-1.8.10 has been released.

Here's major changes since iRedMail-1.8.9:

Supports new distribution release
  • OpenBSD 8.0. OpenBSD 7.9 and earlier releases have been dropped.

Updated packages

And do not forget to update PHP packages to fix the critical vulnerabilities: https://forum.iredmail.org/topic21232.html

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: iRedMail-1.8.10 has been released.

I think the Roundcube 1.7.6 release is BAF.
The file copy completes, then the database upgrade fails yielding an unusable system.
I had to fall-back to 1.7.5

Additionally, the Roundcube patches fail to apply using the "./bin/installto" technique as it fails to adequately match the current version. I had to manually edit the file  <INSTALLDIR>/program/include/iniset.php to fix the version and add the correct version.
For example, the setting
define('RCMAIL_VERSION', "1.7-git");
has to change to
define('RCMAIL_VERSION', '1.7.5');

then the patches since at least 1.7.4 apply successfully

3

Re: iRedMail-1.8.10 has been released.

jchimene wrote:

define('RCMAIL_VERSION', "1.7-git");

Did you ever download git version and upgrade?

4 (edited by jchimene Yesterday 19:51:39)

Re: iRedMail-1.8.10 has been released.

ZhangHuangbin wrote:
jchimene wrote:

define('RCMAIL_VERSION', "1.7-git");

Did you ever download git version and upgrade?


It's updated following the Roundcube instructions. Basically, "wget <tar.gz from repo> <local>"

Looking at the source in github, the "-git" semantic version is there.

Anyway, that's only part of the issue: the SQL schema upgrade fails in 1.7.6
It's quite reproducible.

This answer assumes I know what you're asking. Maybe I misunderstood your question?

Even more on the patch issue. I'm guessing these are AI-generated issues (1.7.4-.6) upstream is responding to. I think their upgrade procedure breaks in the face of sub-version increments. If you look at recent releases, they've changed the semantic version to address this. However, on MAIN, they're back to "1.8-git"; when what I think they want is "1.8.0-git" or something like that.