- dovecot - dovecot.org

[Dovecot] Logwatch
by Rich West 16 Apr '05

16 Apr '05

Having FC3 systems and utilizing Dovecot, I have come to rely on some of the information I get from the daily logwatch run. Logwatch, by default, doesn't properly recognize dovecot's information in the messages file, but it is easy to tweak. The patch below will give you some statistics regarding POP3 and IMAP usage. I believe I grabbed all of the differences in the unified diff below. If I missed anything, please post. :) -Rich --- /etc/log.d/conf/services/imapd.conf 2005-04-15 14:24:52.000000000 -0400 +++ /etc/log.d/conf/services/imapd.conf 2005-04-15 14:51:52.073609243 -0400 @@ -20,7 +20,7 @@ # Only give lines pertaining to courier... # I'm not sure if this is complete, especially for the new webmail daemon in 0.44.1 #but you will get at least all currently supported logs -*OnlyService = (imapd|imapd-ssl) +*OnlyService = (imap-login|imapd|imapd-ssl) *RemoveHeaders = --- /etc/log.d/conf/services/pop3.conf 2005-04-15 14:51:22.795813799 -0400 +++ /etc/log.d/conf/services/pop3.conf 2005-04-15 15:07:00.837019392 -0400 @@ -15,12 +15,12 @@ Title = "POP-3" # Which logfile group... -LogFile = messages +LogFile = maillog # Only give lines pertaining to courier... # I'm not sure if this is complete, especially for the new webmail daemon in 0.44.1 #but you will get at least all currently supported logs -*OnlyService = (pop3d-ssl|pop3d|spop3d) +*OnlyService = (pop3-login|pop3d-ssl|pop3d|spop3d) *RemoveHeaders = --- /etc/log.d/scripts/services/pop3 2005-04-15 15:15:28.727123168 -0400 +++ /etc/log.d/scripts/services/pop3 2005-04-15 15:03:47.402606350 -0400 @@ -58,6 +58,8 @@ # Don't care about these... } elsif ( ($User, $Host) = ( $ThisLine =~ /^user (.*?) authenticated - (.*)$/ ) ) { $Login{$User}{$Host}++; + } elsif ( ($User, $Host) = ( $ThisLine =~ /Login: (.*?) (\[.*\])/ ) ) { + $Login{$User}{$Host}++; } elsif ( ($User,$Downloaded,$DownloadSize,$Left,$LeftSize) = ( $ThisLine =~ /^Stats: (.*?) (.*?) (.*?) (.*?) (.*?)$/) ) { $DownloadedMessages{$User} += $Downloaded; $DownloadedMessagesSize{$User} += $DownloadSize; --- /etc/log.d/scripts/services/imapd 2005-04-15 15:15:20.742084824 -0400 +++ /etc/log.d/scripts/services/imapd 2005-04-15 15:04:39.868698875 -0400 @@ -43,6 +43,9 @@ # Don't care about these... } elsif ( ($User, $Host) = ( $ThisLine =~ /^Login user=(.*?) host=(.* \[.*\])$/ ) ) { $Login{$User}{$Host}++; + } elsif ( ($User, $Host) = ( $ThisLine =~ /Login: (.*?) (\[.*\])/ ) ) { + $ConnectionNonSSL{$Host}++; + $Connection{$Host}++; } elsif ( ($User,$Host) = ( $ThisLine =~ /^Authenticated user=(.*) host=(.* \[.*\])$/ ) ) { $Login{$User}{$Host}++; } elsif ( ($User,$Host) = ( $ThisLine =~ /^Preauthenticated user=(.*) host=(.*)$/ ) ) {

3 3

Re: [Dovecot] maildir in NFS
by Lev Butyrev 15 Apr '05

15 Apr '05

>I think it might be replaced with "mmap_disable=yes" (see the >dovecot-example.conf). I guess the nfs.txt file is a little out of date. > >Chris I try to use option "mmap_disable=yes", but in dovecot logs same messages: "mail_index_lock_fd() failed with file /var/mail/sam-butyrev.lk/dovecot.index.log: No locks available\ ..." In syslog such messages: kernel: lockd: cannot monitor ip_address_nfs_server kernel: lockd: failed to monitor ip_address_nfs_server nfs server Solaris 9 nfs client linux slackware 10.1 with kernel 2.4.29 Sory for my english.

2 1

[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

[Dovecot] Authentication and the wrong mailbox?
by Rich West 10 Apr '05

10 Apr '05

I just migrated from UW-imap to dovecot last night. After some tweaking of the dovecot.conf file, disabling xinetd's entries, firing up the dovecot daemon, and copying the .mailboxlist to .subscriptions for all users, things looked to be going just fine! I received a call this morning from a user stating that they had all of *my* emails in *their* inbox! They don't know when it happened as their machine POP's email off every 5-10 minutes or so, but we were able to isolate it to a 8hr period last night. Further investigation showed that at some time through the evening, dovecot freaked out during the authentication phase and for some bizzare reason, when the user connected via POP3, they were able to download all of my inbox! Additionally, by the time I was looking in to it, NO users could authenticate via dovecot, and, hence, no one had access to email. Restarting dovecot resolved the issue, but I have my doubts about it being truly resolved. I'm going to run some tests (what little I can think of), but this is the first time I have ever experienced a situation such as this. One thing for UW is that this situation never happened, and I've only had dovecot running for about 13hrs. Any ideas as to how or why this may have happened, and how it can be prevented, would be wonderful. -Rich -- Richard West $14.95 Registrations mailto:rwest@wesmo.com Wesmo Computer Services .com .net .org .tv .cc http://www.wesmo.com Full Domain & Web Hosting .BIZ .INFO & MORE!!

4 8

[Dovecot] Failed to create storage with data
by Christopher Cheng 09 Apr '05

09 Apr '05

I was trying to configure postfix, mysql with dovecot. The postfix part is fine, but dovecot seems cannot cannot read the mail directory dovecot: Apr 09 16:22:37 Info: Dovecot starting up dovecot-auth: Apr 09 16:22:38 Info: MySQL: connected to localhost dovecot-auth: Apr 09 16:22:38 Info: Login process 7 connected dovecot-auth: Apr 09 16:22:38 Info: Login process 8 connected dovecot-auth: Apr 09 16:22:38 Info: Login process 7 sent handshake: PID 13875 dovecot-auth: Apr 09 16:22:38 Info: Login process 8 sent handshake: PID 13878 dovecot-auth: Apr 09 16:22:38 Info: Login process 9 connected dovecot-auth: Apr 09 16:22:38 Info: Login process 9 sent handshake: PID 13876 dovecot-auth: Apr 09 16:23:11 Info: MySQL: Performing query: SELECT clear FROM postfix_users WHERE user='chris' dovecot-auth: Apr 09 16:23:11 Info: MySQL: Performing query: SELECT concat('/var/spool/mail/', maildir) AS mail, uid, gid FROM postfix_users WHERE user='chris' imap(chris): Apr 09 16:23:11 Error: mbox: Can't create root IMAP folder /mail: Permission denied imap(chris): Apr 09 16:23:11 Fatal: Failed to create storage with data: /var/spool/mail/mydomain.com/chris/Maildir imap-login: Apr 09 16:23:11 Info: Login: chris [::ffff:192.168.1.2] dovecot-auth: Apr 09 16:23:11 Info: Login process 9 disconnected dovecot: Apr 09 16:23:11 Error: child 13879 (imap) returned error 89 dovecot-auth: Apr 09 16:23:11 Info: Login process 9 connected dovecot-auth: Apr 09 16:23:11 Info: Login process 9 sent handshake: PID 13880 The file status in the mail folder. The uid and gid of vmail is 1004 [root@bluemountain chris]# ls /var/spool/mail/mydomain.com/chris/ -l total 16 -rwx------ 1 vmail vmail 11382 Apr 9 00:51 Maildir Here's my mysql data mysql> select * from postfix_users; +----+----------------------+-------+-------+------+------+------+---------- ----------------------+------------------------------+-------+--------+----- ----+-------+ | id | email | clear | crypt | name | uid | gid | homedir | maildir | quota | access | postfix | user | +----+----------------------+-------+-------+------+------+------+---------- ----------------------+------------------------------+-------+--------+----- ----+-------+ | 1 | chris(a)mydomain.com | pass | | | 1004 | 1004 | /var/spool/mail/mydomain.com | mydomain.com/chris/Maildir | | Y | Y | chris | +----+----------------------+-------+-------+------+------+------+---------- ----------------------+------------------------------+-------+--------+----- ----+-------+ 1 row in set (0.00 sec)

1 1

[Dovecot] Outlook express confusion
by Andrew Hutchings 08 Apr '05

08 Apr '05

Hi, This may be a problem with my config file but I am finding that customers (and more importantly my boss) that are using outlook express when using test66/67 (upgraded from test60 + from address patch) are having message reappear after being fully deleted (not just marked) but are unreadable, sometimes blank headers appear too but again no message. Since it is affecting my boss he has told me to go back to test60 or lower, and won't let me find the problem. Regards Andrew -- Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Random BOFH excuse: Cosmic ray particles crashed through the hard disk platter

2 10

[Dovecot] maildir quota management
by Wayne Lovely 08 Apr '05

08 Apr '05

Hi everyone, my name is Wayne Lovely and this is my first post. My company has a need for dovecot to decrement the portion of quota used. The used portion and hard limit will be stored in a central database. Initially I'll just hack in what we need as a proof of concept, but I would like to get some input into what people would really like, such that I can make a good contribution. regards, Wayne Lovely

2 3

[Dovecot] 1.0-test67
by Timo Sirainen 08 Apr '05

08 Apr '05

http://dovecot.org/test/ Hopefully better release than last one. Fixes several problems test66 had and also some older problems reported in this list. It also contains a pretty large mbox code cleanup, fixing several problems (especially related to X-IMAP/X-IMAPbase headers) and making it a bit faster. Maybe I'll backport it to 1.0-stable too when it looks like it's stable.. BTW. mbox code is slower than necessary when updating message flags and mbox_lazy_writes=yes, because it reads message headers for each message whose flag is to be changed (in index). Should fix that one soon too..

2 4

Re: [Dovecot] Delimiter of mailbox changes in response to STATUS command...
by Lawrence Katz 08 Apr '05

08 Apr '05

Hi Chris - Thank you for the reply. > I can't reproduce this in our setup in either 1.0-stable or > 1.0-test66. What's your namespace definition and MAIL= environment? > What does > > 1 LIST "Misc/" "*" > > give you? The LIST command returns what I expect to see (for readability): 2 list "Misc/" "*" * LIST (\HasNoChildren) "/" "Misc/Spam" > Can you 1 SELECT "Misc/Spam" OK? I can select that mailbox as well as others without a problem. Here's what NAMESPACE returns: 3 NAMESPACE * NAMESPACE (("" "/")) NIL NIL My namespace definition in dovecot.conf is as follows: namespace private { separator = / # prefix = # location = inbox = yes # hidden = yes } I didn't have default_mail_env set to anything, but I just tried the following without a change in the STATUS command's behavior: default_mail_env = maildir:/home/%u/Maildir Is there any other information that might help? Thanks, Lawrence

3 6

[Dovecot] Linux, Maildir over NFS, Locking problems
by Terrence Martin 08 Apr '05

08 Apr '05

Hi, I am having problems with file locks with my NFS mounted Maildir setup. NFS Client/IMAP Server is RHEL3 clone whitebox and NFS server is a Fedora Core 2 system. Both are running lockd as far as I can tell. dovecot is installed with Dag's latest dovecot RPMs for RHEL3. Time is synced between the two systems. Here is the pertinent log file entry dovecot: Dovecot starting up Apr 7 11:17:42 sentry imap(tmartin): /home/tmartin/Maildir/.subscriptions failed with subscription file file_wait_lock(): No locks available Now what I can find in nfs.txt is that I need to use fnctl is this ".customflags and .subscriptions files require fcntl() locking currently. Many NFS servers don't support it, at least without a separate lockd daemon. These will be fixed later to be NFS-safe by default." My question is am I using fcntl? The only reference I can find in the config refers to mbox formats, but I am using maildir. Setting the one reference to fcntl does not seem to have any effect. Is there a configuration setting to tell the server to use fcntl locks or a way to tell if it is trying to use fcntl locks? Thanks for any tips, Terrence

2 4

[Dovecot] MySQL-Auth Problem
by Felix Jirka 08 Apr '05

08 Apr '05

Hi, i would use Dovecot-test66 with MySQL-Auth for virtual users. MySQLd version: 4.1.10a I compliled dovecot with: CPPFLAGS=-I/usr/include/mysql LDFLAGS=-L/usr/lib ./configure --prefix=/usr --sysconfdir=/etc/dovecot --without-passwd --without-shadow --without-pam --without-checkpassword --without-bsdauth --without-vpopmail --with-mysql --with-ssl=openssl --with-storages=maildir --with-moduledir=/etc/dovecot/modules but if i start Dovecot i get: Apr 3 12:44:28 l2 dovecot: auth-worker(default): mysql: Connect failed to 127.0.0.1 (mail): Benutzer 'mail'@'localhost' hat keine Zugriffsberechtigung (verwendetes Passwort: Ja) - waiting for 75 seconds before retry but password and user are correct and worked with dovecot 0.99.14 cu Felix

2 1

[Dovecot] 1.0-test66
by Timo Sirainen 08 Apr '05

08 Apr '05

http://dovecot.org/test/ I've still lots of mails in my INBOX and in this list that I should be looking into.. But here's a release that fixes at least some things. Maybe I'll make another one tomorrow.. Most importantly keyword code was changed a lot. It's now faster and less buggy. The keywords are also finally written into mbox, and keyword changes in the mbox are picked up. So upgrading from Dovecot 0.99.x or UW-IMAP (or reverting back to them) doesn't anymore lose the keywords. Maildir still needs 0.99.x-compatible customflags-file and storing the keywords as a..z flags in maildir filename. Hopefully I'll get that done soon, and then we should be nearing 1.0-alpha1 release :) The new keyword code hasn't been tested much, so this might be less stable than earlier versions. - Renamed oe6-fetch-no-newmail workaround to delay-newmail and changed it to work more like the name says: only newmail notifications are skipped and not only for FETCH command. - LDAP crashfixes - Changed FETCH to return smaller items first. Should fix all kmail and Thunderbird problems. Removed tb-negative-fetch workaround as it shouldn't be needed anymore. - Cache file was breaking constantly with test65 - Blocking passdb fixes and proper RPA realm support patches from Andrey - in-memory indexes should be working again if someone wants to use them for some reason (:INDEX=MEMORY) - gzipped mbox plugin http://dovecot.org/patches/1.0/zlib-plugin.tar.gz - SORT crashfix - Some mbox rewriting fixes (should fix some asserts) - etc.

6 6

[Dovecot] Question about "reply from worker without password scheme"
by Zoong PHAM 08 Apr '05

08 Apr '05

I have dovecot-1.0-test64 installed on OpenBSD-3.6. It works fine with local password. Now I fail to get dovecot to use MySQL to query for user details. Any help would be very appreciated. Here are the details: from /var/log/maillog: 1) with "default_pass_scheme = PLAIN" Apr 3 07:20:22 www dovecot: Dovecot v1.0-test64 starting up Apr 3 07:20:23 www dovecot: auth(default): mysql: Connected to (null) (dovecot) Apr 3 07:20:23 www dovecot: auth-worker(default): mysql: Connected to (null) (dovecot) Apr 3 07:20:50 www dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=1.2.3.4 rip=5.6.7.8 resp=AGhhemVsQGhhemVscGhhbS5jb20AemhAMTlTQXZl Apr 3 07:20:50 www dovecot: auth-worker(default): sql(client(a)clientdomain.com,5.6.7.8): query: SELECT pass AS password FROM user WHERE user = 'client(a)clientdomain.com' Apr 3 07:20:50 www dovecot: auth(default): blocking(client(a)clientdomain.com,5.6.7.8): Received reply from worker without password scheme Apr 3 07:20:51 www dovecot: auth(default): client out: FAIL 1 user=client(a)clientdomain.com temp Apr 3 07:21:50 www dovecot: imap-login: Disconnected: Inactivity [5.6.7.8] 2) with "default_pass_scheme = PLAIN-MD5" Apr 3 07:07:13 www dovecot: Dovecot v1.0-test64 starting up Apr 3 07:07:14 www dovecot: auth(default): mysql: Connected to (null) (dovecot) Apr 3 07:07:14 www dovecot: auth-worker(default): mysql: Connected to (null) (dovecot) Apr 3 07:07:47 www dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP se cured lip=1.2.3.4 rip=5.6.7.8 resp=AGhhemVsQGhhemVscGhhbS5jb20AemhAMTlTQXZl Apr 3 07:07:47 www dovecot: auth-worker(default): sql(client(a)clientdomain.com,5.6.7.8): query: SELECT pass AS password FROM user WHERE user = 'client(a)clientdomain.com' Apr 3 07:07:48 www dovecot: auth(default): client out: FAIL 1 user=client(a)clientdomain.com Command to start dovecot: /usr/local/dovecot/sbin/dovecot -c /usr/local/dovecot/etc/dovecot.conf Part of /usr/local/dovecot/etc/dovecot.conf: .... disable_plaintext_auth = no .... # SQL database passdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for # example args = /usr/local/dovecot/etc/dovecot-mysql.conf } .... # SQL database userdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for # example args = /usr/local/dovecot/etc/dovecot-mysql.conf } .... I also tried with "disable_plaintext_auth = yes" without any luck. /usr/local/dovecot-1.0-test64/etc/dovecot-mysql.conf: driver = mysql connect = host=/var/www/dovecot/mysql.sock dbname=dovecot user=dovecot password=secretpwDB default_pass_scheme = PLAIN password_query = SELECT pass AS password FROM user WHERE user = '%u' user_query = SELECT maildir AS mail, sysuid AS uid, sysgid AS gid FROM user WHERE user = '%n' Manually query MySQL with username and passwd as specified in /usr/local/dovecot-1.0-test64/etc/dovecot-mysql.conf: mysql> SELECT pass AS password FROM user WHERE user ='client(a)clientdomain.com'; +-----------+ | password | +-----------+ | secretpw | +-----------+ 1 row in set (0.00 sec) mysql> Thanks, Zoong

3 10

[Dovecot] imap segfault in mail-cache.c
by Todd Burroughs 08 Apr '05

08 Apr '05

Found an imap crash. I'm using the CVS copy from March 23. This is running under Linux, kernel 2.6.11.something. We use mbox over NFS, everything is on the NFS server. There is currently only one dovecot server accessing the mailbox. Here's the log messages: dovecot: Apr 05 13:11:20 Error: 27911 IMAP(support): UIDVALIDITY changed (1112720886 -> 1112721068) in mbox file /mailhome/new/m/support/mbox dovecot: Apr 05 13:11:20 Error: 27911 IMAP(support): mbox sync: UID inserted in the middle of mailbox /mailhome/new/m/support/mbox (316790 > 316789) dovecot: Apr 05 13:11:20 Error: 27911 IMAP(support): Corrupted index cache file /mailhome/new/m/support/.imap/INBOX/dovecot.index.cache: indexid changed dovecot: Apr 05 13:11:20 Error: child 27911 (imap) killed with signal 11 Here's a backtrace. Note that cache->hdr is NULL. Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. #0 0x080777f9 in mail_cache_lock (cache=0x80c4e20) at mail-cache.c:404 404 cache->hdr_copy = *cache->hdr; (gdb) bt #0 0x080777f9 in mail_cache_lock (cache=0x80c4e20) at mail-cache.c:404 #1 0x0807a1e9 in mail_cache_handler_init (ctx_r=0xbffff3d8, cache=0x80c4e20) at mail-cache-sync-update.c:40 #2 0x0807a3a0 in mail_cache_expunge_handler (sync_ctx=0xbffff520, seq=32, data=0x80cc964, context=0x80c8ce0) at mail-cache-sync-update.c:85 #3 0x08081ba3 in mail_index_sync_record (ctx=0xbffff520, hdr=0x80c5e34, data=0x80cb590) at mail-index-sync-update.c:135 #4 0x080826b9 in mail_index_sync_update_index (sync_ctx=0x80c5d98, sync_only_external=0) at mail-index-sync-update.c:648 #5 0x08080913 in mail_index_sync_commit (ctx=0x80c5d98) at mail-index-sync.c:595 #6 0x0806e432 in mbox_sync (ibox=0x80c3fe0, flags=MBOX_SYNC_REWRITE) at mbox-sync.c:1418 #7 0x08067eb9 in mbox_storage_close (box=0x80c3fe0) at mbox-storage.c:914 #8 0x0808a72d in mailbox_close (box=0xffffff02) at mail-storage.c:299 #9 0x08057efc in _cmd_select_full (cmd=0x80b9050, readonly=0) at cmd-select.c:50 #10 0x08057f31 in cmd_select (cmd=0x80b9050) at cmd-select.c:99 #11 0x080593f5 in _client_input (context=0x80b9010) at client.c:334 #12 0x0809b28a in io_loop_handler_run (ioloop=0x80b79e8) at ioloop-poll.c:184 #13 0x0809a9a9 in io_loop_run (ioloop=0x80b79e8) at ioloop.c:218 #14 0x080602a7 in main (argc=1, argv=0xbffffa34, envp=0xbffffa3c) at main.c:229 (gdb) bt full #0 0x080777f9 in mail_cache_lock (cache=0x80c4e20) at mail-cache.c:404 view = (struct mail_index_view *) 0x80c4748 ext = (const struct mail_index_ext *) 0x80c62c8 i = 0 ret = -1 #1 0x0807a1e9 in mail_cache_handler_init (ctx_r=0xbffff3d8, cache=0x80c4e20) at mail-cache-sync-update.c:40 ctx = (struct mail_cache_sync_context *) 0x80c6958 ret = Variable "ret" is not available. (gdb) p cache->hdr $1 = (const struct mail_cache_header *) 0x0 Todd Burroughs

2 1

[Dovecot] Archiving Dovecot format maildir
by Leslie Viljoen 08 Apr '05

08 Apr '05

Hi! It seems that the Maildir format used by Dovecot is a standard, right? Has anyone written something to archive mail in Dovecot format maildirs? I have a script that seems to be for Cyrus IMAP but it doesn't seem to work. I'll write a Perl program if there is nothing available but I am concerned about dovecot's index files - do I need to do anything to get dovecot to rebuild them? Leslie Viljoen

2 1

[Dovecot] headers don't match message
by Kevin 08 Apr '05

08 Apr '05

the other day i moved all mail functions to a different machine. i copied over my existing maildir's and installed dovecot-stable-20050405. once i had everything moved and dovecot running i checked my mail via imap. all the messages appeared however when i try to read a message the message body doesn't match the header info that's showed in the message list. is this an index problem? or did i corrupt my maildir when i moved it over to another host?

3 4