Hi, > I have temporarily stopped the error by turning tls off in the avelsieve > plugin, but > I'm wondering if there is something I can do to fix either timsieved > (cyrus) or > Berkeley DB (currently 4.3.28-2tr) so that I can get around this problem. > > Anyone else have this trouble? Any solutions/patches?
Not exactly this trouble, but trouble with postfix with SASL/TLS. I've just "migrated" one TSL 3.0 server to new TSL 3.0.5 one, with identical settings, that worked like a charm on the old system. Theese messages i've found in /var/log/mail/warnings: Sep 28 10:50:07 ns postfix/smtpd[4620]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasl/sasldb: Permission denied Sep 28 10:50:07 ns postfix/smtpd[4620]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasl/sasldb: Permission denied Sep 28 10:50:07 ns postfix/smtpd[4620]: warning: SASL authentication failure: Password verification failed Sep 28 10:50:07 ns postfix/smtpd[4620]: warning: unknown[192.168.10.55]: SASL PLAIN authentication failed Sep 28 10:50:07 ns postfix/smtpd[4620]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasl/sasldb: Permission denied Sep 28 10:50:07 ns last message repeated 3 times Sep 28 10:50:07 ns postfix/smtpd[4620]: warning: unknown[192.168.10.55]: SASL LOGIN authentication failed When I tried testsaslauthd, it worked with OK status and when I tried to chang permissions on /etc/sasl/sasldb to 777, messages turned to theese: Sep 28 12:09:03 ns postfix/smtpd[8048]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasl/sasldb: Bad file descriptor So it looks like BerkleyDB is involved in TSL 3.0.5 beta2... Cheers -- Jaroslav Vrbicky _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
