[Dovecot] v2.0.alpha2 released
http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha2.tar.gz http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha2.tar.gz.sig
Changes since alpha1:
- All debug messages are now logged to debug log (debug_log_path setting, defaults to info_log_path). Patch by Pascal Volk.
- Added support for SORT=DISPLAY IMAP extension.
- Added doveadm who command for listing currently logged in users.
- ssl_ciphers_list: Disable anonymous and export ciphers by default.
- mail_chroot can now contain %variables (e.g. /home/%u)
- fixed a bad maildir crashing bug
- ssl-params is now run with +15 priority when generating the ssl parameters
- Redesigned how login processes log in and create imap/pop3 processes. This fixes several settings and some other problems, plus it's now also possible for a single imap/pop3 process to handle multiple connections. If you want to try this, modify master.conf:
service imap { # comment out: #service_count = 1
# This should be at least the number of CPUs, maybe more (2-3x?) process_min_avail = 4
# Limit the number of clients a single process can handle. # Disk IO is blocking, so some commands can take a while. client_limit = 5 }
It currently doesn't even try to group same user's connections to same process, they'll just go randomly to whichever process manages to accept it first. Some day perhaps there should be a new service in the middle that keeps track of existing connections and forwards new ones to right mail processes.
v2.0.beta1 TODO list:
- master.conf has to be somehow put into defaults, so doveconf -n doesn't show its contents. an example master.conf would be minimal and show only those settings that admin might want to change (and those would show up in doveconf -n)
- verbose_proctitle=yes is now quite useless because of the imap/pop3 process creation change. Probably enable linux-proctitle-hack and start changing the proctitle much more often. For example it could contain the command that's currently being run by user. And login processes could contain how many client connections they currently have. And other processes too something similar..
- change plugin hook design to allow multiple users in same process to run different plugins
See alpha1 release announcement for more about these TODO:
- v1.x config backwards compatibility
- dsync is buggy
- config process is slow
- tcp-wrappers support
On 10/23/2009 05:14 AM Timo Sirainen wrote:
http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha2.tar.gz http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha2.tar.gz.sig
Changes since alpha1:
…
- Added doveadm who command for listing currently logged in users.
v2.0.beta1 TODO list:
- verbose_proctitle=yes is now quite useless because of the imap/pop3 process creation change. Probably enable linux-proctitle-hack and start changing the proctitle much more often. For example it could contain the command that's currently being run by user. And login processes could contain how many client connections they currently have. And other processes too something similar..
I had also the idea, that the verbose_proctitle could display additional the currently executed command. BUT, is there still a need for verbose_proctitle support? (It currently doesn't work on Linux.) I think it could be replaced by the new doveadm who command.
Regards, Pascal
The trapper recommends today: cafebabe.0929605@localdomain.org
On Fri, 2009-10-23 at 05:30 +0200, Pascal Volk wrote:
I had also the idea, that the verbose_proctitle could display additional the currently executed command. BUT, is there still a need for verbose_proctitle support? (It currently doesn't work on Linux.)
I'm trying to get setproctitle() syscall added to Linux, and in the mean time it could use the ugly hackish way that OpenSSH and sendmail also uses.
I think it could be replaced by the new doveadm who command.
Hmm. Perhaps. But that would need some way for doveadm to figure out what each process is doing. And that could be annoying to do.. Basically two possibilities:
a) doveadm connects to each process and asks what they're doing (and how would it connect?..)
b) each process is talking to some state gathering process and telling all the time what they're doing (waste of cpu/etc)
Timo Sirainen wrote:
It currently doesn't even try to group same user's connections to same process, they'll just go randomly to whichever process manages to accept it first. Some day perhaps there should be a new service in the middle that keeps track of existing connections and forwards new ones to right mail processes.
Might this drop out to some extent if you used some kind of consistent hash algorithm to map user_name to processes? I guess it's likely to be imperfect, but might buy you something for free?
Just a thought
Ed W
On Fri, Oct 23, 2009 at 6:14 AM, Timo Sirainen <tss@iki.fi> wrote:
http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha2.tar.gz http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha2.tar.gz.sig
I have successfully installed it on a few FreeBSD boxes (6.4 and 7.2) with a few hundred users each, in MySQL Db. Nothing changed so far in terms of tuning and it's been trudging on well since morning!
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223
"If you have nothing good to say about someone, just shut up!." -- Lucky Dube
participants (4)
-
Ed W
-
Odhiambo Washington
-
Pascal Volk
-
Timo Sirainen