On 10/17/05, Febo Aristots <[EMAIL PROTECTED]> wrote:
>
> >From: Febo Aristots <[EMAIL PROTECTED]>
> >Date: Oct 17, 2005 6:16 PM
> >Subject: db4 problems with cyrus 2.1.16
> >To: info-cyrus@lists.andrew.cmu.edu
>
> >I have had a bad problem with a seemingly corrupted mailboxes.db with
> cyrus-imap
>From: Febo Aristots <[EMAIL PROTECTED]>>Date: Oct 17, 2005 6:16 PM>Subject: db4 problems with cyrus
2.1.16>To: info-cyrus@lists.andrew.cmu.edu>I have had a bad problem with a seemingly corrupted mailboxes.db with cyrus-imap 2.1.16
I seem to have solved the problem this way:
- stopping cyrus
- I
Andrew Morgan wrote:
On Mon, 17 Oct 2005, Nick Trenary wrote:
Cyrus imapd v2.2.12 and Squirrelmail v1.4.5 running on OS X server
10.4.2. I've been having intermittent problems with our imap server
since day 1. The problem appears to occur when users logged into
Squirrelmail try to move mail
On Mon, 17 Oct 2005, Nick Trenary wrote:
Cyrus imapd v2.2.12 and Squirrelmail v1.4.5 running on OS X server 10.4.2.
I've been having intermittent problems with our imap server since day 1. The
problem appears to occur when users logged into Squirrelmail try to move mail
from one mailbox to a
Cyrus imapd v2.2.12 and Squirrelmail v1.4.5 running on OS X server
10.4.2. I've been having intermittent problems with our imap server
since day 1. The problem appears to occur when users logged into
Squirrelmail try to move mail from one mailbox to another. For whatever
reason the imapd pro
I have had a bad problem with a seemingly corrupted mailboxes.db with cyrus-imap 2.1.16
the problem started with this log entries:
Oct 17 03:27:21 mail ctl_cyrusdb[9217]: DBERROR db4: DB_LOGC->get: log record ch
ecksum mismatch
Oct 17 03:27:21 mail ctl_cyrusdb[9217]: DBERROR db4: DB_LOGC->get: cat