1 (edited by Neovana 2025-01-16 17:59:49)

Topic: OpenBSD 7.6 and iRedMail 1.7.2

Congratulations, it looks like you've just updated iRedMail to 1.7.2 (but the announcement post isn't out yet). Please let me know if OpenBSD 7.6 is recommended (main page lists 7.5).

----

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

2 (edited by Neovana 2025-01-15 18:30:35)

Re: OpenBSD 7.6 and iRedMail 1.7.2

# wget -O /usr/local/bin/fail2ban_banned_db https://raw.githubusercontent.com/iredmail/iRedMail/1.7.2/samples/fail2ban/bin/fail2ban_banned_db

https://raw.githubusercontent.com/iredm … _banned_db

Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.111.133,

185.199.108.133, 185.199.109.133, ...

Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.111.133|:443... connected.

HTTP request sent, awaiting response... 404 Not Found

I think this link works:

https://raw.githubusercontent.com/iredm … _banned_db

3

Re: OpenBSD 7.6 and iRedMail 1.7.2

Neovana wrote:

Congratulation, it looks like you've just updated iRedMail to 1.7.2 (but the announcement post isn't out yet). Please let me know if OpenBSD 7.6 is recommended (main page lists 7.5).

We're preparing iRedMail v1.7.2, release note and upgrade tutorial are ready, just need to tag the version in git repo.

And yes OpenBSD 7.6 is recommended with v1.7.2, 7.5 was dropped.

In the meantime, new iRedAdmin-Pro is ready too. More important thing is, first stable release of iRedMail Enterprise Edition ("EE" for short) v1.0.0 is coming, and we have good news for iRedAdmin-Pro license owners and iRedMail Easy subscribers (annual subscription only).

4 (edited by Neovana 2025-01-16 18:25:40)

Re: OpenBSD 7.6 and iRedMail 1.7.2

I upgraded to 1.7.2 and OpenBSD 7.6.

I am experiencing issues with: mimmjadminuwsgil, iredadminuwsgil, and fail2ban. During boot, the following errors are produced:

starting package daemons: postgresql nginx php81_fpm dovecot clamd freshclam amavisd postfix mimmjadminuwsgi[1287]: pinsyscalls addr 45a52ec4259 code 253, pinoff Oxffffffff (pin 330 45a7d5ee000-45a7d5fc66d e66d) (libcpin 0 0-0 0) error 78 (failed) iredapd iredadminuwsgi[91938]: pinsyscalls addr c99aa8ac259 code 253, pinoff Oxffffffff (pin 330 c99122a4000-c99122b266d e66d) (libcpin 0 0-0 0) error 78 (failed) fail2ban(failed) gemu_ga.
starting local daemons: cron.

Additionally, after login - when I try to run:

doas fail2ban-client -x reload

I get the following error:

Traceback (most recent call last):
  File "/usr/local/bin/fail2ban-client", line 34, in <module>
    from fail2ban.client.fail2banclient import exec_command_line, sys
ModuleNotFoundError: No module named 'fail2ban'

I've also received an email from root on the server with the following error message:

Subject: Cron <root@mail> /usr/local/bin/bash /usr/local/bin/fail2ban_banned_db unban_db
Body: ld.so: psql: can't load library 'liblzma.so.2.2'

All system patches have been applied and all packages are updated. The issue persists after rebooting.

It looks like I have a file /usr/local/lib/liblzma.so.2.3, so I tried:

doas ln -s /usr/local/lib/liblzma.so.2.3 /usr/local/lib/liblzma.so.2.2

I also tried replacing the shabang line in doas nano /usr/local/bin/fail2ban_banned_db to:

#!/usr/local/bin/bash

Neither helped.