From: Andreas Winkelmann (mlawinkelmann.de)
Date: Fri Jul 14 2006 - 10:43:58 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Am Friday 14 July 2006 00:59 schrieb Technical Support:

> I'm having a strange problem with SASL. Using the following
> configuration information for SASL:
>
> ./configure --enable-cram --disable-digest --disable-otp \
> --disable-krb4 --disable-gssapi --enable-plain --disable-anon \
> --enable-login --disable-pwcheck --with-gnu-ld --without-pam \
> --without-saslauthd --with-bdb-libdir=/usr/local/BerkeleyDB.4.4/lib\
> --with-bdb-incdir=/usr/local/BerkeleyDB.4.4/include
>
> And the following make information for postfix:
>
> make makefiles CCARGS="-DUSE_SASL_AUTH -DUSE_CYRUS_SASL \
> -I/usr/local/include/sasl" AUXLIBS="-L/usr/local/lib -lsasl2"
>
> This used to worked just fine until I was forced to update software.
> I'm using the today's snapshots for everything. So now EHLO responds
> with the following mechanisms:
>
> 250-AUTH GSSAPI DHX
>
> Because of the configuration options set in SASL, I would have
> expected the following instead:
>
> 250-AUTH CRAM-MD5
>
> What's worse, there appears to be no authentication mechanism, even
> for plain AUTH. Relaying is denied exactly as if I hadn't bothered
> installing SASL at all. Does anyone have any ideas what might be
> happening?

Did you check if there is another Cyrus-SASL Installation on your system?

Run "ldd" or similar on smtpd.

--
        Andreas

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]