Type Number in mailboxes.db
Hallo, which values are possible and what is the corresponding meaning for the Type Number in mailboxes.db? After failed XFERs we see - on the murder user.richard^hildebrand 1 mailcluster1 - on mailcluster1 user.richard^hildebrand 8 mailbackend-1-febe!default We would like to know what this means. Is it in error? And if it is, how to solve the problem. --Frank Elsner Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Type Number in mailboxes.db
On 02/08/11 16:30 +0200, Frank Elsner wrote: Hallo, which values are possible and what is the corresponding meaning for the Type Number in mailboxes.db? After failed XFERs we see - on the murder user.richard^hildebrand 1 mailcluster1 - on mailcluster1 user.richard^hildebrand 8 mailbackend-1-febe!default We would like to know what this means. Is it in error? And if it is, how to solve the problem. For documentation on the mailbox format, see: http://www.cyrusimap.org/docs/cyrus-imapd/2.4.10/internal/database-formats.php and /imap/mboxlist.h in the source: /* flags for types of mailboxes */ #define MBTYPE_REMOTE (10) /* Not on this server (part is remote host) */ #define MBTYPE_RESERVE (11) /* Reserved [mupdate/imapd] / Rename Target [imapd] (part is normal, but you are not allowed to create this mailbox, even though it doesn't actually exist */ #define MBTYPE_NETNEWS (12) /* Netnews Mailbox - NO LONGER USED */ #define MBTYPE_MOVING (13) /* Mailbox in mid-transfer (part is remotehost!localpart) */ #define MBTYPE_DELETED (14) /* Mailbox has been deleted, but not yet cleaned up */ It appears that mailcluster1 believes a mailbox transfer was initiated, but has not yet completed (or failed). You can use cyr_dbtool to manually edit the entry in your mailboxes.db, or remove it. See: http://asg.andrew.cmu.edu/archive/message.php?mailbox=archive.info-cyrusmsg=52899 -- Dan White Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: IOERROR: zero index/expunge record
Does anybody have an idea what cause this problem and how to finally fix it? Am 22.07.2011 10:19, schrieb Marc Muehlfeld: Hi, two weeks ago we migrated from Centos 5.6 (cyrus 2.3.7) to Scientific Linux 6.0 (cyrus 2.3.16). Since that day some users are having problems with their mailbox. Thunderbird shows them IOERRORS and some are seeing undeletable mails with no content. The imapd's logfile contains the following: imap[21918]: IOERROR: user.xxx zero index/expunge record 41/47 imap[16600]: IOERROR: user.yyy zero index/expunge record 16/17 Also the mailbox (sub-)folder contains *.NEW files when this happens: -rw--- 1 cyrus mail 13660 22. Jul 09:22 cyrus.cache.NEW -rw--- 1 cyrus mail800 22. Jul 09:22 cyrus.index.NEW Reconstructing the mailbox removes the *.NEW files and it's working for some hours or a day. But the problem and the *NEW files are always comming back. But reconstructing several mailboxes every day can't be the solution. On client side nothing had changed. For the migration the database was converted to text on the old system and reimported on SL6 using ctl_mboxlist. /etc/imapd.conf and /etc/cyrus.conf are copied from the old system. Does anybody have an idea what could be wrong and how it could be fixed? Regards, Marc Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: IOERROR: zero index/expunge record
Does anybody have an idea what cause this problem and how to finally fix it? Am 22.07.2011 10:19, schrieb Marc Muehlfeld: Hi, two weeks ago we migrated from Centos 5.6 (cyrus 2.3.7) to Scientific Linux 6.0 (cyrus 2.3.16). Since that day some users are having problems with their mailbox. Thunderbird shows them IOERRORS and some are seeing undeletable mails with no content. The imapd's logfile contains the following: imap[21918]: IOERROR: user.xxx zero index/expunge record 41/47 imap[16600]: IOERROR: user.yyy zero index/expunge record 16/17 Also the mailbox (sub-)folder contains *.NEW files when this happens: -rw--- 1 cyrus mail 13660 22. Jul 09:22 cyrus.cache.NEW -rw--- 1 cyrus mail800 22. Jul 09:22 cyrus.index.NEW Reconstructing the mailbox removes the *.NEW files and it's working for some hours or a day. But the problem and the *NEW files are always comming back. But reconstructing several mailboxes every day can't be the solution. On client side nothing had changed. For the migration the database was converted to text on the old system and Something is wrong with the database because Cyrus-imapd uses a number of databases. So I guess here is a problem. Do you not see any other errors in the Cyrus logs? Simon Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
