June 2016 - dovecot - dovecot.org

v2.2.25 release candidate released
by Timo Sirainen 01 Jul '16

01 Jul '16

http://dovecot.org/releases/2.2/rc/dovecot-2.2.25.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.25.rc1.tar.gz.sig Quite a lot of changes. Please test out before the final v2.2.25 release, which I'm planning for tomorrow. Especially the new lib-dcrypt might have compiling problems with some OpenSSL versions. * lmtp: Start tracking lmtp_user_concurrency_limit and reject already at RCPT TO stage. This avoids MTA unnecessarily completing DATA only to get an error. * doveadm: Previously only mail settings were read from protocol doveadm { .. } section. Now all settings are. + quota: Added quota_over_flag_lazy_check setting. It avoids checking quota_over_flag always at startup. Instead it's checked only when quota is being read for some other purpose. + auth: Added a new auth policy service: http://wiki2.dovecot.org/Authentication/Policy + auth: Added PBKDF2 password scheme + auth: Added %{auth_user}, %{auth_username} and %{auth_domain} + auth: Added ":remove" suffix to extra field names to remove them. + auth: Added "delay_until=<timestamp>[+<max random secs>]" passdb extra field. The auth will wait until <timestamp> and optionally some randomness and then return success. + dict proxy: Added idle_msecs=<n> parameter. Support async operations. + Performance improvements for handling large mailboxes. + Added lib-dcrypt API for providing cryptographic functions. + Added "doveadm mailbox update" command + imap commands' output now includes timing spent on the "syncing" stage if it's larger than 0. + cassandra: Added metrics=<path> to connect setting to output internal statistics in JSON format every second to <path>. + doveadm mailbox delete: Added -e parameter to delete only empty mailboxes. Added --unsafe option to quickly delete a mailbox, bypassing lazy_expunge and quota plugins. + doveadm user & auth cache flush are now available via doveadm-server. + doveadm service stop <services> will stop specified services while leaving the rest of Dovecot running. + quota optimization: Avoid reading mail sizes for backends which don't need them (count, fs, dirsize) + Added mailbox { autoexpunge_max_mails=<n> } setting. + Added welcome plugin: http://wiki2.dovecot.org/Plugins/Welcome + fts: Added fts_autoindex_exclude setting. - v2.2.24's MIME parser was assert-crashing on mails having truncated MIME headers. - auth: With multiple userdbs the final success/failure result wasn't always correct. The last userdb's result was always used. - doveadm backup was sometimes deleting entire mailboxes unnecessarily. - doveadm: Command -parameters weren't being sent to doveadm-server. - If dovecot.index read failed e.g. because mmap() reached VSZ limit, an empty index could have been opened instead, corrupting the mailbox state. - imapc: Fixed EXPUNGE handling when imapc_features didn't have modseq. - lazy-expunge: Fixed a crash when copying failed. Various other fixes. - fts-lucene: Fixed crash on index rescan. - auth_stats=yes produced broken output - dict-ldap: Various fixes - dict-sql: NULL values crashed. Now they're treated as "not found".

6 9

Released Pigeonhole v0.4.15.rc1 for Dovecot v2.2.25.rc1.
by Stephan Bosch 01 Jul '16

01 Jul '16

Hello Dovecot users, This upcoming release is all about bug fixes, of which only one is really important. It affects the new imapsieve plugin. Changelog v0.4.15: - imapsieve plugin: For any mail transaction, the mailbox was opened a second time, even if no mailbox rule matched. This was unintentional, useless and caused problems when the imapsieve plugin was used with other plugins like acl. - extprograms plugin: Significantly improved error handling. No stream errors were logged. - Several small fixes based on static analysis. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.15… http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.15… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

quota-status service
by Michael Fox 30 Jun '16

30 Jun '16

I'm trying to understand the quota-status service, but I can't find complete documentation. The quota-status service is mentioned here: http://wiki.dovecot.org/Quota And an example configuration is shown: service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 # You can choose any port you want } client_limit = 1 } But I can't find any information on quota-status. "man quota-status" returns nothing. I am unable to find a "quota-status" file on my machine. Where is the executable located? What does the "-p postfix" option do? Are there any other command line options? The above wiki page shows three quota_status_* options in use: quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = "552 5.2.2 Mailbox is full" Where are their meanings documented? What are the allowed values? Are there other quota_status_* options? Thanks in advance. Thanks, Michael

1 0

quota_full_tempfail
by Felipe Gasper 30 Jun '16

30 Jun '16

Hi all, What specifically does this flag do? Does it affect what happens: -------------- - when the drive is full? - when the system user’s disk quota is full? - when the mailbox’s quota is full? -------------- Also, does it work with both LDA and LMTP? I don’t see much on this option in the docs. Thank you! -Felipe Gasper Houston, TX

1 0

Re: Error when searching in mailfolders
by Christoph Pleger 30 Jun '16

30 Jun '16

Hello, >>> Lucene library is throwing an error, which crashes Dovecot. Maybe Dovecot >>> should catch the error, but it would still be broken. Try deleting the lucene indexes and rebuilding them? >> Deleting the indexes helped, but after they had been rebuilt, the error occurred again. > Could you enable core dumps and run bt full in gdb? I attached the result. Regards Christoph

2 2

Remove my email id from mailing list
by Mayuri AgarwAl 30 Jun '16

30 Jun '16

Sent from my iPhone

2 1

Dictionary quota with Flat file database
by Sam 30 Jun '16

30 Jun '16

Hello, I want specific quotas for certain users and I looking for doing that with dictionary quota backend and Flat file. Because I am using "active directory" with PAM for authenticate, I can't get per-user quota limits with set/override them by returning "quota_rule" extra field from userdb. I started reading http://wiki1.dovecot.org/Quota/Dict, saw some good stuff... The problem is that I don't understand how to set the limit in the users files. If I open one created file I only see the current number of messages and the actual size. Not the quota limits... vi /home/vmail/john.doe/Maildir/dovecot-quota : priv/quota/messages 13 priv/quota/storage 600201 Here is /etc/dovecot/conf.d/90-quota.conf file details : plugin { # I think I have to set the default limits here quota_rule = *:storage=10G:messages=10000 } ... plugin { quota = dict:user::file:%h/Maildir/dovecot-quota # same result with : # quota = dict:User::file:%h/Maildir/dovecot-quota } my server : CentOS Linux release 7.2.1511 dovecot : dovecot-2.2.10-5.el7.x86_64 Thanks for helping. Sam

2 1

Unread Mail flag being reset frequently with dovecot -git master-2.2
by Reuben Farrelly 30 Jun '16

30 Jun '16

Hi again, I'm experiencing problems with the Dovecot git master-2.2 branch, in which mails that have been previously read are randomly appearing as unread. This happens slowly and affects more and more emails the more changes that occur to a mailbox. I am using Maildir format and on Gentoo Linux x86_64 on local disks. Usually only a few at a time change their status - and it seems to be random which ones lose their read status. Typically though they are the most recent emails that have been delivered in the past few months (I haven't yet seen this occur with any really old emails). This problem is MUA independent, it can be observed with Thunderbird as well as Roundcube. If I go in and mark all mails as read then they will show as read for a short while until they too slowly start become 'unread' again. Currently I'm running git rev from https://github.com/dovecot/core/commits/master-2.2 : f292589f4b85e02d97d974dfe34324c6c0bb9d9f (I can't run anything newer due to an SSL symbol error which I reported earlier). This rev: b1254dfe442639236f881afae85e0739520ab409 Is known to be good, so the problem started happening somewhere between these two. (I know there are a lot of in-between revisions, but bisecting that could take days of time). Dovecot config is up at: http://www.reub.net/files/dovecot/thunderstorm-dovecot.conf Rawlog debug files are at http://www.reub.net/files/dovecot/rawlogs/ Hopefully someone else may have seen this happen before. Are there any other debugs I can gather which will help get to the bottom of this? Reuben

2 2

Re[2]: External mail attachments storage cleanup
by Николай Мананков 30 Jun '16

30 Jun '16

Yes "dovecot purge" is certainly my mistake in the script but it really works completely analogous "doveadm purge" probably why I did not notice the difference before :) It looks like it just launches the doveadm in this case. Adding slashes after asterisks unfortunately they also adds to the variable and the script gives an error like "doveadm(user/(a)example.org/): Error: User doesn't exist" Thanks for the idea , I think it will be now more correctly : === #!/bin/sh cd /backup/MailRoot/dovecot/domains || exit 1 for i in * do if [ -d $i ]; then cd $i for j in * do if [ -d $j ]; then dovecot purge -u $j@$i fi done cd .. fi done === >Четверг, 30 июня 2016, 13:53 +03:00 от Alexander Moisseev <moiseev(a)mezonplus.ru>: > >On 30.06.16 12:51, Николай Мананков wrote: >> -----screenshot begin----- >> >> mail:/etc/cron.daily # cat ./dovepurge.sh >> #!/bin/sh >> >> cd /MailRoot/dovecot/domains >> >> for i in * >> do >> cd $i >> for j in *; do dovecot purge -u $j@$i; done >> cd .. >> done >> >> -----screenshot end ----- >> >It might be worth to add slashes after asterisks to process only directories. >Does "dovecot purge" actually work? > >-----screenshot begin----- > >#!/bin/sh > >cd /MailRoot/dovecot/domains || exit 1 > >for i in */ > do > cd $i > for j in */; do doveadm purge -u $j@$i; done > cd .. >done > >-----screenshot end ----- > >> It is strange that the daemon does not do this automatically, and even setting up autoexpunge option does not help. Also IMHO certainly evident mistake in the documentation about the wildcards processing by purge command.. > >I don't know how the developers themselves use Dovecot, but it lacks some obvious features like automatic purge or SIS cleanup on mailbox deletion. >

1 0

Re[2]: External mail attachments storage cleanup
by Николай Мананков 30 Jun '16

30 Jun '16

Yes "dovecot purge" is certainly my mistake in the script but it really works completely analogous "doveadm purge" probably why I did not notice the difference before :) It looks like it just launches the doveadm in this case. Adding slashes after asterisks unfortunately they also adds to the variable and the script gives an error like "doveadm(user/(a)example.org/): Error: User doesn't exist" Thanks for the idea , I think it will be now more correctly : === #!/bin/sh cd /backup/MailRoot/dovecot/domains || exit 1 for i in * do if [ -d $i ]; then cd $i for j in * do if [ -d $j ]; then dovecot purge -u $j@$i fi done cd .. fi done === >Четверг, 30 июня 2016, 13:53 +03:00 от Alexander Moisseev <moiseev(a)mezonplus.ru>: > >On 30.06.16 12:51, Николай Мананков wrote: >> -----screenshot begin----- >> >> mail:/etc/cron.daily # cat ./dovepurge.sh >> #!/bin/sh >> >> cd /MailRoot/dovecot/domains >> >> for i in * >> do >> cd $i >> for j in *; do dovecot purge -u $j@$i; done >> cd .. >> done >> >> -----screenshot end ----- >> >It might be worth to add slashes after asterisks to process only directories. >Does "dovecot purge" actually work? > >-----screenshot begin----- > >#!/bin/sh > >cd /MailRoot/dovecot/domains || exit 1 > >for i in */ > do > cd $i > for j in */; do doveadm purge -u $j@$i; done > cd .. >done > >-----screenshot end ----- > >> It is strange that the daemon does not do this automatically, and even setting up autoexpunge option does not help. Also IMHO certainly evident mistake in the documentation about the wildcards processing by purge command.. > >I don't know how the developers themselves use Dovecot, but it lacks some obvious features like automatic purge or SIS cleanup on mailbox deletion. >

1 0