Hi guys, I know this is pretty old stuff by now, but I updated my mail server yesterday to 7.2 and of course experienced the very same behavior. Should have looked faster into the mail archives :)
Anyway, is this something that’s being worked on? Does it help to file a bug with postfix? For now I reverted to file based dictionaries, which is of course not very nice, but the installation is rather small and static. Would be nice to have Postgres in the loop again. Best regards Stephan > Am 01.11.2022 um 13:32 schrieb Stuart Henderson <s...@spacehopper.org>: > > On 2022/11/01 12:58, Marc Peters wrote: >> On Sun, Oct 30, 2022 at 09:13:19AM +0000, Stuart Henderson wrote: >>> Seems there is still some conflict between Postfix 3.7 (which needs >>> OpenSSL) and libraries (like libpq) using LibreSSL, despite the static >>> linking. (the upstream developer of TLS code in Postfix is also an >>> OpenSSL developer and seems to prefer using OpenSSL APIs which LibreSSL >>> doesn't have yet). >>> >>> If you have the ports tree on your machine you can unpack the attached >>> file under /usr/ports/mail/postfix, pkg_delete postfix, and build a 3.5 >>> version from /usr/ports/mail/postfix/stable35 with "FLAVOR=pgsql make >>> install". >> >> Hi, >> >> i saw the same behaviour on my mailserver but used the excuse to move to >> opensmtpd and reworked the setup in general. Maybe this should be mentioned >> on the upgrade page for users as a heads up? > > We are trying to figure out what to do with this. > > Brad, you didn't answer my other mail so I ask again: how about I commit > stable35 to the tree for now?
