February 2012 - dovecot

[Dovecot] Managesieve Build failure
by Ralf Hildebrandt 04 Feb '12

04 Feb '12

I pulled the recent dovecot-2.0-pigeonhole and dovecot 2.0.x trees and rebuild, got this error today: ... make[3]: Leaving directory /usr/src/dovecot-2.0/dovecot-2.0-pigeonhole/src/managesieve' make[2]: Leaving directory /usr/src/dovecot-2.0/dovecot-2.0-pigeonhole/src/managesieve' Making install in managesieve-login make[2]: Entering directory /usr/src/dovecot-2.0/dovecot-2.0-pigeonhole/src/managesieve-login' /bin/bash ../../libtool --tag=CC --mode=link gcc -I/usr/src/dovecot-2.0/dovecot-2.0/src/config -DPKG_LIBEXECDIR=\""/usr/local/libexec/dovecot"\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -module -avoid-version -g -Wl,--as-needed -o libmanagesieve_login_settings.la -rpath /usr/local/lib/dovecot/settings libmanagesieve_login_settings_la-managesieve-login-settings.lo libmanagesieve_login_settings_la-managesieve-login-settings-plugin.lo -lrt gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/src/dovecot-2.0/dovecot-2.0 -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-dict -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-dns -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-mail -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-imap -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-fs -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-charset -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-index -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-storage -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-storage/index -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-storage/index/raw -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-master -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-settings -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-auth -I/usr/src/dovecot-2.0/dovecot-2.0/src/login-common -I../.. -I../../src/lib-managesieve -g -Wl,--as-needed -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT managesieve-proxy.o -MD -MP -MF .deps/managesieve-proxy.Tpo -c -o managesieve-proxy.o managesieve-proxy.c managesieve-proxy.c: In function ‘managesieve_proxy_parse_line’: managesieve-proxy.c:334:19: error: ‘const struct login_settings’ has no member named ‘verbose_auth’ make[2]: *** [managesieve-proxy.o] Error 1 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 1

[Dovecot] Vacation via database
by list＠airstreamcomm.net 04 Feb '12

04 Feb '12

We are moving our inbound mail to use dovecot LMTP in the near future and we are looking for suggestions on how to implement a mysql based vacation system. If anyone has experience with this, good or bad please let us know.

5 6

[Dovecot] LDAP auth improvements
by Timo Sirainen 03 Feb '12

03 Feb '12

v2.1 supports now multiple LDAP fields in a template e.g.: user_attrs = \ homeDirectory=home, \ uidNumber=uid, \ gidNumber=gid, \ =mail=%{ldap:mailboxFormat}:%{ldap:homeDirectory} which is the same as: user_attrs = \ =home=%{ldap:homeDirectory}, \ =uid=%{ldap:uidNumber}, \ =gid=%{ldap:gidNumber}, \ =mail=%{ldap:mailboxFormat}:%{ldap:homeDirectory} I was also thinking about adding an alternative simplified syntax for this: user_attrs { home = %{ldap:homeDirectory} uid = %{ldap:uidNumber} gid = %{ldap:gidNumber} mail = %{ldap:mailboxFormat}:%{ldap:homeDirectory} } Any ideas for further improvements before I do this change? One thing I'm still wondering about is what I should do when LDAP returns multiple values. Like perhaps: acl_groups = %{ldap:aclGroups:,} Which would mean that all the aclGroups values would be joined together separated by "," characters. And a bit more complex with multiple gidNumbers: gid = %{ldap:gidNumber[0]} mail_access_groups = %{ldap:gidNumber[1:]:,}

2 1

[Dovecot] Errors starting Dovecot
by Andre Lopes 03 Feb '12

03 Feb '12

Hi, I'm new to Dovecot. I'm trying to start Dovecot(2.0.9) but I'm getting an error. I think the error is because I'm doing a tutorial for an old version of Devcot(1.x.x). What I get is the following: [code] [root@mailserver dovecot]# service dovecot start Starting Dovecot Imap: doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1: protocols=imaps is no longer necessary, remove it doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1: protocols=pop3s is no longer necessary, remove it doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:5: ssl_cert_file has been replaced by ssl_cert = <file doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:6: ssl_key_file has been replaced by ssl_key = <file doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:8: namespace private {} has been replaced by namespace { type=private } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:24: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:25: auth_user has been replaced by service auth { user } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:27: passdb sql {} has been replaced by passdb { driver=sql } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:31: userdb static {} has been replaced by userdb { driver=static } [ OK ] [/code] My dovecot.conf have the following: [code] protocols = imap imaps pop3 pop3s log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/vmail/%d/%n/Maildir ssl_cert_file = /etc/pki/dovecot/certs/dovecot.pem ssl_key_file = /etc/pki/dovecot/private/dovecot.pem namespace private { separator = . prefix = INBOX. inbox = yes } protocol lda { log_path = /home/vmail/dovecot-deliver.log auth_socket_path = /var/run/dovecot/auth-master postmaster_address = postmaster(a)example.com } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } auth default { user = root passdb sql { args = /etc/dovecot-sql.conf } userdb static { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } [/code] Any clues on how can I adapt this configuration file to Dovecot 2.0.9? Best Regards,

1 0

[Dovecot] Doubts about dsync, mdbox, SIS
by Jan-Frode Myklebust 03 Feb '12

03 Feb '12

I've been running continous dsync backups of our Maildirs for a few weeks now, with the destination dsync server using mdbox and SIS. The idea was that the destination server would act as a warm copy of all our active users data. The active servers are using Maildir, and has: $ df -h /usr/local/atmail/users/ Filesystem Size Used Avail Use% Mounted on /dev/atmailusers 14T 12T 2.2T 85% /usr/local/atmail/users $ df -hi /usr/local/atmail/users/ Filesystem Inodes IUsed IFree IUse% Mounted on /dev/atmailusers 145M 113M 33M 78% /usr/local/atmail/users very little of this is compressed (zlib plugin enabled during christmas). I'm surprised that the destination server is so large, was expecting zlib and mdbox and SIS would compress it down to much less than what we're seeing (12TB -> 5TB): $ df -h /srv/mailbackup Filesystem Size Used Avail Use% Mounted on /dev/mapper/mailbackupvg-mailbackuplv 5.7T 4.8T 882G 85% /srv/mailbackup Lots and lots of the attachement storage is duplicated into identical files, instead of hard linked. When running "doveadm purge -u $user", we're seeing lots of Error: unlink(/srv/mailbackup/attachments/c3/17/c317b32b97688c16859956f11b803e3bba434349-057274283bb51f4f917e0000bf34f6ab) failed: No such file or directory "/srv/mailbackup/attachments/c3/17/c317b32b97688c16859956f11b803e3bba434349-057274283bb51f4f917e0000bf34f6ab" is missing, but there are 205 other copies of this file named /srv/mailbackup/attachments/c3/17/c317b32b97688c16859956f11b803e3bba434349-* with identical sha1sum. Also we see corrupted indexes during the purge. This makes me quite uncertain if dsync is a workable backup solution.. or if we can trust mdboxes. Also on the source side, during dsync, we see too many problems. Some samples: Error: Mailboxes don't have unique GUIDs: 08b46439069d3d4db0490000e671bf84 is shared by INBOX and INBOX Error: command BOX-LIST failed Error: Worker server's mailbox iteration failed Error: read() from worker server failed: EOF Error: Failed to sync mailbox INBOX.ferie 2006.: Invalid mailbox name Error: read() from proxy client failed: EOF Error: Unexpected finish reply: 1 596fec275888dbd89f6d1f5356c22db6 3720 0 \dsync-expunged 0 Error: Unexpected reply from server: 1 12200572a70726fca946da6f9378dc03 3721 0 \dsync-expunged 0 Error: Failed to sync mailbox INBOX.INBOX.Gerda: Mailbox doesn't exist: INBOX/Gerda Error: command BOX-LIST failed Error: read() failed: Broken pipe Panic: file dsync-worker-local.c: line 1678 (local_worker_save_msg_continue): assertion failed: (ret == -1) Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x367703c680] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x35) [0x367703c765] -> /usr/lib64/dovecot/libdovecot.so.0 [0x367703bb93] -> /usr/bin/dsync [0x40f48d] -> /usr/bin/dsync [0x40f589] -> /usr/bin/dsync(dsync_worker_msg_save+0x8e) [0x40eb3e] -> /usr/bin/dsync [0x40d71a] -> /usr/bin/dsync [0x40cdbf] -> /usr/bin/dsync [0x40d105] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x48) [0x3677047278] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0xd5) [0x36770485c5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x2d) [0x367704720d] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x3677035a83] -> /usr/bin/dsync(main+0x71e) [0x406c4e] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3e3941d994] -> /usr/bin/dsync [0x406369] Do you have any idea for what our problems might be? Should we: avoid SIS ? avoid doing Maildir on one side and mdbox on the other? try other dovecot version for dsync? anything else? -jf ------------- destination server, running dovecot v2.0.14 -------- mail_attachment_dir = /srv/mailbackup/attachments mail_location = mdbox:~/mdbox mail_plugins = zlib mdbox_rotate_size = 5 M namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { driver = static } plugin { zlib_save = gz zlib_save_level = 9 } protocols = service auth-worker { user = $default_internal_user } service auth { unix_listener auth-userdb { mode = 0600 user = mailbackup } } ssl = no userdb { args = home=/srv/mailbackup/%256Hu/%d/%n driver = static } -------------/destination server -------- -jf

3 7

[Dovecot] Feature request - search and tag protocol - notmuch-alike approach
by Kirill A. Shutemov 03 Feb '12

03 Feb '12

Hi all, notmuch[1] becomes more and more popular. At least in geek community. But notmuch is local-only (except ssh)... It looks like it's hard (if even possible) to use IMAP as transport for notmuch-alike work flow. I think it would be great to create a new protocol based global search and message tagging. All core notmuch operations (search, show, count, tag) can be mapped to the new protocol (more or less) directly. Search syntax can be reused as is, I think. The tricky part is initial tagging. It requires some kind of transaction to be able to tag new messages without racing with upcoming messages. Request (command) syntax can be similar to unix command. This way we can reuse notmuch syntax even deeper. Like: search --limit 10 --sort=oldest-first tag:to-me tag:unread Replies are often structured. I think it's reasonable to use JSON for all replies. Any ideas? I've started to write a proof-of-concept, but it moves too slow, since my knowledge of dovecot internals is poor and it's hard to find time for the project. I hope somebody else has similar idea in mind and just wait opportunity to discuss the idea and start to write code. ;) [1] http://notmuchmail.org/ -- Kirill A. Shutemov

1 0

[Dovecot] converting from mbox to maildir ?
by Frank Bonnet 02 Feb '12

02 Feb '12

Hello We are planning to convert our mailhub ( freebsd 7.4 ) from mbox format to maildir format. I've read the documentation and performed some tests on another machine it is a bit long ... I would like some feedback from guys who did this operation and need some advice on what to convert first ? - first convert INBOX then convert IMAP folders ? - first convert IMAP folders then convert INBOX ? the machine use real users thru openldap ( pam_ldap + nss_ldap ) another problem is disk space. The users's email data takes about 2 Terabytes of data and I cannot duplicate as I only have 3 Tb on the raid array of the server. My idea is to use one of our NFS netapp filer during the convertion to throw the result of the convertion on an NFS mounted directory. Anyone did this before ? If yes I would be greatly interrested by their experience Thank you

2 6

[Dovecot] locking problem
by myron 02 Feb '12

02 Feb '12

I have one user who can't read his e-mail. The /var/log/mail.log file has this statement. dovecot: IMAP(<user>): Timeout while waiting for lock for transaction log file /users/<user>/mail/.imap/INBOX/dovecot.index.log I tried killing the imap daemons and removing the lock file, but it keeps coming back. Any idea what else to do? This is the dovecot file: dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-28-server x86_64 Ubuntu 10.04.3 LTS log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/certs/ssl-cert-snakeoil.pem ssl_key_file: /etc/ssl/private/ssl-cert-snakeoil.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth-client mode: 432 user: postfix group: postfix --myron ================================= Myron Kowalski MoCoSIN Network/Systems Administrator Moravian College myron(a)moravian.edu (610) 861-1441

2 4

[Dovecot] Renaming user account / mailbox
by Nikolaos Milas 02 Feb '12

02 Feb '12

Hello, I am running dovecot-2.0.13-1_128.el5 x86_64 RPM on CentOS 5.7. All accounts are virtual, hosted on LDAP Server. We are using Maildir mailboxes. The question: What is the process to rename an existing account/mailbox? I would like to rename userx with email: userx(a)example.com to ux(a)example.com with a mailbox of ux (currently: userx) Of course the idea is that new mail will continue to be delivered to the same mailbox, although it has been renamed. How can I achieve it? Would it be enough (after changing the associated data in the associated LDAP entry) to simply rename the virtual user directory name, e.g. from /home/vmail/userx to /home/vmail/ux ? Thanks in advance, Nick

2 2

[Dovecot] Site-wide configurable Sieve
by Gedalya 01 Feb '12

01 Feb '12

Hi, I need some sieve actions to be specified per-user, but exposing actual sieve scripts to users is of the question. For example, I need to be able to either put spam messages into a spam folder, or discard them, based on user preference. Presumably this would be done using Sieve. As I understand, it's not possible to query a database from within a sieve script. If I can't use a single global script, I can imagine automatically generating per-user scripts when settings are saved in a GUI (e.g. webmail) and store them on the dovecot machine. This would work but I would love to hear if someone has a smarter, more robust idea. Thanks, Gedalya

1 0