>>>>> On April 1, 2026 Viktor Dukhovni via Postfix-users 
>>>>> <[email protected]> wrote:

> First step is to find out where the missing plugins are or to
> install them if not installed.  The relevant Debian package is
> rumoured to be "libsasl2-modules".

Hi Victor, thank you for the reply,

It looks like while both debian 10 and testing/14 have a dependency of
the postfix package on libsasl2-2, in both cases libsasl2-2 merely
recommends libsasl2-modules.  Also, postfix merely suggests
libsasl2-modules in both cases.

However, for some reason on my debian 10 system, it shows
libsasl2-modules having been installed automatically:

% aptitude why libsasl2-modules
i   postfix    Depends    libsasl2-2 (>= 2.1.27+dfsg)                
i A libsasl2-2 Recommends libsasl2-modules (>= 2.1.27+dfsg-1+deb10u2)

% aptitude search libsasl2-modules
i A libsasl2-modules       - Cyrus SASL - pluggable authentication modules

I am curious that it shows installed automatically on my debian 10
system, as I don't understand why based on the dependencies.

but on my testing/14 system, it had not been installed.

After installing libsasl2-modules on the new system, the problem with
relaying is fixed.

CC'ing Michael Tokarev, the Debian package maintainer.

IMO it seems like maybe postfix should require libsasl2-modules, the
300kB is well spent if you're installing postfix, rather than silently
failing.

But it might also make sense to update this text of SASL_README:

| This same error message will also be logged when the libplain.so or
| liblogin.so modules are not installed in the /usr/lib/sasl2 directory

as that directory is not necessarily correct (for me it is
/usr/lib/x86_64-linux-gnu/sasl2/), and it would be good to mention the
package name for the most popular distros (libsasl2-modules),
especially noting that the package may not be a postfix dependency and
may need to be manually installed on some distros.

thank you both,
Greg
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to