From: Tony Earnshaw (tonyebilly.demon.nl)
Date: Sat Apr 02 2005 - 13:36:34 CST

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

Thomas A. Luther:

> Summary:
>
>
> Posfix works fine until I uncomment the line smtpd_sasl_auth_enable
> =
> yes in the main.cf file. Then postfix dies with the error:
>
> Apr 2 10:24:18 spamfilter postfix/master[6750]: warning: process
> usr/libexec/postfix/smtpd pid 7482 killed by signal 11 Apr 2
> 10:24:18 spamfilter postfix/master[6750]: warning:
> /usr/libexec/postfix/smtpd: bad command startup -- throttling

I'm a RHAS3 person (also postfix 2.1.5 and greater, SMTP AUTH via
Cyrus SASL).

Looks like you're pulling in SASL 1 stuff.

1: ldd on the smtpd binary?

> ==============================
> Situation:
> RedHat 3.0 ES

O.k. Updates (there are 43 possible updates)?

> Postfix 2.1.5

2: Where from? Source or rpm? Whose rpm?

> Sasl 2.1.15

Is buggy, should be at least 2.1.20. Should work, though,

At the moment (it will change) I compile almost all my non Red Hat
stuff from source (Samba 3 is one exception, srpm). As much as
possible of the source code installs goes into /usr/local, so's not
to conflict with the Red Hat stuff. When I compile pure source code,
I point my configure (or ENV) at the /usr/local headers and
libraries.

As far as Cyrus SASL goes, I have these SASL headers on my RHAS3
test machine:

/usr/local/include/sasl/sasl.h ## Cyrus SASL 2 2.1.20 source install
/usr/include/sasl/sasl.h ## Red Hat SASL2
/usr/include/sasl.h ## Red Hat SASL1

You have to keep the one from the other during a compile,
unfortunately I guess you didn't.

Answers to the above 2 questions?

--Tonni

--
mail: tonyebilly.demon.nl
http://www.billy.demon.nl

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