Corrupt IMAP Mailbox - time critical, appreciate any help!
Simon Matter
simon.matter at ch.sauter-bc.com
Thu Dec 18 03:07:01 EST 2003
> Setup is based on Andrew Koros':
> Postfix+Cyrus+PostgreSQL+Web-cyradm+RedHat
>
> My ver of cyrus is listed at bottom of this post.
>
> I am in a bind due to a disk gone corrupt on our RAID5 array. We had to
> fsck the filesystems. Most mailboxes and users are now working fine
> again after doing some reconstructs. However, there are a few critical
> issues that I cannot seem to fix. Here is what I have done:
>
> (As Cyrus User)
> /usr/lib/cyrus-imapd/reconstruct user/john.smith.somewhere.com
Hi,
Did you try running 'reconstruct -r' ? It looks like there is still
something corrupt.
Simon
>
> Reconstruct seemed to work for the most part. I can now successfully
> login via IMAP with this user account. I can download and read
> messages, etc.
>
> HOWEVER, when trying to SEND messages to these user accounts I am
> getting one of the following two error messages (different for each
> account):
>
> delay=1382, status=deferred (host public/lmtp[public/lmtp] said: 451
> 4.2.0 Mailbox has an invalid format (in reply to RCPT TO command))
>
> relay=public/lmtp[public/lmtp], delay=1705, status=deferred (host
> public/lmtp[public/lmtp] said: 451 4.3.0 System I/O error (in reply to
> RCPT TO command))
>
> Thanks very much for any help or ideas!
>
> Kind regards,
>
> trichard
>
> ---
>
> localhost.localdomain> ver
> name : Cyrus IMAPD
> version : v2.1.13-Invoca-RPM-2.1.13-4 2003/05/01 19:05:29
> vendor : Project Cyrus
> support-url: http://asg.web.cmu.edu/cyrus
> os : Linux
> os-version : 2.4.20-18.8smp
> environment: Cyrus SASL 2.1.10
> Sleepycat Software: Berkeley DB 4.0.14: (November 18, 2001)
> Built w/OpenSSL 0.9.6b [engine] 9 Jul 2001
> Running w/OpenSSL 0.9.6b [engine] 9 Jul 2001
> CMU Sieve 2.2
> TCP Wrappers
> mmap = shared
> lock = fcntl
> nonblock = fcntl
> auth = unix
> idle = poll
> mboxlist.db = skiplist
> subs.db = flat
> seen.db = skiplist
> duplicate.db = db3-nosync
> tls.db = db3-nosync
>
>
>
More information about the Info-cyrus
mailing list