1

Topic: Postfix connection fail after OpenSSL upgrade to version 3.5.1

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.7.4
- Deployed with iRedMail Easy or the downloadable installer? Downloadable installer
- Linux/BSD distribution name and version: Rocky Linux 9.6
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

In a recent recent Rocky Linux update OpenSSL was upgraded from version 3.2 to version 3.5. This resulted in Postfix generating the following error:

postfix/amavis/smtp[10244]: warning: run-time library vs. compile-time header version mismatch: OpenSSL 3.5.0 may not be compatible with OpenSSL 3.2.0'

The end result is that mail is no longer accepted, postfix on 127.0.0.1 generates a 'Connection refused' error.


Is this a known problem? Is it possible to compile Postfix to support OpenSSL 3.5?

----

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

2

Re: Postfix connection fail after OpenSSL upgrade to version 3.5.1

I'm running Rocky Linux 10 and get the same messages and don't have an issue with Postfix.

3

Re: Postfix connection fail after OpenSSL upgrade to version 3.5.1

Different versions of Postfix.
RL9    -  Postfix 3.5
RL10  -  Postfix 3.7

Postfix 3.7 natively supports OpenSSL 3.x while Postfix 3.5 has OpenSSL 3.0 compatibility support.
Postfix 3.5 lacks full native support for some new features and changes introduced in OpenSSL 3.

So I guess chances of it working with OpenSSL 3.5 are much higher on RL10.This could mean that iRedMail smtp functionality will not work on an updated RL9 system. I am wondering if I'm the only one encoutering this issue.

4

Re: Postfix connection fail after OpenSSL upgrade to version 3.5.1

Seems like more ppl are having the same issue:

issues.redhat.com/browse/RHEL-128018

Guess we'll have to wait until Red Hat fixes it