In case anyone else has the problem.. It is the dreaded db3 problem with
Redhat's links.Had to search the list archives to find it. The sasl
libraries build fine using the db3 headers but I could'nt get cyrus-imap to
compile the deliver program properly using the db3 headers and library. I
had to make a link for /usr/lib/libdb.so to point to libdb1.so in order and
use CPPFLAGS=-I/usr/include/db2 and LDFLAGS=-L/usr/lib . Redhat puts a link
in /lib/libdb.so to point to the db3 library file but the cyrus-imapd
configure just would work or compile properly with the include db3 library.
Had to use the db1 one. All is fine now. If anyone has a better fix or a
better explanation, let me know.
Do intend to move to 2.0.12 eventually but am waiting for all db related
issues to be resolved.
Alain
----- Original Message -----
From: "Alain Turbide" <[EMAIL PROTECTED]>
To: "Cyrus Mailinglist" <[EMAIL PROTECTED]>
Sent: Monday, March 05, 2001 9:11 AM
Subject: Redhat 7.0 + Cyrus Imap 1.6.25 deliverdb problem
> Can anyone shed some light on this problem I'm having. Whenever a message
> needs to be delivered to more then one recipient in the same deliverdb
> database file I get a "resource not available" message from the deliver
> process (in LMTP mode) and the message remains queued. Seems like a db
> locking problem to me.. The deliver.db files do get created and seem to
work
> ok for duplicate message suppression but I still get this error. I've
> recompiled cyrus to use the db1 header files instead of the db3 includes
and
> still the same problem. The only difference I really see is when I run
> configure. The dbopen function never gets located on Redhat 7.0 but is ok
> on a Redhat 6.2 system. The messages do get delivered eventually but
takes
> a few runs of the queue first. One more weird sympton is that the
vacation
> replies totally ignore the days setting and always send a reply to every
> message.
>
> Yes I know I should upgrade to 2.0.x eventually but I'm ready yet to
switch
> over my production system to it.
>
>
