- dovecot - dovecot.org

[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 11 Apr '05

11 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 11 Apr '05

11 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 09 Apr '05

09 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 09 Apr '05

09 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