On Mon, Oct 03, 2022 at 08:43:18PM +0000, Martin wrote:
> yes, I'm afraid that's true, these are the contents of that old
> directory (I renamed it and put a symbolic link to the sbin directory carrying
> the current executables):
> root@jerakeen:/usr/libexec/postfix/sbin.OLD# find . -type f -print |
> while read file; do echo -n "$file -> "; strings $file | grep
> mail_version; done | grep 3.
> ./oqmgr -> mail_version=3.4.13
> ./fsstone -> mail_version=3.4.13
> ./flush -> mail_version=3.4.13
> ./tlsproxy -> mail_version=3.4.13
> ./postscreen -> mail_version=3.4.13
> ./bounce -> mail_version=3.4.13
> ./postfix-script -> ./verify -> mail_version=3.4.13
> ./smtpd -> mail_version=3.4.13
> ./scache -> mail_version=3.4.13
> ./showq -> mail_version=3.4.13
> ./qmqpd -> mail_version=3.4.13
> ./anvil -> mail_version=3.4.13
> ./spawn -> mail_version=3.4.13
The system is fairly well messed up. If by a miracle only Postfix is
broken, and nothing, else, then save the config files, and fully remove
all Postfix-related packages and residual executables, ... Then
re-install the correct package.
Perhaps you previously had a "backports" package that uses a non-default
release label, and it persisted across the upgrade... You may need to
also look at the configs (IIRC) /etc/apt.d/ to see what release pins
and preferences you have in place...
Recovering a messed up system is an art. Good luck. If you can afford
some down time, I'd attempt to save all user data and do a clean
reinstall.
The problem isn't the symlinks, it is multiple conflicting Postfix
builds.
--
Viktor.
