- dovecot - dovecot.org

[Dovecot] v2.0.19 released
by Timo Sirainen 15 Mar '12

15 Mar '12

http://dovecot.org/releases/2.0/dovecot-2.0.19.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.19.tar.gz.sig Hopefully one of the last v2.0.x releases. - IMAP: ENABLE CONDSTORE/QRESYNC + STATUS for a mailbox might not have seen latest external changes to it, like new mails. - imap_id_* settings were ignored before login. - doveadm altmove did too much work sometimes, retrying moves it had already done. - mbox: Fixed accessing Dovecot v1.x mbox index files without errors.

1 0

[Dovecot] sieve.before script is taking preceedence over user defined rules
by Alexis Lelion 15 Mar '12

15 Mar '12

Hello, In my current setup, I have a spam filter upstream that adds a specific header - X-Spam-Level on every incoming mail. Based on this level, the mail will be moved to the user spam folder using sieve by doing "fileinto :create 'spam';" Unfortunately, some legitimate email may end up in this spam folder, so I have kind of a whitelist that performs an explicit keep over specific trusted domains. So, my complete spam filtering rule is : if address :domain :contains "From" ["mycompany.tld", "trusted.tld" ]{ keep; elseif header :contains "X-Spam-Level" ["0","1","2"] { fileinto :create "__spam__"; } This rule is stored in "/var/lib/dovecot/sieve/before.sieve", which is my "sieve_before" file as defined in /etc/dovecot/conf.d/90-sieve.conf This works as expected except that it doesn't take into account users filtering for domains that were matched for the explicit keep. For example, I have the following rule : if address :domain "From" "trusted.tld" { fileinto "trusted" } But mail coming from that domain are still delivered in my mailbox. Is there something I'm missing here? I guess yes, otherwise it would work as I want ^_^ Any help/comment is appreciated Thanks! Alexis

2 4

Re: [Dovecot] doveadm -A stops processing at first uid<first_valid_uid
by Joseph Tam 15 Mar '12

15 Mar '12

On Sun, 4 Mar 2012, Timo Sirainen writes: > > I would like to run various doveadm commands that involves all (mail) users like > > > > doveadm expunge -A mailbox Trash savedbefore 30d > > > > but any doveadm command that uses "-A" to iterate through all users will > > stop processing at the first account with UID<first_valid_uid. > > What userdb are you using? userdb passwd should already skip users that > aren't in the valid range. And what Dovecot version are you using? passwd-file under dovecot 2.0.16. > And one more thing: Does it really even stop there? Looking at the code > it's supposed to log an error and continue to next user. Note that it says > "Failed to iterate through SOME users". The wording did not escape my notice, which is why I suspect it's not doing what it was designed to do. This is my test: # Command doveadm mailbox list -A # Start of password file sysdaemon:*:500:500:System daemon:/:/dev/null ... and the rest ... # dovecot.conf ... first_valid_uid = 10000 first_valid_gid = 10000 ... In this situation, doveadm will exit immediately with an UID error message. If I change the UID>10000, it will produce the analogous GID error message. If I satify both UID and GID constraints, it will fail on the next daemon entry. If I move the sysdaemon entry all the way to the bottom of the pasword file, I get user1 saved-messages user1 sent-mail user1 postponed-msgs user1 temp user1 temp/temp user1 INBOX user2 sent-mail user2 101 user2 345 user2 ckf ... all user's mailbox with UID>10000, then ... doveadm(sysdaemon): Error: user sysdaemon: Couldn't drop privileges: Mail access for users with UID 500 not permitted (see first_valid_uid in config file, uid from userdb lookup). doveadm(sysdaemon): Error: User init failed doveadm: Error: Failed to iterate through some users > Oh, it says about first_valid_gid. Is sysdaemon's UID within valid range? Sorry for this error mismatch -- I cut&pasted the wrong test output; however, the problem I witnessed applies to both UID and GID (if either constraint is not met, user iteration terminates). > I also added this today: http://hg.dovecot.org/dovecot-2.1/rev/85a8d582d37f It looks like I'll be upgrading. Oh, I just spotted this in the ChangeLog -- maybe you are undoing this? (2010-10-21) * src/auth/auth-settings.c, src/auth/auth-settings.h, src/auth/userdb- passwd.c: auth: userdb passwd iteration now lists only users within first_valid_uid..last_valid_uid range. [745ef289b0ea] Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] Shared folder prefix listed multiple times with dovecot 2.1.1
by Markus Petri 15 Mar '12

15 Mar '12

Hi, after upgrading from 2.0.18 to 2.1.1 I noticed that I could not use shared folders with mutt anymore. 2.1 lists the shared namespace prefix once per user sharing an folder in LIST "" "%". I also noticed, that with 2.1 the user folder (Shared/<username>) is no longer tagged as \NoSelect. Is this the intended behaviour and mutt simply cannot cope with it or is it a dovecot problem? Here an example with three users sharing a folder to the logged in user with Dovecot 2.1.1: 2 LIST "" "*" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\HasChildren) "/" "Shared/test" * LIST (\HasNoChildren) "/" "Shared/test/Share" * LIST (\HasChildren) "/" "Shared/test2" * LIST (\HasNoChildren) "/" "Shared/test2/Share2" * LIST (\HasChildren) "/" "Shared/test3" * LIST (\HasNoChildren) "/" "Shared/test3/Share3" 2 OK List completed. 2 LIST "" "%" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\Noselect \HasChildren) "/" "Shared" * LIST (\Noselect \HasChildren) "/" "Shared" * LIST (\Noselect \HasChildren) "/" "Shared" 2 OK List completed. The same three users and config with Dovecot 2.0.18: 2 LIST "" "*" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\Noselect \HasChildren) "/" "Shared/test" * LIST (\Noselect \HasChildren) "/" "Shared/test2" * LIST (\Noselect \HasChildren) "/" "Shared/test3" * LIST (\HasNoChildren) "/" "Shared/test/Share" * LIST (\HasNoChildren) "/" "Shared/test2/Share2" * LIST (\HasNoChildren) "/" "Shared/test3/Share3" 2 OK List completed. 2 LIST "" "%" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\Noselect \HasChildren) "/" "Shared" 2 OK List completed. Markus # 2.1.1: /opt/dovecot-2.1/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-1-amd64 x86_64 Debian wheezy/sid auth_mechanisms = plain login disable_plaintext_auth = no listen = 192.168.56.11 mail_location = maildir:~/Maildir mail_plugins = acl managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace { inbox = yes location = prefix = separator = / subscriptions = yes type = private } namespace { inbox = no list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/index/shared/%%u prefix = Shared/%%u/ separator = / subscriptions = no type = shared } passdb { args = /opt/dovecot-2.1/etc/dovecot/passwd driver = passwd-file } plugin { acl = vfile acl_anyone = allow acl_shared_dict = file:/var/lib/vdovecot/shared-mailboxes.db } protocols = imap service auth { unix_listener auth-userdb { mode = 0600 user = vdovecot } } ssl = no userdb { args = /opt/dovecot-2.1/etc/dovecot/passwd driver = passwd-file } verbose_proctitle = yes protocol imap { mail_plugins = acl imap_acl }

2 3

Re: [Dovecot] Dovecot 2.1 with custom OpenSSL fails to build
by Andreas M. Kirchwitz 15 Mar '12

15 Mar '12

Timo Sirainen <tss(a)iki.fi> wrote: >> There seems to be a new dependency in some modules (eg, lib-storage, >> libdovecot-lda, libdovecot-ssl) on OpenSSL. In Dovecot 2.0, those >> modules didn't require OpenSSL, but 2.1 does. >> >> For the linking process the path to the OpenSSL library isn't >> specified properly (SSL_LIBS). Dovecot fails to build if OpenSSL >> is in a non-standard path. (Haven't checked if SSL_CFLAGS isn't >> properly used as well.) > > Maybe http://hg.dovecot.org/dovecot-2.1/rev/c07415305d9e fixes > everything? That's the way to go. Makes things better, but I've found three more dependencies. This patch is against the daily snapshot 20120228. (Sorry for the changes to Makefile.in which you won't need. But this way I don't have to rebuild Makefile.in from Makefile.am when compiling. ;-) diff -ur dovecot-20120228.original/src/auth/Makefile.am dovecot-20120228/src/auth/Makefile.am --- dovecot-20120228.original/src/auth/Makefile.am 2012-02-26 04:00:02.000000000 +0100 +++ dovecot-20120228/src/auth/Makefile.am 2012-02-29 01:38:41.000000000 +0100 @@ -167,7 +167,7 @@ libauthdb_imap_la_LIBADD = \ ../lib-imap-client/libimap_client.la \ ../lib-ssl-iostream/libssl_iostream.la \ - $(LIBDOVECOT) + $(LIBDOVECOT) $(SSL_LIBS) libauthdb_imap_la_CPPFLAGS = \ $(AM_CPPFLAGS) \ -I$(top_srcdir)/src/lib-imap \ diff -ur dovecot-20120228.original/src/auth/Makefile.in dovecot-20120228/src/auth/Makefile.in --- dovecot-20120228.original/src/auth/Makefile.in 2012-02-28 04:00:12.000000000 +0100 +++ dovecot-20120228/src/auth/Makefile.in 2012-02-29 01:38:44.000000000 +0100 @@ -499,7 +499,7 @@ libauthdb_imap_la_LIBADD = \ ../lib-imap-client/libimap_client.la \ ../lib-ssl-iostream/libssl_iostream.la \ - $(LIBDOVECOT) + $(LIBDOVECOT) $(SSL_LIBS) libauthdb_imap_la_CPPFLAGS = \ $(AM_CPPFLAGS) \ diff -ur dovecot-20120228.original/src/lib-storage/Makefile.am dovecot-20120228/src/lib-storage/Makefile.am --- dovecot-20120228.original/src/lib-storage/Makefile.am 2012-02-10 04:00:02.000000000 +0100 +++ dovecot-20120228/src/lib-storage/Makefile.am 2012-02-29 01:38:21.000000000 +0100 @@ -85,7 +85,7 @@ pkglib_LTLIBRARIES = libdovecot-storage.la libdovecot_storage_la_SOURCES = -libdovecot_storage_la_LIBADD = $(shlibs) $(MODULE_LIBS) +libdovecot_storage_la_LIBADD = $(shlibs) $(MODULE_LIBS) $(SSL_LIBS) libdovecot_storage_la_DEPENDENCIES = $(shlibs) libdovecot_storage_la_LDFLAGS = -export-dynamic diff -ur dovecot-20120228.original/src/lib-storage/Makefile.in dovecot-20120228/src/lib-storage/Makefile.in --- dovecot-20120228.original/src/lib-storage/Makefile.in 2012-02-28 04:00:15.000000000 +0100 +++ dovecot-20120228/src/lib-storage/Makefile.in 2012-02-29 01:38:21.000000000 +0100 @@ -397,7 +397,7 @@ pkglib_LTLIBRARIES = libdovecot-storage.la libdovecot_storage_la_SOURCES = -libdovecot_storage_la_LIBADD = $(shlibs) $(MODULE_LIBS) +libdovecot_storage_la_LIBADD = $(shlibs) $(MODULE_LIBS) $(SSL_LIBS) libdovecot_storage_la_DEPENDENCIES = $(shlibs) libdovecot_storage_la_LDFLAGS = -export-dynamic test_programs = \ diff -ur dovecot-20120228.original/src/login-common/Makefile.am dovecot-20120228/src/login-common/Makefile.am --- dovecot-20120228.original/src/login-common/Makefile.am 2011-11-09 04:00:01.000000000 +0100 +++ dovecot-20120228/src/login-common/Makefile.am 2012-02-29 01:38:21.000000000 +0100 @@ -40,6 +40,6 @@ pkglib_LTLIBRARIES = libdovecot-login.la libdovecot_login_la_SOURCES = -libdovecot_login_la_LIBADD = liblogin.la ../lib-ssl-iostream/libssl_iostream.la ../lib-dovecot/libdovecot.la +libdovecot_login_la_LIBADD = liblogin.la ../lib-ssl-iostream/libssl_iostream.la ../lib-dovecot/libdovecot.la $(SSL_LIBS) libdovecot_login_la_DEPENDENCIES = liblogin.la libdovecot_login_la_LDFLAGS = -export-dynamic diff -ur dovecot-20120228.original/src/login-common/Makefile.in dovecot-20120228/src/login-common/Makefile.in --- dovecot-20120228.original/src/login-common/Makefile.in 2012-02-28 04:00:18.000000000 +0100 +++ dovecot-20120228/src/login-common/Makefile.in 2012-02-29 01:38:21.000000000 +0100 @@ -320,7 +320,7 @@ pkginc_lib_HEADERS = $(headers) pkglib_LTLIBRARIES = libdovecot-login.la libdovecot_login_la_SOURCES = -libdovecot_login_la_LIBADD = liblogin.la ../lib-ssl-iostream/libssl_iostream.la ../lib-dovecot/libdovecot.la +libdovecot_login_la_LIBADD = liblogin.la ../lib-ssl-iostream/libssl_iostream.la ../lib-dovecot/libdovecot.la $(SSL_LIBS) libdovecot_login_la_DEPENDENCIES = liblogin.la libdovecot_login_la_LDFLAGS = -export-dynamic all: all-am

2 3

[Dovecot] .mailboxlist -> .subscriptions
by Steve Campbell 15 Mar '12

15 Mar '12

I've mostly finished a conversion from an old Centos 3 UW-Imap server to a new Centos 6 dovecot server. I did not copy the old ~/.mailboxlist file to ~/mail/.subscriptions file, but notice some users have the latter file now. These are all mbox folders on the old and new server. I'm getting ready to do the same to another old/new pair of servers and I'm wondering if there is an advantage of doing the copy. I'm assuming the .subscription files are created when they access their account through our webmail application, but I'm not sure if it was automatic or due to a "subscribe" action done manually. There are 49 accounts with a .mailboxlist file and only 4 with the new .subscriptions file. So either our webmail application isn't being used a lot or there's a problem with it due to the missing .subscriptions file, but the phone usually rings pretty quickly when problems arise. One last question, please. Over the years, some imap accounts had their folders directly in their home directory and the contents of the .mailboxlist file would have an entry with just the name of the folder in it (Trash, eg), and most had the folders in their ~/mail folder with an entry like "mail/Trash". Our webmail app, Horde/Imp, always seemed to take care of this. If I create the .subscription file for the users during the move to the new server, should I move the folders to the mail directory and amend their .subscriptions file to reflect that change on these odd ball accounts, and will that affect how their client is seeing these? The first server conversion was a bear due to my lack of dovecot knowledge. I've since learned a little more, and mostly found out that dovecot is a more complex application than the old imap application. There's so much more that can be done with dovecot, whereas the old imap server was mostly just load-and-go. Seems like no matter how much I read, the more I discovered I didn't know. Anyway, thanks for all the past help and any opinions anyone might decide to offer on this post. steve campbell

3 6

[Dovecot] 2.1: timeout waiting for lock?
by Ralf Hildebrandt 15 Mar '12

15 Mar '12

Mar 15 09:46:11 postamt dovecot: pop3(username): Error: Couldn't open INBOX: Timeout while waiting for lock Mar 15 09:46:11 postamt dovecot: pop3(username): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 Mar 15 09:47:26 postamt dovecot: pop3(username): Error: Couldn't open INBOX: Timeout while waiting for lock Mar 15 09:47:26 postamt dovecot: pop3(username): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 Mar 15 09:51:01 postamt dovecot: pop3(username): Error: Couldn't open INBOX: Timeout while waiting for lock Mar 15 09:51:01 postamt dovecot: pop3(username): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 during that time, I wasn't able to access the mailbox using imap. I then issued doveadm kick username and all over sudden the mailbox was accessible (via IMAP) # doveadm kick username kicked connections from the following users: username # /usr/local/scripts/find_abnormal_imap Mar 15 11:38:48 postamt dovecot: imap: Warning: Killed with signal 15 (by pid=24545 uid=0 code=kill) -- 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 4

Re: [Dovecot] .mailboxlist -> .subscriptions
by Joseph Tam 15 Mar '12

15 Mar '12

Steve Campbell <campbell(a)cnpapers.com> writes: > Their imap folders, the ones that they create using an imap client or > webmail, are either in ~ or ~/mail. Their original .mailboxlist is > always in ~. Based on that, I should probably copy any imap folders not > in ~/mail to that folder, duplicate ~/.mailboxlist to the file > ~/mail/.subscriptions, and amend any .subscriptions file contents to > just have the name of the folders (without any "mail/folder" reference > in it). > > My example would then be as follows > > /home/steve = folder > /home/steve/Drafts = original folder > /home/steve/AnyFolder = original folder > /home/steve/.mailboxlist = original file > /home/steve/mail = folder (either original or created) > /home/steve/mail/.subscriptions = copied contents of .mailboxlist > file > /home/steve/mail/Drafts = copied folder of original > /home/steve/mail/AnyFolder = copied folder of original > > Contents of original .mailboxlist and new .subscriptions: > > Drafts > AnyFolder > > If the imap folders were in ~/mail, then the original .mailboxlist would > have been > > mail/Drafts > mail/AnyFolder > > but after the corrections to the .subscriptions file, they would be as > above (without reference to the mail folder). > > Is this correct? That depends -- are you aliasing namespaces so that prefix={"", "mail/", etc.} all map to a user's ~/mail folder? You may be creating a confusing situation where a client with a null IMAP prefix has 2 copies of a mailbox. Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] firefox dovecot-sieve
by paul 15 Mar '12

15 Mar '12

Send this to dovecot(a)dovecot.org, not dovecot-owner(a)dovecot.org On 14.3.2012, at 4.45, paul wrote: > HI. I have just started to play with sieve and everything seems ok when > logging on using telnet localhost 4190 and an encoded username/password. > If I try to connect with firefox at localhost:4190 I get > "IMPLEMENTATION" "Dovecot Pigeonhole" > "SIEVE" "fileinto reject envelope encoded-character vacation subaddress > comparator-i;ascii-numeric relational regex imap4flags copy include > variables body enotify environment mailbox date ihave" > "NOTIFY" "mailto" > "SASL" "PLAIN LOGIN" > "STARTTLS" > "VERSION" "1.0" > OK "Dovecot ready." > NO "Error in MANAGESIEVE command received by server." > NO "Error in MANAGESIEVE command received by server." > NO "Invalid characters in atom" > BYE "Too many invalid MANAGESIEVE commands." > my dovecot -n shows > # 2.0.18: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.42.9-1.fc15.i686.PAE i686 Fedora release 15 (Lovelock) > auth_mechanisms = plain login > disable_plaintext_auth = no > mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u > mail_privileged_group = mail > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope > encoded-character vacation subaddress comparator-i;ascii-numeric > relational regex imap4flags copy include variables body enotify > environment mailbox date ihave > mbox_write_locks = fcntl > passdb { > driver = pam > } > plugin { > sieve = ~/.dovecot.sieve > sieve_dir = ~/sieve > } > protocols = imap pop3 lmtp sieve > service managesieve-login { > inet_listener sieve { > port = 4190 > } > } > ssl_cert = </etc/pki/dovecot/certs/dovecot.pem > ssl_key = </etc/pki/dovecot/private/dovecot.pem > userdb { > driver = passwd > } > Have I missed something obvious or does Firefox clash with Managesieve? > Thanks. Paul >

2 1

[Dovecot] Login Failed
by Aydın Demirel 15 Mar '12

15 Mar '12

Hi; We are using scripts for login successes. Is there a feature for login failed status or can it be developed? Regards -- *Aydın Demirel Endersys Ltd. Sistem Destek Mühendisi/ System Support Engineer* * *<<Endersys is the first Advanced Business Partner of Red Hat in Turkey! http://www.europe.redhat.com/partners/endersys/>> Phone : +90 216 470 9423 | GSM : +90 530 401 8203 Fax : +90 216 470 9508 | Web : http://www.endersys.com <http://www.endersys.com/> Blog : http://blog.endersys.com <http://blog.endersys.com/> Twitter : http://www.twitter.com/endersys LPI : The #1 Linux Certification for IT Professionals LPI (Linux Professional Institute) Turkey http://www.lpi-turkey.com <http://www.lpi-turkey.com/>

2 1