- dovecot - dovecot.org

[Dovecot] comparision with other imap servers and folder sharing
by Emmett Lazich 15 Apr '05

15 Apr '05

Some praise: Timo, I must say I am super impressed with this product. I do free support a few good friends with small businesses running Linux servers (a mix of RH9, Suse9.2 and gentoo) that I dropped as email and samba servers. I found UW-IMAP to be terrible in every way except that using mbox is sometimes nice for old s/w tools. No need for details re UW-IMAP problems. In early 2004 I found courier-imap to be vastly better behaved than UW-IMAP and also much faster once large folders were open. DJB's Maildirs seemed cool, and postfix likes them too, and mb2md-3.20.pl worked great . So everything seemed good and certainly was better. But courier cannot cope with large imap accounts (eg. millions of messages and a few GBytes) where courier-imap grinds to a halt on the initial folder scanning. Cyrus just looks like a big evil beast that needs too much time to learn. Four days ago, this lead me to dovecot. The performance, reliability, configurability of dovecot is amazing. Timo, I think you could give yourself more credit on something important when selling Dovecot. You write that Dovecot "does not support shared folders". This might turn away some people considering Dovecot. People whom like me do not have/want a good understanding of the imap protocol. I believe you mean that Dovecot does not support shared folders in the technical imap sense of shared namespaces between separate imap accounts. Since Dovecot works beautifully when sharing folders via logging in with the same username more than once. Plus your documentation and config notes imply that this is no problem. IDLE and fcntl locking works great for me. Thank you and good luck! -Emmett

1 0

[Dovecot] maildir in NFS
by Lev Butyrev 14 Apr '05

14 Apr '05

How can I configure the dovecot for working with maildir's through NFS? If I add option "index_mmap_invalidate = yes" (as in doc/nfs.t) then in log I have this message: "Error: Error in configuration file /etc/dovecot.conf line 296: Unknown setting: index_mmap_invalidate" If I try to get the mail without option "index_mmap_invalidate" then I have in log this message: "Error: POP3(butyrev.lk): mail_index_lock_fd() failed with file /var/mail/sam-butyrev.lk/dovecot.index.log: No locks available dovecot: Error: POP3(butyrev.lk): mail_index_wait_lock_fd() failed with file /var/mail/sam-butyrev.lk/dovecot.index.log: No locks available dovecot: Error: POP3(butyrev.lk): Couldn't open INBOX: Internal error occured. Refer to server log for more information." dovecot-stable-20050414

2 1

[Dovecot] dovecot + pam + krb5 + nsswitch
by Askar 14 Apr '05

14 Apr '05

hi, anyone of you pls guide me what entries to put in nsswitch.conf for pam to work with krberse, i'm trying to authenticate users from AD, I thinks (my findings) pam.d/dovecot looks into /etc/nsswitch.conf for which passwd databases to use while authenticating a users. my krb setup is working fine I tested with "kinit username" and it authenticat to AD server. Atm i'm trying with these setttings in /etc/nsswitch.conf with no success. #group: compat #group_compat: nis passwd: files krb group: files krb hosts: files dns #networks: files #passwd: compat #passwd_compat: nis #shells: files ~ My plateform is freebsd 5.3 regards Askar

1 0

[Dovecot] test67 ldap_connection
by Thomas Hummel 13 Apr '05

13 Apr '05

Hello, I've been trying to figure out what's wrong with authentication against an ldap pass/user db with test67 as test62 was working fine. [ The problem is the same as previously described in this list : - FreeBSD-5.3 - dovecot-1.0-test67 - openldap-2.1.27 --> "ldap(dovetest,127.0.0.1): No password in reply" --> "NO Temporary authentication failure." or -- dovecot: Apr 12 18:22:41 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=157.99.64.42 rip=157.99.64.42 dovecot: Apr 12 18:22:41 Info: auth(default): client out: CONT 1 dovecot: Apr 12 18:22:41 Info: auth(default): client in: CONT 1 AGRvdmV0ZXN0AGZvbw== dovecot: Apr 12 18:22:41 Info: auth(default): ldap(dovetest,157.99.64.42): base=ou=personnes, dc=pasteur, dc=fr scope=subtree filter=(&(objectClass=posixAccount)(uid=dovetest)) fields=uid,homeDirectory,,,uidNumber,gidNumber dovecot: Apr 12 18:22:42 Info: auth(default): client in: AUTH 2 PLAIN service=IMAP lip=157.99.64.42 rip=157.99.64.42 resp=AGRvdmV0ZXN0AGZvbw== dovecot: Apr 12 18:22:42 Info: auth(default): ldap(dovetest,157.99.64.42): base=ou=personnes, dc=pasteur, dc=fr scope=subtree filter=(&(objectClass=posixAccount)(uid=dovetest)) fields=uid,homeDirectory,,,uidNumber,gidNumber dovecot: Apr 12 18:22:42 Error: auth(default): ldap(dovetest,157.99.64.42): No password in reply dovecot: Apr 12 18:22:42 Error: auth(default): file passdb-ldap.c: line 122 (handle_request): assertion failed: (scheme != NULL) dovecot: Apr 12 18:22:42 Error: child 43147 (auth) killed with signal 6 -- ] I've noticed the following changes in the source code, and my understanding (which may be wrong) of my problem goes as follows : - In test62, the 'attr_names' attribute array was defined outside the 'ldap_connection' struct, thus allowing 'passdb_ldap_conn' and 'userdb_ldap_conn' structs to have different array of such type. - At the opposite, in test67, the 'attr_names' array is inside the 'ldap_connection'. As 'passdb_ldap_conn' and 'userdb_ldap_conn' are of the 'ldap_connection' type and since the 'db_ldap_init' function returns the existing ldap connection if it exists, the 'passdb_ldap_preinit' and 'usedb_ldap_preinit' will call the 'db_ldap_set_attrs' function on _the same_ 'ldap_connection' object. - So when the 'db_ldap_search' function is called from the 'passdb-ldap.c:ldap_lookup_pass function, the 5th argument (passdb_ldap_conn->attr_names) will point to the 'user_attrs' instead of the 'pass_attrs', since userdb_preinit will have already been called. - I've also noticed the use of the 'attr_map' hash to store the attribute/value pairs, but since it doesn't seems to be used when calling 'ldap_lookup_pass', I guess the problem is somewhere else. Can someone give me a clue ? Has someone successfully set up dovecot-1.0-test67 on a similar configuration ? thanks -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 2

[Dovecot] dovecot 0.99.14 assertion failed
by Ivan Pesin 13 Apr '05

13 Apr '05

Hello. Recently I've got following assertion on my server with dovecot 0.99.14 when searching: file message-body-search.c: line 391 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos) -- Ivan Pesin N-iX Newcomp GmbH

1 0

[Dovecot] dovecot + postfix + active directory
by Askar 12 Apr '05

12 Apr '05

hi list, I'm just curious if someone succesfully done dovecot authentication of Active directory and I will appreciage any link in this regards Thanks Askar

3 6

[Dovecot] Syslog, Dovecot, and LogWatch
by Rich West 12 Apr '05

12 Apr '05

At what level does Dovecot log to syslog? UW-IMAP uses local6.debug to log to syslog, but it doesn't seem that dovecot does the same.. (the file I defined for UW-IMAP's output hasn't received anything since I moved over to Dovecot? Also, has anyone managed to get LogWatch and Dovecot to play nicely together? I noticed that LogWatch no longer gives any statistics on the imap usage since I shut down UW and went full blast with Dovecot.. -Rich

4 4

[Dovecot] Index(?) problem under OpenBSD
by Gaby vanhegan 12 Apr '05

12 Apr '05

Hi, My apologies if this has been mentioned before, I haven't pulled up a google search yet. I run Dovecot from the package under OpenBSD 3.6 (dovecot-0.99.10.8). The problem I have is that occasionally dovecot corrupts an index file (I think), which causes the process to gradually creep up in usage, until it hits 99%, where it stays, without quitting. If I then fire up my mail client later on, it does the same thing. Doing this two or three times results in 3 processes, all at 33%, and a load of 100 on the server. The problem is resolved by deleting all the index files in my Maildir. If this doesn't solve the problem, then duplicating my Maildir and using the new copy, after deleting all the index files, fixes the problem. But these only work for a while, and the problem rears it's head with other users as well, so I need a fix. Has anybody else suffered this problem? Is there a fix in a more recent version? Is it OpenBSD specific? What can I do to help diagnose the problem? Should I turn of indexes? Upgrade to the latest version? Some example errors from my logfile: imap(gaby): Apr 11 15:32:37 Error: Corrupted index file /home/gaby/Maildir/.INBOX/.imap.index: Wrong messages_count in header (261 != 382) imap(gaby): Apr 11 15:32:37 Error: Corrupted index data file /home/gaby/Maildir/.INBOX/.imap.index.data: used_file_size larger than real file size (142368 vs 10264) imap(gaby): Apr 11 15:32:44 Error: Corrupted index file (in-memory index for /home/gaby/Maildir): UIDVALIDITY changed in uidlist imap(gaby): Apr 11 15:36:12 Error: Timeout while waiting for release of shared fcntl() lock for index file /home/gaby/Maildir/.Work.LTSN/.imap.index imap(gaby): Apr 11 16:21:27 Error: Timeout while waiting for release of shared fcntl() lock for index file /home/gaby/Maildir/.Archive.Trash-20050308/.ima imap(gaby): Apr 11 16:25:02 Error: Timeout while waiting for release of shared fcntl() lock for index file /home/gaby/Maildir/.Archive.Trash-20050407/.ima Gaby -- Uganda Maximum - Enemy of the English Thrust gaby(a)vanhegan.net http://weblog.vanhegan.net

3 5

[Dovecot] Namespace prefix not ending with separator
by Chris Wakelin 11 Apr '05

11 Apr '05

I'm still battling my way through using hidden namespaces to hide the change from UW-IMAP to Dovecot 1.0-stable from my users. The latest problem is that some (probably many) users have their IMAP folder prefix set to "~/mail" rather than "~/mail/". I have hidden namespaces with prefixes "~/mail/", "~%u/mail/" and "mail/". LIST "~/mail" "*" returns nothing, so I've tried adding another namespace for "~/mail". Now LIST "~/mail" "*" returns * LIST (\NoInferiors \UnMarked) "/" "~/mailtest1/test1-2" * LIST (\NoInferiors \UnMarked) "/" "~/mailtest2" * LIST (\NoInferiors \UnMarked) "/" "~/mailtest3" whereas UW-IMAP returns * LIST (\NoInferiors \UnMarked) "/" ~/mail/test1/test1-2 * LIST (\NoInferiors \UnMarked) "/" ~/mail/test2 * LIST (\NoInferiors \UnMarked) "/" ~/mail/test3 I wonder whether LIST should insert an extra namespace separator in such cases? Having said that, it seems to work, except it may cause problems with folder subscriptions, which I've had to hack in order for them to be compatible with UW-IMAP (i.e. to store them as "~/mail/test1" etc.) Best Wishes, Chris --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 0

[Dovecot] imap segfault in mail-index-sync.c
by Todd Burroughs 10 Apr '05

10 Apr '05

Our support team seems to have caused another crash. They treat this mailbox like a shared one, so there may be a few people accessing it at once. They are mostly using dovecot, but some could be using uw-imap. These are the only two ways that this box is accessed. I know that this doesn't really work with mbox, but it doesn't appear to corrupt the mailbox. It seems to be a good stress test... In this case, it looks like several of them are logged in at once. Here's the log entry and backtrace of the imap process which segfaulted. I'll put a section of logs covering this time at the end, in case it helps. The problem appears to be here in mail-index-sync.c: #define MAIL_INDEX_IS_SYNCS_SAME(index) \ ((index)->sync_log_file_seq == (index)->hdr->log_file_seq && \ (index)->sync_log_file_offset == (index)->hdr->log_file_ext_offset) index->hdr is NULL dovecot: Apr 09 20:52:07 Error: 27413 IMAP(support): Fixed index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: recent_messages_count 12 -> 0 dovecot: Apr 09 20:52:11 Error: 27413 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: Extension introduction for unknown id 1 dovecot: Apr 09 20:52:11 Error: 27413 IMAP(support): Corrupted index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: File too small dovecot: Apr 09 20:52:12 Error: child 27413 (imap) killed with signal 11 Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. (gdb) bt #0 0x08082836 in mail_index_sync_begin (index=0x80c1dc8, ctx_r=0x1, view_r=0x1, log_file_seq=4294967295, log_file_offset=Unhandled dwarf expression opcode 0x93 ) at mail-index-sync.c:322 #1 0x0806e7f3 in mbox_sync (mbox=0x80c29a8, flags=Variable "flags" is not available. ) at mbox-sync.c:1459 #2 0x080683f6 in mbox_storage_close (box=0x80c29a8) at mbox-storage.c:955 #3 0x0808c59d in mailbox_close (box=0x1) at mail-storage.c:300 #4 0x080593da in client_destroy (client=0x80bb968) at client.c:72 #5 0x080596d6 in _client_input (context=0x80bb968) at client.c:387 #6 0x0809d74a in io_loop_handler_run (ioloop=0x80ba5b0) at ioloop-poll.c:184 #7 0x0809ce69 in io_loop_run (ioloop=0x80ba5b0) at ioloop.c:218 #8 0x080604a7 in main (argc=1, argv=0xbffffa44, envp=0xbffffa4c) at main.c:228 (gdb) p index->hdr $11 = (const struct mail_index_header *) 0x0 Here's the rest of the logs: dovecot: Apr 09 20:51:59 Error: 27337 IMAP(support): Fixed index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: recent_messages_count 12 -> 0 dovecot: Apr 09 20:52:01 Error: 27337 IMAP(support): Cached message offset lost for seq 11 in mbox file /mailhome/new/m/2/support/mbox dovecot: Apr 09 20:52:07 Error: 27413 IMAP(support): Fixed index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: recent_messages_count 12 -> 0 dovecot: Apr 09 20:52:11 Error: 25454 IMAP(support): mbox sync: Expunged message reappeared in mailbox /mailhome/new/m/2/support/mbox (UID 323634 < 324043) dovecot: Apr 09 20:52:11 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: Append with UID 323479, but next_uid = 324043 dovecot: Apr 09 20:52:11 Error: 27413 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: Extension introduction for unknown id 1 dovecot: Apr 09 20:52:11 Error: 27413 IMAP(support): Corrupted index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: File too small dovecot: Apr 09 20:52:12 Error: child 27413 (imap) killed with signal 11 dovecot: Apr 09 20:52:13 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 1 dovecot: Apr 09 20:52:15 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 1 dovecot: Apr 09 20:52:17 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 1 dovecot: Apr 09 20:52:18 Error: 27467 IMAP(support): Corrupted index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: File too small dovecot: Apr 09 20:52:18 Error: 27467 IMAP(support): Corrupted index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: File too small dovecot: Apr 09 20:52:19 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:19 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 1 dovecot: Apr 09 20:52:19 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (2 >= 2) dovecot: Apr 09 20:52:21 Error: 25454 IMAP(support): Corrupted index cache file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.cache: indexid changed dovecot: Apr 09 20:52:21 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:21 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 1 dovecot: Apr 09 20:52:21 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (96) > file size (24) dovecot: Apr 09 20:52:21 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (3 >= 3) dovecot: Apr 09 20:52:23 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:23 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 2 dovecot: Apr 09 20:52:23 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (96) > file size (24) dovecot: Apr 09 20:52:23 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (4 >= 4) dovecot: Apr 09 20:52:25 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 3 dovecot: Apr 09 20:52:27 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:27 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 3 dovecot: Apr 09 20:52:27 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (44) > file size (24) dovecot: Apr 09 20:52:27 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (5 >= 5) dovecot: Apr 09 20:52:29 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:29 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 4 dovecot: Apr 09 20:52:29 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (44) > file size (24) dovecot: Apr 09 20:52:29 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (6 >= 6) dovecot: Apr 09 20:52:31 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:31 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 5 dovecot: Apr 09 20:52:31 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (44) > file size (24) dovecot: Apr 09 20:52:31 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (7 >= 7) dovecot: Apr 09 20:52:33 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:33 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 6 dovecot: Apr 09 20:52:33 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (44) > file size (24) dovecot: Apr 09 20:52:33 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (8 >= 8) dovecot: Apr 09 20:52:35 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:35 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 7 dovecot: Apr 09 20:52:35 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (84) > file size (24) dovecot: Apr 09 20:52:35 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (9 >= 9) dovecot: Apr 09 20:52:38 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:38 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 8 dovecot: Apr 09 20:52:38 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (140) > file size (24) dovecot: Apr 09 20:52:38 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (10 >= 10) dovecot: Apr 09 20:52:39 Error: 27552 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 10 dovecot: Apr 09 20:52:40 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:40 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 9 dovecot: Apr 09 20:52:40 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (44) > file size (24) dovecot: Apr 09 20:52:40 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (11 >= 11) dovecot: Apr 09 20:52:42 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:52:42 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 10 dovecot: Apr 09 20:52:42 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (44) > file size (24) dovecot: Apr 09 20:52:42 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (12 >= 12) dovecot: Apr 09 20:52:42 Error: 27552 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 11 dovecot: Apr 09 20:53:12 Error: 27552 IMAP(support): file_dotlock_open() failed with file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: Resource temporarily unavailable dovecot: Apr 09 20:53:12 Error: 27552 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 11 dovecot: Apr 09 20:53:12 Error: 27552 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 11 dovecot: Apr 09 20:53:12 Error: 27552 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 11 dovecot: Apr 09 20:53:12 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:53:12 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 11 dovecot: Apr 09 20:53:12 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (13 >= 13) dovecot: Apr 09 20:53:14 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 11 dovecot: Apr 09 20:53:16 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:53:16 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 11 dovecot: Apr 09 20:53:16 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 12 dovecot: Apr 09 20:53:16 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (14 >= 14) dovecot: Apr 09 20:53:18 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid indexid (1113094338 != 1113087252) dovecot: Apr 09 20:53:18 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 12 dovecot: Apr 09 20:53:18 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 13 dovecot: Apr 09 20:53:18 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (15 >= 15)

1 0