Dovecot v2.2.0 released

Arieh

Verified User
Joined
May 27, 2008
Messages
1,205
Location
The Netherlands
v2.2.0 is now the newest stable.
Everything now seems to be stable and working in v2.2, so I can finally
move onto developing great new interesting features for v2.3. :)
[...]
* When creating home directories, the permissions are copied from the
parent directory if it has setgid-bit set. For full details, see
http://wiki2.dovecot.org/SharedMailboxes/Permissions
* "doveadm auth" command was renamed to "doveadm auth test"
* IMAP: ID command now advertises server name as Dovecot by default.
It was already trivial to guess this from command replies.
* dovecot.index.cache files can be safely accessed only by v2.1.11+.
Older versions may think they're corrupted and delete them.
* LDA/LMTP: If saving a mail brings user from under quota to over
quota, allow it based on quota_grace setting (default: 10%
above quota limit).
* pop3_lock_session=yes now uses a POP3-only dovecot-pop3-session.lock
file instead of actually locking the mailbox (and causing
IMAP/LDA/LMTP to wait for the POP3 session to close).
* mail_shared_explicit_inbox setting's default switched to "no".
* ssl_client_ca_dir setting replaced imapc_ssl_ca_dir and
pop3c_ssl_ca_dir settings.

+ Implemented IMAP MOVE and BINARY extensions
+ Implemented IMAP CATENATE, URLAUTH and URLAUTH=BINARY extensions
(by Stephan Bosch).
+ Implemented IMAP NOTIFY extension. Requires mailbox_list_index=yes
to be enabled.
+ Redesigned and rewritten dsync. The new design makes the syncing
faster, more reliable and more featureful. The new dsync protocol
isn't backwards compatible with old dsync versions (but is designed
to be forwards compatible with future versions).
+ All mailbox formats now support per-user message flags for shared
mailboxes by using a private index. It can be enabled by adding
:INDEXPVT=<path> to mail location. This should be used instead of
:INDEX also for Maildir/mbox to improve performance.
+ Improved mailbox list indexes. They should be usable now, although
still disabled by default.
+ Added LAYOUT=index. The mailbox directories are created using their
GUIDs in the filesystem, while the actual GUID <-> name mapping
exists only in the index.
+ LMTP proxy: Implemented XCLIENT extension for passing remote IP
address through proxy.
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
8,960
Hello,

In case anyone is wondering why 2.2.0 is not yet set in the versions.txt on the files servers, our initial test showed that the limit counting had changed very slightly..
It still worked ok, but a warning about the client_limit was thrown, where, in the event of max clients, there wouldn't be enough clients, and 3 too many authenticators.

I've since updated the default dovecot.conf:
http://files.directadmin.com/services/custombuild/dovecot.conf.2.0

to use:
Code:
[COLOR=#000000]default_client_limit = 1003[/COLOR]
which overrides the internal default of 1000.

I then tested this update on a different box (without the default_client_limit change) and it did not run into the error... so not sure if it was an isolated issue or not.

I believe the "count" came into play when the process_limit=800 option was added (plus 2.2.0):
Code:
service imap-login {
  process_limit = 800
so if you don't have that, then you'd be ok.

Even if you do have it, and update, you'd just see this warning:
Code:
[root@server custombuild]# /etc/init.d/dovecot restart
Shutting down dovecot:                                     [  [COLOR=#008000]OK[/COLOR]  ]
Starting dovecot: doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (1003)
Warning: service anvil { client_limit=1000 } is lower than required under max. load (1003)
                                                           [  [COLOR=#008000]OK[/COLOR]  ]
[root@server custombuild]#
which will still let dovecot run just fine... you'd just need to either added the default_client_limit = 1003 to the very top of the dovecot.conf, or just download a new one.

I'll let this information sit for a few days to see what people think.

You can manually test the update now by editing your versions.txt, and set the line:
Code:
dovecot:2.2.0:
followed by a
Code:
./build dovecot
If reports are all ok, even with the warning, then I'll consider updating the versions.txt to 2.2.0, even with the warning.

With the 2.2.0 version and the warning, the worst case is there would be authentication issues after 1000 simultaneous connections.... which there would be anyway, but it may just throw strange errors, rather than a nice error.
All restarts of dovecot would throw the warning, so people would likely know to search for that error.. which would likely bring them to this thread.

John
 

James2k

Verified User
Joined
Nov 28, 2012
Messages
38
Make sense, I added default_client_limit to my dovecot.conf and compiled 2.2.0, working fine on CentOS 6.4
 

wattie

Verified User
Joined
May 31, 2008
Messages
1,036
Location
Bulgaria
Updated to 2.2 on FreeBSD 9.1 and I got no errors:

root@srv:/usr/local/directadmin/custombuild # /usr/local/etc/rc.d/dovecot restart
Stopping dovecot: [ OK ]
Starting dovecot: [ OK ]

I never edited anything in the dovecot.conf.
 

bobsthename

Verified User
Joined
Sep 23, 2009
Messages
66
Location
NZ
Can this be added to CB yet?
I upgraded to 2.2.1 with no errors or other problems on debian squeeze 64bit, and I never edited anything in the dovecot.conf either.
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
8,960
Hello,

I've tested quite a bit on several different OS's and didn't run into anything significant.

I did get the odd warning about a low ulimit.. if you do get that warning, just grab a new boot script, but isn't integral to having it work:
http://files.directadmin.com/services/custombuild/dovecot.boot
http://files.directadmin.com/services/custombuild/dovecot.boot.debian
http://files.directadmin.com/services/custombuild/dovecot.boot.freebsd

The other warning I saw once, was a process limit warning with the dovecot.conf, where it said that at max load, there would be more auth workers, than actual imap workers (something along those lines)
Again, not integral to the functioning of dovecot, unless you're regularly at the max capacity of dovecot.
Either way, if you want the latest dovecot.conf, this is it:
http://files.directadmin.com/services/custombuild/dovecot.conf.2.0

If you get zero warnings when dovecot is restarted, then you're fine.
If you do, dovecot will still run without any noticeable issues, but you can fix the warnings by updating the relevant files, above.

John
 

ditto

Verified User
Joined
Apr 27, 2009
Messages
2,505
I have upgraded dovecot to 2.2.1 now, and tested some. First I did NOT change dovecot.conf and dovecot.boot, but only run ./build update and ./build dovecot - there was NO errors at all.

Then I tested by removing dovecot.conf and dovecot.boot and then run ./build dovecot so that I get the newest versions of dovecot.conf and dovecot.boot, this time I get this warning:

Code:
Restarting dovecot.
Shutting down dovecot:                                     [  OK  ]
Starting dovecot: Warning: fd limit (ulimit -n) is lower than required under max. load (1024 < 2048), because of default_client_count
                                                           [  OK  ]
[root@server custombuild]#
Then I added back the old dovecot.conf and dovecot.boot files and run ./build dovecot again, and like the first time there was NO warnings.

I am running CentOS 6.4 64 bit. So, to me it seems like the warnings is only when using DirectAdmin new versions of dovecot.conf and dovecot.boot, but when using the old versions of dovecot.conf and dovecot.boot, there is NO warnings.

By the way, everything seems to work fine. So I will use the old dovecot.conf and dovecot.boot files, wich does not produce any warnings at all.
 
Last edited:

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
8,960
Hello,

That sounds about right.

The newer dovecot.conf is tweaked to have a higher connection limit, as there were reports within the last few months of some servers having many clients, and the limit being hit, thus logins being denied.

Also, with RoundCube and SquirrelMail all connecting to 127.0.0.1, then "per-ip" connection limit on 127.0.0.1 was being hit, so the newer dovecot.conf has settings for that as well.

Glad to hear everything is working correctly.

John
 

zEitEr

Super Moderator
Joined
Apr 11, 2005
Messages
13,932
Location
GMT +7.00
As dovecot 2.2. released there might be issues with Pigeonhole with Customduild 2.0 (and manual installation with Custombuild 1.x), as there is no a stable Pigeonhole release for the Dovecot 2.2 available yet.

Pigeonhole package for Dovecot v2.2 (development)

http://pigeonhole.dovecot.org/download.html

You might want to follow these instructions to get it from dev repo:

Code:
# v2.2 code tree:
hg clone http://hg.rename-it.nl/dovecot-2.2-pigeonhole/
and build for Dovecot 2.2:

Code:
cd /usr/local/src
hg clone http://hg.rename-it.nl/dovecot-2.2-pigeonhole/
cd dovecot-2.2-pigeonhole
./autogen.sh
./configure --prefix=/usr
make && make install
 
Last edited:

interfasys

Verified User
Joined
Oct 31, 2003
Messages
2,099
Location
Switzerland

ditto

Verified User
Joined
Apr 27, 2009
Messages
2,505
@John, I just upgraded to Dovecot 2.2.2, I am running the newest versions of:

/etc/dovecot/dovecot.conf (from http://files.directadmin.com/services/custombuild/dovecot.conf.2.0 )
and
/usr/local/directadmin/custombuild/dovecot.boot (from http://files.directadmin.com/services/custombuild/dovecot.boot )

I get the same warning as before (thats not a problem):

Code:
Restarting dovecot.
Shutting down dovecot:                                     [  OK  ]
Starting dovecot: Warning: fd limit (ulimit -n) is lower than required under max. load (1024 < 2048), because of default_client_limit
                                                           [  OK  ]
[root@server custombuild]#
However I just installed DirectAdmin on a brand new server, wich runs all the same setup, and on that server I do not get the warning when restarting Dovecot. All my servers, both the old ones and the new one, is running CentOS 6.4 64bit and custombuild 2.0

Dovecot works fine on all servers, I just found it strange that on the new server I do not get the warning when restarting Dovecot, so I wonder why. I have the same new dovecot.boot and dovecot.conf file on both old and new server. Only new server do not give warning when restarting Dovecot. Just wanted to let you know about it.
 

kanary

Verified User
Joined
Jun 8, 2007
Messages
113
Location
Holland - Het westland
Since update 2.0.1 i get alot of spam in my mailbox instead of in the spambox.

It looks like it ignores the settings in spam assisan.


Hope this update will fix this problem.
 
Top