July 2008 - dovecot - dovecot.org

[Dovecot] dovecot.sieve file location?
by kbajwa 28 Jul '08

28 Jul '08

CentOS 5.2 Postfix-2.3.3 Dovecot-1.1.1 Dovecot.Sieve-1.1.5 I have setup with: home_mailbox = Maildir/ (/etc/postfix/main.cf) & mail-location = maildir:~/Maildir (/etc/dovecot.conf) I have created a 'test' user to test Sieve 'Vacation' setup. My questions are: 1. Which folder '.dovecot.sieve' script is copied into? Is it 'home/test' -or- 'home/test/Maildir' or someplace else? 2. '.dovecot.sieve' script parameter ":days 1" means that the reply is sent once a day. Is it possible to send the reply 'immediately'? Kirti

1 0

Re: [Dovecot] Error - Dovecot Permission denied
by Sahil Tandon 28 Jul '08

28 Jul '08

kbajwa <kbajwa(a)tibonline.net> wrote: > I have posted the permissions on another post. However, when I look at > "properties" & then "permissions" for 'dovecot.conf' file, following are the > 'permissions' listed: > > Owner: dovecot > Access: Read & Write > > Group: Mail > Access: Read-Only > > Others > Access: none This is the problem. The mailbox_command runs neither as the dovecot user nor with the mail GID. You need to give others access to read the file. # chmod o+r /etc/dovecot.conf > > Execute: [] Allow executing file as program > SELinux Context: file_t > > I hope it makes sense to you, it does not to me. > > Let me know if the above need some change. [...] -- Sahil Tandon <sahil(a)tandon.net>

2 1

[Dovecot] mail extra field to override default mail_location for only certain users
by Sahil Tandon 27 Jul '08

27 Jul '08

I am running version 1.1.1 with mail_location: maildir:~/Maildir. This is working great as all our users have UNIX accounts with nologin shells. New domains (and their users) are about to come online and we would like to migrate to a setup with virtual mailboxes/users. From the wiki and comments within dovecot.conf, I see it is possible to do this piecemeal so both local and virtual users can co-exist during the transition. My question is how to keep things working as they are for existing users/domains (which will be migrated later), and use the virtual mailboxes (and thus, a different mail_location) exclusively for the new users. I understand that multiple userdbs and passdbs can be specified, and this will take care of authentication. On http://wiki.dovecot.org/VirtualUsers#homedirs it is stated that "The userdb can return the mail extra field to override the default mail_location setting. Usually you shouldn't need this." Where is this mail extra field defined? In the userdb passwd-file or somewhere within dovecot.conf? If the former, would something like this suffice (mind the wrapping): user@domain.org::5000:5000::/home/vhosts/domain.org/:/usr/sbin/nologin::mail=m aildir:/home/vhosts/%d/%n Thanks, -- Sahil Tandon <sahil(a)tandon.net>

1 1

[Dovecot] trace shows imap proceses stuck listing folders
by Ryan Rawdon 27 Jul '08

27 Jul '08

I just moved my mail setup from one machine to a new one. After doing so, I've encountered a problem where imap processes will start accumulating, stuck in a loop eating loads of IO. Below is a trace

1 0

Re: [Dovecot] how to store flags \Seen into read-only mailbox?
by seriv＠parkheights.dyndns.org 25 Jul '08

25 Jul '08

I was looking for workaround, and tried to use one uid for all users, and ACL plugin to give permissions like: --- owner lrwstiekxa anyone rls --- rls should mean read, lookup and write-seen. Read and lookup works, and as soon as I remove these letters I can't read mail folder. But 's' is not working, I'm getting the same: --- 7 OK Store ignored with read-only mailbox. --- in rawlogs I can not find a way for users to keep their own track of what messages have been \Seen in read-only shared folder. -- Sergey Ivanov. ----- seriv(a)parkheights.dyndns.org wrote: > This problem is apparently about changeset > http://hg.dovecot.org/dovecot-1.1/rev/eec74a6ad62e. > This change makes dovecot behaviour different from what is described > in wiki, about sharing and making private /Seen flags, > see http://wiki.dovecot.org/SharedMailboxes?highlight=(flags are > shared or private) > When I've tried to revert it, first time with my client it worked > perfectly. > But then clients were not able to open any mail folders, and imap > processes were dying. > -- > Sergey Ivanov.

1 1

[Dovecot] quota vs. antispam issue
by Johannes Berg 25 Jul '08

25 Jul '08

Can you help me maybe? I don't see the bug. QUOTA=maildir QUOTA_RULE='*:storage=100M' MAIL_PLUGINS="antispam quota" MAIL_PLUGIN_DIR=/home/johannes/Projects/dovecot/antispam gdb --args /home/johannes/Projects/dovecot/dovecot-1.1/src/imap/imap GNU gdb 6.8-debian Copyright (C) 2008 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 "powerpc-linux-gnu"... (gdb) run Starting program: /home/johannes/Projects/dovecot/dovecot-1.1/src/imap/imap * PREAUTH [CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1] Logged in as johannes 01 select SPAM * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 8 EXISTS * 0 RECENT * OK [UIDVALIDITY 1212140311] UIDs valid * OK [UIDNEXT 9] Predicted next UID 01 OK [READ-WRITE] Select completed. A003 APPEND SPAM () {2} + OK ab Program received signal SIGSEGV, Segmentation fault. 0x100929f4 in mail_get_physical_size (mail=0x0, size_r=0xbfeaf030) at mail.c:100 100 return p->v.get_physical_size(mail, size_r); (gdb) bt #0 0x100929f4 in mail_get_physical_size (mail=0x0, size_r=0xbfeaf030) at mail.c:100 #1 0x0fe29be0 in quota_try_alloc (ctx=0x101707a8, mail=0x0, too_large_r=0xbfeaf060) at quota.c:818 #2 0x0fe303dc in quota_check (t=0x10170158, mail=0x0) at quota-storage.c:148 #3 0x0fe30968 in quota_save_finish (ctx=0x10177c10) at quota-storage.c:251 #4 0x0fdfec58 in antispam_save_finish (ctx=0x10177c10) at antispam-storage-1.1.c:178 #5 0x10097c94 in mailbox_save_finish (_ctx=0x10159004) at mail-storage.c:738 #6 0x10016988 in cmd_append_continue_message (cmd=0x10158f98) at cmd-append.c:408 #7 0x10015804 in client_input_append (cmd=0x10158f98) at cmd-append.c:79 #8 0x101029e0 in io_loop_handler_run (ioloop=0x10154aa8) at ioloop-epoll.c:201 #9 0x10101514 in io_loop_run (ioloop=0x10154aa8) at ioloop.c:308 #10 0x1003094c in main (argc=1, argv=0xbfeaf4b4, envp=0xbfeaf4bc) at main.c:293 I'll keep digging but I don't see why return quota_check(ctx->transaction, ctx->dest_mail != NULL ? ctx->dest_mail : qt->tmp_mail); should pass NULL in the second argument. johannes

4 11

[Dovecot] dovecot 1.1.2, another assertion failure in index-mail.c: (!mail->data.destroying_stream)
by Diego Liziero 25 Jul '08

25 Jul '08

Here is the log. --- dovecot: Jul 25 07:18:35 Panic: IMAP(user): file index-mail.c: line 1091 (index_mail_close): assertion failed: (!mail->data.destroying_stream) dovecot: Jul 25 07:18:35 Error: IMAP(user): Raw backtrace: /usr/libexec/dovecot/imap [0x80f5fd4] -> /usr/libexec/dovecot/imap [0x80f6877] -> /usr/libexec/dovecot/imap(i_fatal+0) [0x80f6130] -> /usr/libexec/dovecot/imap(index_mail_close+0xf9) [0x80a8129] -> /usr/libexec/dovecot/imap [0x80a8148] -> /usr/libexec/dovecot/imap(index_mail_set_seq+0x50) [0x80a8302] -> /usr/libexec/dovecot/imap [0x8087e3b] -> /usr/libexec/dovecot/imap(mail_set_seq+0x21) [0x80b391c] -> /usr/libexec/dovecot/imap(index_storage_search_next_nonblock+0xcb) [0x80ad3e8] -> /usr/libexec/dovecot/imap(mailbox_search_next_nonblock+0x26) [0x80b6a97] -> /usr/libexec/dovecot/imap(mailbox_search_next+0x2c) [0x80b6a63] -> /usr/libexec/dovecot/imap [0x805b757] -> /usr/libexec/dovecot/imap(cmd_copy+0x1c4) [0x805b98e] -> /usr/libexec/dovecot/imap(cmd_uid+0xbb) [0x80610d3] -> /usr/libexec/dovecot/imap [0x8062494] -> /usr/libexec/dovecot/imap [0x80626c9] -> /usr/libexec/dovecot/imap [0x80627c7] -> /usr/libexec/dovecot/imap [0x8062803] -> /usr/libexec/dovecot/imap(client_input+0xb7) [0x8062991] -> dovecot: Jul 25 07:18:35 Error: IMAP(user): /usr/libexec/dovecot/imap(io_loop_handler_run+0x17d) [0x8100630] -> /usr/libexec/dovecot/imap(io_loop_run+0x35) [0x80ff8de] -> /usr/libexec/dovecot/imap(main+0xe4) [0x806de1d] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x42bdec] -> /usr/libexec/dovecot/imap [0x805a1a1] dovecot: Jul 25 07:18:35 Error: child 27074 (imap) killed with signal 6 dovecot: Jul 25 07:18:35 Error: IMAP(user): Corrupted transaction log file /mailhome/user/.imap/Trash/dovecot.index.log: record size too small (type=0x40, offset=56, size=0) dovecot: Jul 25 07:18:36 Error: IMAP(user): Corrupted transaction log file /mailhome/user/.imap/Trash/dovecot.index.log: record size too small (type=0x40, offset=56, size=0) dovecot: Jul 25 07:19:33 Error: IMAP(user): Corrupted transaction log file /mailhome/user/.imap/Trash/dovecot.index.log: record size too small (type=0x40, offset=56, size=0) dovecot: Jul 25 07:19:42 Error: IMAP(user): Corrupted transaction log file /mailhome/user/.imap/Trash/dovecot.index.log: record size too small (type=0x40, offset=56, size=0) dovecot: Jul 25 07:19:48 Warning: IMAP(user): fscking index file (in-memory index) dovecot: Jul 25 07:19:48 Error: IMAP(user): Transaction log got desynced for index (in-memory index)

1 0

[Dovecot] Dovecot 1.1.2, SIGABRT on copy mail
by Andreas M. Kirchwitz 25 Jul '08

25 Jul '08

Hi folks, with the brandnew release Dovecot 1.1.2, the daemon killed itself with signal 6 (SIGABRT) when trying to save a mail from the INBOX to another folder. The mail client is PINE 4.64. After reconnecting to the IMAP server, the mail was actually copied to the destination folder, but the original mail was still in the INBOX and not flagged as "deleted". This is the panic: Jul 25 02:13:25 linux dovecot: Panic: IMAP(user2): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) Jul 25 02:13:25 linux dovecot: IMAP(user2): Raw backtrace: imap [0x80cf8e0] -> imap [0x80cf93a] -> imap [0x80cf26c] -> imap [0x809d11a] -> imap(index_mailbox_set_recent_seq+0x3e) [0x809d15e] -> imap(mbox_sync+0x105d) [0x80823fd] -> imap [0x807a454] -> imap(index_transaction_commit+0x4e) [0x809ddfe] -> imap(cmd_copy+0x35f) [0x805b26f] -> imap [0x805fd7c] -> imap [0x805fe25] -> imap [0x80605e5] -> imap(client_input+0x5e) [0x80607fe] -> imap(io_loop_handler_run+0x100) [0x80d7230] -> imap(io_loop_run+0x28) [0x80d63c8] -> imap(main+0x4a1) [0x8068321] -> /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] -> imap [0x805a101] Jul 25 02:13:25 linux dovecot: child 7954 (imap) killed with signal 6 Thus, the daemon died somewhere between successfully saving a copy of the mail from INBOX to the destination folder and flagging it to be deleted in the INBOX. Just a couple of minutes later, Dovecot died again. Wanted to save a message from INBOX to another folder. But this time, the message wasn't written to the destination folder. As before, the original mail in the INBOX didn't change any flags. Jul 25 02:22:07 linux dovecot: Panic: IMAP(user2): file message-parser.c: line 770 (message_parser_parse_next_block): assertion failed: (ctx->input->eof || ctx->input->closed || ctx->input->stream_errno != 0 || ctx->broken) Jul 25 02:22:07 linux dovecot: IMAP(user2): Raw backtrace: imap [0x80cf8e0] -> imap [0x80cf93a] -> imap [0x80cf26c] -> imap(message_parser_parse_body+0) [0x80c8ba0] -> imap(message_parser_parse_body+0x1e) [0x80c8bbe] -> imap [0x8095120] -> imap [0x809528c] -> imap(index_mail_get_special+0x3a7) [0x8095757] -> imap [0x8061b94] -> imap(imap_fetch+0x148) [0x80620f8] -> imap(cmd_fetch+0x28e) [0x805bcae] -> imap [0x805fd7c] -> imap [0x805fe25] -> imap [0x80605e5] -> imap(client_input+0x5e) [0x80607fe] -> imap(io_loop_handler_run+0x100) [0x80d7230] -> imap(io_loop_run+0x28) [0x80d63c8] -> imap(main+0x4a1) [0x8068321] -> /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] -> imap [0x805a101] Jul 25 02:22:07 linux dovecot: child 17931 (imap) killed with signal 6 The error cannot be reproduced with these messages. They can be saved/copied now without problems back and forth. I've tried to send more mail and reproduce the problem, but no success. Works perfectly fine. Dovecot 1.1.2 is running on Fedora 8 Linux 32 Bit with all patches and custom OpenSSL 0.9.8h. [ output of "dovecot -n" ] # 1.1.2: /usr/local/dovecot/etc/dovecot.conf ssl_cert_file: /usr/local/dovecot/etc/dovecot.crt ssl_key_file: /usr/local/dovecot/etc/dovecot.key login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login mail_location: mbox:~/Mail:INBOX=/var/spool/mail/%u auth default: mechanisms: plain login digest-md5 cram-md5 passdb: driver: passwd-file args: /usr/local/dovecot/etc/dovecot.passwd userdb: driver: passwd-file args: /usr/local/dovecot/etc/dovecot.passwd The problem was reported by a user who continued to work with his mail folders. I was only a few seconds too late to grab a copy of the INBOX and index files. Greetings, Andreas

1 0

[Dovecot] dovecot 1.1.2 dbox file_dotlock_open() failed with file
by Robert Schetterer 25 Jul '08

25 Jul '08

Hi Timo, i have failures like with deleting a folder in the log dovecot: Jul 25 02:12:14 Error: IMAP(.....com): file_dotlock_open() failed with file /usr/local/virtual/.../...@....com/zzzz/dbox-Mails/dovecot.index.log: No such file or directory with short tests i cant see any real problem folder can be created and deleted with thunderbird ( but only with tb-extra-mailbox-sep enabled ) its not a new log entry to dovecot 1.1.2 but this is first time i noticed , by near expection of the log after update, and of course i missed it by playing so much with configs -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 0

[Dovecot] dovecot.conf permissions
by Dan Horák 24 Jul '08

24 Jul '08

Hi, I have a little problem with defining the right permissions for dovecot.conf. The main problem is that the password for SSL certificates is stored there and the conf file is world readable by default, which makes a security problem [1]. It is not a problem to restrict the permissions to 0600, dovecot will still work, but then deliver cannot work as it reads the conf too, but it runs under arbitrary user. So my last iteration is 0640 as permission and root:mail as ownership, but that expects that deliver is run with group = mail. For the long term solution I would prefer to move the password into a separate config file so the permissions can be properly restricted there. What are your opinions? With regards, Dan [1] https://bugzilla.redhat.com/show_bug.cgi?id=436287 -- Fedora and Red Hat package maintainer

3 2