On Tue, 2006-08-29 at 11:58 -0400, Shelley Waltz wrote:
my distro (cyrus-imapd-2.2.3-4) does not appear to have db_recover?
It's from the Berkeley DB tools; db4-utils on RHEL.
Wil
--
Wil Cooley [EMAIL PROTECTED]
Naked Ape Consulting, Ltd
signature.asc
Description: This is a digitally signed
On Tue, 2006-08-29 at 11:22 -0400, Shelley Waltz wrote:
Aug 24 10:50:33 chipmunk lmtpunix[18963]: DBERROR: opening
/var/lib/imap/deliver.db: Cannot allocate memory
Aug 24 10:50:33 chipmunk lmtpunix[18963]: DBERROR: opening
/var/lib/imap/deliver.db: cyrusdb error
Aug 24 10:50:33 chipmunk
I have read many threads regarding issues with deliver.db being in Berkeley
DB format. I am running cyrus-imapd-2.2.3-4 on Redhat AS3. I have not
had any issues with deliver.db until last week. I have about 200 accounts
with
most at 250MB, some at 500MB and a few at 1GB.
The issue started with
Use db_recover
Shelley Waltz wrote:
I have read many threads regarding issues with deliver.db being in Berkeley
DB format. I am running cyrus-imapd-2.2.3-4 on Redhat AS3. I have not
had any issues with deliver.db until last week. I have about 200 accounts
with
most at 250MB, some at
my distro (cyrus-imapd-2.2.3-4) does not appear to have db_recover?
Rafael Alcalde said:
Use db_recover
Shelley Waltz wrote:
I have read many threads regarding issues with deliver.db being in
Berkeley
DB format. I am running cyrus-imapd-2.2.3-4 on Redhat AS3. I have not
had any
On 29 Aug 2006, at 11:22, Shelley Waltz wrote:
My question is - should I convert the deliver.db to skiplist? If I
simply
move it elsewhere and change the imapd.conf to use a deliver.db in
skiplist
and restart, what is lost? Surely this huge db contains information
necessary and useful to
