- dovecot - dovecot.org

[Dovecot] Problems under opensuse-10.3-x86_64
by Christian Kuehn 02 Jun '08

02 Jun '08

Hi, I have a lot of problems to compile or to run the dovecot on my OpenSUSE 10.3 x86_64. Sometimes the compiled binary cannot read the existing and running config, the dovecot -n results in: ian:/opt/src/build/dovecot-1.1.rc7 # /opt/dovecot/sbin/dovecot -n # 1.1.rc7: /etc/dovecot/dovecot.conf Error: Missing auth section for server default Fatal: Invalid configuration in /etc/dovecot/dovecot.conf The prebuild RPM-daemon (v 10.0.13) said: ian:/opt/src/build/dovecot-1.1.rc7 # dovecot -n # 1.0.13: /etc/dovecot/dovecot.conf listen: *:8088 ssl_listen: *:10943 ssl_disable: yes ssl_cert_file: /etc/exim/www.foo-bar.de.crt ssl_key_file: /etc/exim/www.foo-bar.de.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /opt/dovecot/libexec/dovecot/imap-login first_valid_uid: 98 mail_location: maildir:~/maildir mail_executable: /opt/dovecot/libexec/dovecot/imap auth default: passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf This looks fine and right, but there is no access to my old maildir (created by courier-imap) and I found several entries like this in my maillog: May 27 19:13:54 ian dovecot: IMAP(tkstest(a)foor-bar.de): Unexpected eof found when reading file 'UNOPENED' (Errcode: 0) or: May 27 16:22:44 ian dovecot: IMAP(tkstest(a)foo-bar.de): Corrupted transaction log file /var/spool/virtuser/xxxxx/mail/INBOX./.imap/Trash/dovecot.index.log: unexpected end of file while reading header or: May 27 18:05:44 ian dovecot: IMAP(tkstest(a)foo-bar.de): file mail-index.c: line 1 900 (mail_index_move_to_memory): assertion failed: (index->fd == -1) May 27 18:05:44 ian dovecot: IMAP(tkstest(a)foo-bar.de): Raw backtrace: imap [0x4648be] -> imap [0x4645fe] -> imap [0x443834] -> imap [0x450b08] -> imap(mail_index_open+0x1df) [0x444e6f] -> imap(index_storage_mailbox_init+0x159) [0x43c119] -> imap [0x41fe0d] -> imap [0x420ab8] -> imap(_cmd_select_full+0xaa) [0x4149ca] -> imap(cmd_select+0xb) [0x414b7b] -> imap [0x415e97] -> imap [0x415f29] -> imap(_client_input+0x6f) [0x4165cf] -> imap(io_loop_handler_run+0x101) [0x46a021] -> imap(io_loop_run+0x18) [0x4691f8] -> imap(main+0x457) [0x41e087] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b5ab1476ae4] -> imap [0x411719] May 27 18:05:44 ian dovecot: child 15320 (imap) killed with signal 6 Tested versions: 1.0.13 RPM by OpenSUSE 1.0.13 self-compiled 1.1.rc7 self-compiled OS: Linux ian 2.6.18.8-0.9-default #1 SMP Sun Feb 10 22:48:05 UTC 2008 x86_64 x86_64 x86_64 GNU/Linux configure: ./configure --prefix=/opt/dovecot --sysconfdir=/etc/dovecot --with-mysql --with-pop3d --with-notify=inotify --with-ioloop=epoll --with-sql CPPFLAGS='-fPIC -I/opt/mysql/include' LDFLAGS='-L/opt/mysql/lib -lmysqlclient -lz -lcrypt -lnsl -lm' Any ideas? Kind Regards Christian -- Christian Kuehn eMail: christian(a)hamburg.gay-web.de

2 1

[Dovecot] Requested CRAM-MD5 scheme, but we have only MD5-CRYPT
by Richard Pyne 01 Jun '08

01 Jun '08

After upgrading my dovecot installation about a month ago, I have started seeing "Requested CRAM-MD5 scheme, but we have only MD5-CRYPT" message from dovecot in my logs. Any help in finding and correcting the cause will be greatly appreciated. --Richard

2 4

Re: [Dovecot] Segfault in imap_bodystructure_write when searching
by Christer Mjellem Strand 01 Jun '08

01 Jun '08

>> Whenever I try to search on my dovecot test install, dovecot dies. It >> immediately spawns a new process, which the client tries to connect to, >> and send search commands to, causing that to die, and so forth. This loop >> means I have to kill either the server or the client. > > Your dovecot.index.cache file is probably broken somehow. Try moving > dovecot.index* files elsewhere and see if it works then? If it does and > dovecot.index.cache doesn't contain anything too sensitive > (subjects/from/to addresses), could you send me the dovecot.index* > files? > > If it crashes even without dovecot.index* files then the mails > themselves contain a broken message. It would help if I could get that > message. Bullseye. Why did I fail to mention that I was trying to use uiddb from Courier? :P Using your conversion script fixed it, but simply copying the Courier file crashed Dovecot. According to http://wiki.dovecot.org/Migration/Courier this is supposed to work though, so either that page is wrong, or Dovecot has a bug. >> betty - ~vpopmail/domains/bar.com/foo # gdb /usr/lib/dovecot/imap core > .. >> (no debugging symbols found) >> Core was generated by `imap'. >> Program terminated with signal 11, Segmentation fault. >> #0 0x080a539d in imap_bodystructure_write () >> (gdb) bt full >> #0 0x080a539d in imap_bodystructure_write () >> No symbol table info available. >> #1 0x08083b5c in ?? () > > Unfortunately this backtrace is almost completely broken and it doesn't > really help.. You also could try compiling Dovecot itself with debug > symbols and getting backtrace from it. That'd probably work. I tried reproducing now, but it seems it's started working even when moving all dovecot files and copying courierimapuiddb to dovecot-uidlist. If I see it again I'll send you a copy of the file offlist. Thanks. -- -==- -=- -==- Christer Mjellem Strand yitzhaq System administrator ICQ: 9557698 GSM +47 922 000 12 JID: yitzhaq(a)jabber.no -==- -=- -==-

2 7

Re: [Dovecot] Dovecot hard link problem
by Timo Sirainen 01 Jun '08

01 Jun '08

On Sun, 2008-06-01 at 23:27 +0900, 도원철 wrote: > My company recently changed mail server from cyrus to dovecot. > > The problem is that dovecot does not support hard links for message > files with same message ID. > > I turned on the ‘maildir_copy_with_hardlinks’ option in dovecot.conf, > but it does not seems to have relation to this problem, am I > misunderstood? > > Hard links are created when move or copy messages from one folder to > other folder, but when deliver creates messages this option does not > works. Right. This isn't implemented yet. Also I don't think it should rely on Message-ID: header proving the uniqueness. There are two ways this can be implemented reliably: 1) If the message is sent to multiple recipients using same RCPT TO command, all the recipients could be given to deliver as parameters, and deliver would know that it's the same message and they could be hard linked. 2) Keep some kind of a hash database where hash is e.g. SHA1 sum of the entire message. All messages could be then stored in some global directory and hard linked from there to users' mailboxes. When receiving a new message using an existing hash, it could still compare byte-by-byte the files to make sure that it's not a hash collision before hard linking the file. 1) probably wouldn't be too difficult to implement and probably would solve your problem (assuming the problem is that people are mailing 100MB attachments to everyone inside a company). But I don't think I have time to do it myself..

1 0

[Dovecot] Dovecot hard link problem
by 도원철 01 Jun '08

01 Jun '08

My company recently changed mail server from cyrus to dovecot. The problem is that dovecot does not support hard links for message files with same message ID. I turned on the ‘maildir_copy_with_hardlinks’ option in dovecot.conf, but it does not seems to have relation to this problem, am I misunderstood? Hard links are created when move or copy messages from one folder to other folder, but when deliver creates messages this option does not works. Our mail storage will be exhausted in few days. If you have some idea to solve this problem, please please help me. Or If you fix this problem, I will happily pay for it at reasonable cost. I installed dovecot 1.0.13 and postfix 2.5.1. Best regards, WonChul,Do

1 0

[Dovecot] Segfault in imap_bodystructure_write when searching
by Christer Mjellem Strand 01 Jun '08

01 Jun '08

Whenever I try to search on my dovecot test install, dovecot dies. It immediately spawns a new process, which the client tries to connect to, and send search commands to, causing that to die, and so forth. This loop means I have to kill either the server or the client. Running Dovecot 1.0.13 from/on Debian testing, rebuilt with vpopmail support and no other source changes. Vpopmail version is 5.4.25, latest stable. Client is Mulberry 4.0.8, and the crash seems to occur whenever any type of search is performed, be it subject, sender, body etc. Otherwise the server behaves fine. dovecot -n output: # 1.0.13: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S listen: *:9000 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_greeting_capability: yes login_max_processes_count: 256 first_valid_uid: 89 mail_location: maildir:~/Maildir mail_debug: yes dotlock_use_excl: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_drop_priv_before_exec: yes mail_plugins: quota imap_quota imap_client_workarounds: outlook-idle delay-newmail auth default: user: vpopmail verbose: yes passdb: driver: vpopmail userdb: driver: vpopmail plugin: quota: maildir Anonymized log excerpt: May 31 21:01:24 betty dovecot: imap-login: Login: user=<foo(a)bar.com>, method=PLAIN, rip=1.2.3.4, lip=4.3.2.1 May 31 21:01:24 betty dovecot: child 21748 (imap) killed with signal 11 May 31 21:01:24 betty dovecot: imap-login: Login: user=<foo(a)bar.com>, method=PLAIN, rip=1.2.3.4, lip=4.3.2.1 May 31 21:01:24 betty dovecot: child 21752 (imap) killed with signal 11 May 31 21:01:24 betty dovecot: imap-login: Login: user=<foo(a)bar.com>, method=PLAIN, rip=1.2.3.4, lip=4.3.2.1 May 31 21:01:25 betty dovecot: child 21753 (imap) killed with signal 11 May 31 21:01:25 betty dovecot: imap-login: Login: user=<foo(a)bar.com>, method=PLAIN, rip=1.2.3.4, lip=4.3.2.1 May 31 21:01:25 betty dovecot: child 21759 (imap) killed with signal 11 May 31 21:01:25 betty dovecot: imap-login: Login: user=<foo(a)bar.com>, method=PLAIN, rip=1.2.3.4, lip=4.3.2.1 May 31 21:01:25 betty dovecot: child 21774 (imap) killed with signal 11 May 31 21:01:25 betty dovecot: imap-login: Login: user=<foo(a)bar.com>, method=PLAIN, rip=1.2.3.4, lip=4.3.2.1 May 31 21:01:25 betty dovecot: child 21775 (imap) killed with signal 11 May 31 21:01:25 betty dovecot: imap-login: Login: user=<foo(a)bar.com>, method=PLAIN, rip=1.2.3.4, lip=4.3.2.1 May 31 21:01:25 betty dovecot: child 21776 (imap) killed with signal 11 ... Backtrace: betty - ~vpopmail/domains/bar.com/foo # gdb /usr/lib/dovecot/imap core GNU gdb 6.7.1-debian Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". warning: Can't read pathname for load map: Input/output error. Reading symbols from /lib/i686/cmov/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/i686/cmov/libdl.so.2 Reading symbols from /lib/i686/cmov/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/i686/cmov/libc.so.6 Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so Reading symbols from /usr/lib/dovecot/modules/imap/lib11_imap_quota_plugin.so... (no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/modules/imap/lib11_imap_quota_plugin.so Reading symbols from /usr/lib/gconv/ISO8859-1.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/gconv/ISO8859-1.so (no debugging symbols found) Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. #0 0x080a539d in imap_bodystructure_write () (gdb) bt full #0 0x080a539d in imap_bodystructure_write () No symbol table info available. #1 0x08083b5c in ?? () No symbol table info available. #2 0x080fa698 in ?? () No symbol table info available. #3 0x080fae60 in ?? () No symbol table info available. #4 0x00000001 in ?? () No symbol table info available. #5 0x080fa660 in ?? () No symbol table info available. #6 0x080fae40 in ?? () No symbol table info available. #7 0x080fae40 in ?? () No symbol table info available. #8 0xbfc90328 in ?? () No symbol table info available. #9 0x080b0520 in _buffer_free () No symbol table info available. #10 0x08083f64 in index_mail_get_special () No symbol table info available. #11 0x080703f4 in ?? () No symbol table info available. #12 0x080f8c08 in ?? () No symbol table info available. #13 0x00002000 in ?? () No symbol table info available. #14 0x00000001 in ?? () No symbol table info available. #15 0x080bc105 in o_stream_send_str () No symbol table info available. #16 0x0805f26e in ?? () No symbol table info available. #17 0x080f8c08 in ?? () No symbol table info available. #18 0x00002000 in ?? () No symbol table info available. #19 0x00000001 in ?? () No symbol table info available. #20 0x00000000 in ?? () Any help would be greatly appreciated. -- -==- -=- -==- Christer Mjellem Strand yitzhaq System administrator ICQ: 9557698 GSM +47 922 000 12 JID: yitzhaq(a)jabber.no -==- -=- -==-

2 1

[Dovecot] fetchmail on demand
by Graeme Vetterlein 31 May '08

31 May '08

I hoping this is an RTFM ... and somebody can point me at the correct 'FM' :-) I've just spent a while setting my new Debian , allways-on box in what I suspect is a generally useful configuration. I have fetchmail(1) collect mail from many mailboxes via pop3. I store these mails in different mboxs according to rules in procmail(1) I then offer these out to the household via imap in dovecot(1) . I have fetchmail(1) set to poll the ISPs every 5 minutes, this seems to work fine, but there are two issues: 1: The constant polling keeps the disk spinning for no good reason (most of the time) 2: If I check my mail via a mail reader using imap to the local mboxes ...there could be mail sitting on the ISP servers I don't see (for 5 mins) Now what would be much nicer, would simply be to have dovecot(1) issue the fetchmail(1) command whenever it it got an imap request. I general what I guess I would like is: "When a request comes in (via imap) fork off a command who's name is given in the conf file. ... imap_pre_cmd="xxx" -- Graeme

3 2

[Dovecot] Sieve Editheader Extension?
by Michael K Sanders 31 May '08

31 May '08

I've done extensive searches, and there is virtually no information about actual implementations of the draft Sieve Editheader Extension (which provides 'addheader' and 'deleteheader' actions): http://www.ietf.org/internet-drafts/draft-ietf-sieve-editheader-11.txt Is anyone currently working on this for Dovecot Sieve? If not, are there any plans to do so? And before I start digging through the source, is the architecture amenable to this functionality? Thanks, :: Mike ::

2 1

[Dovecot] dovecot-1.1.rc7 Panic: POP3(username): file index-mail.c: line 1007: unreached
by Diego Liziero 31 May '08

31 May '08

And got this regression with dovecot-1.1.rc7 with each pop3 connection, hg version of 2 days ago was working fine. Now I'm back again to hg before "Message sort index handling rewrite". Regards, Diego. --- Panic: POP3(username): file index-mail.c: line 1007: unreached (gdb) bt #0 0x00b91402 in __kernel_vsyscall () #1 0x00725ba0 in raise () from /lib/libc.so.6 #2 0x007274b1 in abort () from /lib/libc.so.6 #3 0x080c3f0d in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:152 #4 0x080c3f5a in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80d8210 "file %s: line %d: unreached", args=0xbfeec684 "3ï¿½\r\bï¿½\003") at failures.c:418 #5 0x080c37fc in i_panic (format=0x80d8210 "file %s: line %d: unreached") at failures.c:193 #6 0x08089a60 in index_mail_get_special (_mail=0x963cbe0, field=6, value_r=0xbfeec70c) at index-mail.c:1007 #7 0x0805aac5 in list_uids_iter (client=0x9636f68, ctx=0x96389a0) at commands.c:566 #8 0x0805ad31 in client_command_execute (client=0x9636f68, name=0x963b37c "UIDL", args=0x80dc0c2 "") at commands.c:642 #9 0x08059f92 in client_input (client=0x9636f68) at client.c:413 #10 0x080cb7c0 in io_loop_handler_run (ioloop=0x96359b0) at ioloop-epoll.c:201 #11 0x080ca9c8 in io_loop_run (ioloop=0x96359b0) at ioloop.c:308 #12 0x0805bbfc in main (argc=Cannot access memory at address 0x4c52 ) at main.c:275

2 2

[Dovecot] Panic: Trying to close mailbox INBOX with open transactions
by Diego Liziero 31 May '08

31 May '08

Got this using dovecot-1.1 (hg version of 2 days ago). I mean with http://hg.dovecot.org/dovecot-1.1/rev/c4342385d696 included. Regards, Diego. ----- Panic: IMAP(username): Trying to close mailbox INBOX with open transactions (gdb) bt #0 0x007c3402 in __kernel_vsyscall () #1 0x00138ba0 in raise () from /lib/libc.so.6 #2 0x0013a4b1 in abort () from /lib/libc.so.6 #3 0x080d49f0 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:152 #4 0x080d523a in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80f6c34 "Trying to close mailbox %s with open transactions", args=0xbf8648c4 "8^\\\bï¿½H\206ï¿½ï¿½ï¿½\005\b\210ï¿½[\bNï¿½\016\bï¿½H\206ï¿½NI\016\bï¿½ï¿½[\bhï¿½[\b\030I\206ï¿½ï¿½\023\006\bï¿½ï¿½[\bï¿½ï¿½[\b\bI\206ï¿½2ï¿½\016\bï¿½ï¿½[\bï¿½$") at failures.c:418 #5 0x080d4b2a in i_panic (format=0x80f6c34 "Trying to close mailbox %s with open transactions") at failures.c:193 #6 0x080a5126 in mailbox_close (_box=0x6) at mail-storage.c:471 #7 0x0805edb8 in cmd_logout (cmd=0x85bd7d8) at cmd-logout.c:18 #8 0x080613dc in client_command_cancel (_cmd=0x85bd3c4) at client.c:75 #9 0x08061662 in client_destroy (client=0x85bd368, reason=0x80eee5b "Connection closed") at client.c:134 #10 0x0806285e in client_input (client=0x85bd368) at client.c:697 #11 0x080df05a in io_loop_handler_run (ioloop=0x85bb9b0) at ioloop-epoll.c:201 #12 0x080de2a2 in io_loop_run (ioloop=0x85bb9b0) at ioloop.c:308 #13 0x0806dd14 in main (argc=1, argv=0xbf864ab4, envp=0xbf864abc) at main.c:293

2 1