Github messages for voidlinux
 help / color / mirror / Atom feed
From: dezifit <dezifit@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] postfix - wrong runtime version of libssl
Date: Tue, 25 Jun 2024 12:43:02 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50987@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]

New issue by dezifit on void-packages repository

https://github.com/void-linux/void-packages/issues/50987

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.35_1 x86_64-glibc

### Package(s) Affected

postfix-3.8.5_1, libssl3-3.3.0_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

would be nice if postfix won't log a version mismatch warning on every incoming mail and could handle TLS connections

### Actual behaviour

postfix immediately complains about a version mismatch:
```
warning: run-time library vs. compile-time header version mismatch: OpenSSL 3.3.0 may not be compatible with OpenSSL 3.1.0
```

and fails to accept TLS connections
```
connect from internet.nl[62.204.66.10]
SSL_accept error from internet.nl[62.204.66.10]: -1
warning: TLS library problem: error:0A000102:SSL routines::unsupported protocol:ssl/statem/statem_srvr.c:1743:
lost connection after STARTTLS from internet.nl[62.204.66.10]
```
which may be related to the version issue

### Steps to reproduce

just check the pkg versions or install and configure everythings to see the log messages yourself

             reply	other threads:[~2024-06-25 10:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 10:43 dezifit [this message]
2024-06-25 13:21 ` MIvanchev
2024-06-29  4:06 ` [ISSUE] [CLOSED] " classabbyamp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50987@inbox.vuxu.org \
    --to=dezifit@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).