Ok, I recompiled every library Postfix depends on (compiling pam and cyrus-sasl against db4.1 and openldap with gdbm as it otherwise wouldn't build), then postfix itself, and it still doesn't work.
Immediately upon startup, and whenever I try to send a message, I get these in /var/log/mail/warnings: Jul 5 16:52:39 mario postfix/master[21325]: warning: process /usr/lib/postfix/pickup pid 21330 killed by signal 11 Jul 5 16:52:39 mario postfix/master[21325]: warning: /usr/lib/postfix/pickup: bad command startup -- throttling Jul 5 16:52:39 mario postfix/master[21325]: warning: process /usr/lib/postfix/nqmgr pid 21331 killed by signal 11 Jul 5 16:52:39 mario postfix/master[21325]: warning: /usr/lib/postfix/nqmgr: bad command startup -- throttling and telnet localhost 25 doesn't give a version string. Is this a SASL thing, or is glibc broken (maybe that explains libao too, seems to die on a pthreads call)? David Walser wrote: > I am in the midst of recompiling every library Postfix depends on. I notice that > the pam binary is compiled against db4.0, could that be the problem? Or is this a > sasl thing, due to the fact that both versions of that are linked? > > David Walser wrote: >> If I try to run the package in Cooker, I get messages in the log that every child >> process of it segfaults (killed by signal 11). >> >> I recompiled the package myself, and it doesn't send anything to the logs in >> /var/log/mail, and it also doesn't work. >> >> If I use the mail command to send mail to myself, I don't get any mail, and the >> sendmail command segfaults.
