Re: SASL libraries not taken in account when compiling on AIX

--0IvGJv3f9h+YhkrH
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 16, 2004 at 02:44:50PM +0200, Andreas Winkelmann wrote:
> Am Donnerstag, 16. September 2004 13:58 schrieb Jerome Walter:
> > It is, so it is compiled in statically (no reason why, but anyway, i
> > don't care).
>=20
> This is Wietse's nightmare ;-)

Poor of him ;)=20
Anyway, as long as it works even statically linked, i see no problem
with it ;)

> Check, which Mechanisms do you have installed in /usr/lib/sasl2.
=20
root@mail:/home/walter# ls /usr/lib/sasl2
deactivated libcrammd5.la liblogin.la libplain.la
libanonymous.a libdigestmd5.a libotp.a libsasldb.a
libanonymous.la libdigestmd5.la libotp.la libsasldb.la
libcrammd5.a liblogin.a libplain.a smtpd.conf

Should be enough ;) But should also be restricted by mech_list in
smtpd.conf

> Check if Postfix filters some of them smtpd_sasl_security_options.
> Show "postconf -n".

No smtpd_sasl_security_options.=20

postconf -n | grep smtpd_sasl
smtpd_sasl_application_name =3D smtpd
smtpd_sasl_auth_enable =3D no
smtpd_sasl_local_domain =3D $mydomain

> I hope, it comes clear with the static libsasl. Or maybe the mechanisms a=
re=20
> included, too? (horror)

I fear. This AIX is definitively alive and trying to get me mad ;)

is there a way to check ? Some labels that would appear from sasl being
present in smtpd ?


Best regards,

Jerome Walter
--=20
-+-- Jerome Walter - EFREI p2004 ----+-
Mail *is* private

--0IvGJv3f9h+YhkrH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBSaGk+i7U/c9vdcYRAjOeAJwLZx+LwKAq2XOvTXOztKdSSZkQWgCeKMHC
kW/5hHxf7Us/B8CB5jVG4+4=
=4I1v
-----END PGP SIGNATURE-----

--0IvGJv3f9h+YhkrH--