- dovecot - dovecot.org

[Dovecot] doveadm purge on shared storage
by Jan-Frode Myklebust 06 Feb '12

06 Feb '12

We've finally (!) started to put some users on mdbox instead of maildir, and now I'm wondering about the purge step. As we're running GPFS for the mailboxes (and dovecot director in front of every dovecot service), is it important to run the "doveadm purge -u $user" on the same host as $user is logged into to avoid index corruption ? If so, will we need to run the "doveadm purge" trough the dovecot director as well? -jf

2 1

Re: [Dovecot] Sieve notify messages
by Stephan Bosch 05 Feb '12

05 Feb '12

On 2/5/2012 4:57 PM, Andreas Muehlemann wrote: > Hi Stephan > > Thank you very much, the encodeurl and ?body= are the trick! > For posterity, please reply to the mailing list as well, especially when it is a success message ;) Regards, Stephan. > > On 02/05/2012 04:46 PM, Stephan Bosch wrote: >> On 2/5/2012 4:00 PM, Andreas Muehlemann wrote: >>> Hi All >>> >>> I'm using dovecot 2.0.16 with the pigeonhole plugin 0.25. >>> >>> I'm trying to use the notifiy mechanism from sieve to send >>> notifications when a mail arrives in the mailbox. The message is >>> checked to be a 8bit message, otherwise it is replaced by the >>> default message "Notification of new message." How can I create a >>> 8bit message body within the sieve script that is accepted by the >>> notification process? >>> >>> e.g. >>> notify >>> :message "Subject: ${subject}" >>> "mailto:email@domain.com"; >>> >>> Do I have to put the message body into the :message string? Or how >>> can I define a custom message body that is accepted by notify? >> >> If I understand you correctly, the following should be the solution >> for your issue: >> >> <SCRIPT> >> require "enotify"; >> require "variables"; >> require "encoded-character"; >> >> # Percent-encode the UTF-8 message >> # (I'm using encoded-character here, but you can use UTF8 directly of >> course) >> set :encodeurl "message" "In ${unicode:d6}sterreich m${unicode:e4}ht >> Herr M${unicode:fc}ller seinen Rasen ${unicode:fc}brigens auch >> ${unicode:fc}ber dem Durchschnitt schnell."; >> >> # Send the notification >> notify :message "Herr M${unicode:fc}ller m${unicode:e4}ht seinen >> Rasen" "mailto:user@example.com?body=${message}"; >> </SCRIPT> >> >> This sends the following message: >> >> <MESSAGE> >> X-Sieve: Pigeonhole Sieve 0.3.0 >> Message-ID: <dovecot-sieve-1328456217-863910-0(a)host.example.com> >> Date: Sun, 05 Feb 2012 16:36:57 +0100 >> Subject: Herr =?utf-8?q?M=C3=BCller_m=C3=A4ht?= seinen Rasen >> From: Postmaster <postmaster(a)example.com> >> To: user(a)example.com >> Auto-Submitted: auto-notified; >> owner-email="234234234234(a)ext2.domain.tld" >> Precedence: bulk >> X-Priority: 3 (Normal) >> Importance: Normal >> MIME-Version: 1.0 >> Content-Type: text/plain; charset=UTF-8 >> Content-Transfer-Encoding: 8bit >> >> In Österreich mäht Herr Müller seinen Rasen übrigens auch über dem >> Durchschnitt schnell. >> </MESSAGE> >> >> Regards, >> >> Stephan >

1 0

[Dovecot] Sieve notify messages
by Andreas Muehlemann 05 Feb '12

05 Feb '12

Hi All I'm using dovecot 2.0.16 with the pigeonhole plugin 0.25. I'm trying to use the notifiy mechanism from sieve to send notifications when a mail arrives in the mailbox. The message is checked to be a 8bit message, otherwise it is replaced by the default message "Notification of new message." How can I create a 8bit message body within the sieve script that is accepted by the notification process? e.g. notify :message "Subject: ${subject}" "mailto:email@domain.com"; Do I have to put the message body into the :message string? Or how can I define a custom message body that is accepted by notify? Best regards Andreas

2 1

[Dovecot] What does this /var/log/maillog message means?
by Andre Lopes 04 Feb '12

04 Feb '12

Hi, I'm, trying to configure Devcot(2.0.9). Here is my dovecot.conf: [code] protocols = imap pop3 lmtp log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/vmail/%d/%n/Maildir ssl_cert = /etc/pki/dovecot/certs/dovecot.pem ssl_key = /etc/pki/dovecot/private/dovecot.pem namespace { type = 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)mailserver.com } service auth { user = root } passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } userdb { driver = static args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } [/code] I can start the service correctly: [code] [root@mailserver dovecot]# service dovecot start Starting Dovecot Imap: [ OK ] [/code] But when I go to "/var/log/maillog" I get this: [code] Feb 3 14:37:59 www dovecot: master: Warning: Killed with signal 15 (by pid=16757 uid=0 code=kill) Feb 3 14:38:03 www dovecot: master: Dovecot v2.0.9 starting up (core dumps disabled) [/code] What does this mean? I'm doing something that is not correct? Best Regards,

2 1

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

03 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 03 Feb '12

03 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