[Dovecot] v2.0.7 released
http://dovecot.org/releases/2.0/dovecot-2.0.7.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.7.tar.gz.sig
* master: default_process_limit wasn't actually used anywhere,
rather the default was unlimited. Now that it is enforced, you might
notice that the default limit is too low and you need to increase it.
Dovecot logs a warning when this happens.
* mail-log plugin: Log mailbox name as virtual name rather than
physical name (e.g. namespace prefix is included in the name)
+ doveadm dump: Added imapzlib type to uncompress IMAP's
COMPRESS DEFLATE I/O traffic (e.g. from rawlog).
- IMAP: Fixed LIST-STATUS when listing subscriptions with
subscriptions=no namespaces.
- IMAP: Fixed SELECT QRESYNC not to crash on mailbox close if a lot of changes were being sent.
- quota: Don't count virtual mailboxes in quota
- doveadm expunge didn't always actually do the physical expunging
- Fixed some index reading optimizations introduced by v2.0.5.
- LMTP proxying fixesOn 11/8/2010 11:51 AM, Timo Sirainen wrote:
http://dovecot.org/releases/2.0/dovecot-2.0.7.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.7.tar.gz.sig Does this include the fix for the SIS error logs previously mentioned?
Daniel
On 8.11.2010, at 20.44, Daniel L. Miller wrote:
On 11/8/2010 11:51 AM, Timo Sirainen wrote:
http://dovecot.org/releases/2.0/dovecot-2.0.7.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.7.tar.gz.sig Does this include the fix for the SIS error logs previously mentioned?
Yeah. Whenever I give some URL to hg it's always included in next release.
Just installed it and getting this warning:
doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (1603)
Not sure what this means.
On Wed, 2010-11-10 at 10:32 -0800, Marc Perkel wrote:
Just installed it and getting this warning:
doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (1603)
Not sure what this means.
You should set:
service anvil { client_limit = 2000 # or something }
On 10.11.2010, at 19.50, Marc Perkel wrote:
On 11/10/2010 10:52 AM, Timo Sirainen wrote:
service anvil { client_limit = 2000 # or something }
OK - just curious - what is it for? What does this do?
Increases the number of connections that anvil process can handle before it stops accepting new ones. The default limit should be fine as long as you don't change other services' process_limits from defaults. Hmm. Actually the default 1000 limit should be high enough for pretty much all setups. What exactly have you changed to cause that warning? Show your doveconf -n output?
On 11/10/2010 5:25 PM, Timo Sirainen wrote:
On 10.11.2010, at 19.50, Marc Perkel wrote:
On 11/10/2010 10:52 AM, Timo Sirainen wrote:
service anvil { client_limit = 2000 # or something }
OK - just curious - what is it for? What does this do? Increases the number of connections that anvil process can handle before it stops accepting new ones. The default limit should be fine as long as you don't change other services' process_limits from defaults. Hmm. Actually the default 1000 limit should be high enough for pretty much all setups. What exactly have you changed to cause that warning? Show your doveconf -n output?
The only thing I changed was upgrading for 2.06 to 2.07.
# 2.0.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-dzhanibekov.1 x86_64 Fedora release 12 (Constantine) simfs auth_debug = yes auth_master_user_separator = * disable_plaintext_auth = no dotlock_use_excl = yes first_valid_uid = 12 info_log_path = /var/log/dovecot.log log_path = /var/log/dovecot.log login_greeting = Computer Tyme Dovecot ready. mail_fsync = never mail_gid = mail mail_location = maildir:/vhome/%d/home/%n:INDEX=/imap-cache/%d-%n mail_uid = mail mmap_disable = yes passdb { args = /etc/dovecot/sql.conf driver = sql } passdb { args = /etc/dovecot/master-combined-sql.conf driver = sql master = yes pass = yes } protocols = imap pop3 service anvil { client_limit = 2000 } service auth { unix_listener auth-client { mode = 0666 } unix_listener auth-master { mode = 0666 } } service imap-login { process_limit = 800 process_min_avail = 100 service_count = 0 vsz_limit = 64 B } service imap { process_limit = 400 } service pop3-login { process_limit = 800 process_min_avail = 40 service_count = 0 vsz_limit = 64 B } service pop3 { process_limit = 400 } ssl_cert =
On 12.11.2010, at 11.16, Marc Perkel wrote:
service imap-login { process_limit = 800 process_min_avail = 100 service_count = 0
With service_limit=0 the process limits are way way too high. process_min_avail should be the number of CPU cores you have. Also when your process_limit would be reached you'd have 800000 IMAP connections (process_limit * default_client_limit).
vsz_limit = 64 B
This is 64 bytes .. Strange that it even works, remove it or change it.
service pop3-login { process_limit = 800 process_min_avail = 40 service_count = 0 vsz_limit = 64 B }
Same for pop3-login.
On 11/12/2010 6:57 AM, Timo Sirainen wrote:
On 12.11.2010, at 11.16, Marc Perkel wrote:
service imap-login { process_limit = 800 process_min_avail = 100 service_count = 0 With service_limit=0 the process limits are way way too high. process_min_avail should be the number of CPU cores you have. Also when your process_limit would be reached you'd have 800000 IMAP connections (process_limit * default_client_limit).
vsz_limit = 64 B This is 64 bytes .. Strange that it even works, remove it or change it.
service pop3-login { process_limit = 800 process_min_avail = 40 service_count = 0 vsz_limit = 64 B } Same for pop3-login.
OK - I'm not sure how they get set that way. I must have copied something. Here is my new settings. Is there anything else to change or add?
# 2.0.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-dzhanibekov.1 x86_64 Fedora release 12 (Constantine) simfs auth_debug = yes auth_master_user_separator = * disable_plaintext_auth = no dotlock_use_excl = yes first_valid_uid = 12 info_log_path = /var/log/dovecot.log log_path = /var/log/dovecot.log login_greeting = Computer Tyme Dovecot ready. mail_fsync = never mail_gid = mail mail_location = maildir:/vhome/%d/home/%n:INDEX=/imap-cache/%d-%n mail_uid = mail mmap_disable = yes passdb { args = /etc/dovecot/sql.conf driver = sql } passdb { args = /etc/dovecot/master-combined-sql.conf driver = sql master = yes pass = yes } protocols = imap pop3 service anvil { client_limit = 2000 } service auth { unix_listener auth-client { mode = 0666 } unix_listener auth-master { mode = 0666 } } service imap-login { process_limit = 800 process_min_avail = 10 service_count = 0 } service imap { process_limit = 400 } service pop3-login { process_limit = 800 process_min_avail = 10 service_count = 0 } service pop3 { process_limit = 400 } ssl_cert =
On Sun, 2010-11-14 at 06:35 -0800, Marc Perkel wrote:
OK - I'm not sure how they get set that way. I must have copied something. Here is my new settings. Is there anything else to change or add?
service imap-login { process_limit = 800 process_min_avail = 10 service_count = 0 } service pop3-login { process_limit = 800 process_min_avail = 10 service_count = 0 }
The above process_limits are still much higher than useful. They aren't really harmful, but could be confusing.. I'd just remove them and let them be defaults (default=100).
On Tue, Nov 16, 2010 at 10:54 AM, Timo Sirainen tss@iki.fi wrote:
On Sun, 2010-11-14 at 06:35 -0800, Marc Perkel wrote:
OK - I'm not sure how they get set that way. I must have copied something. Here is my new settings. Is there anything else to change or add?
service imap-login { process_limit = 800 process_min_avail = 10 service_count = 0 } service pop3-login { process_limit = 800 process_min_avail = 10 service_count = 0 }
The above process_limits are still much higher than useful. They aren't really harmful, but could be confusing.. I'd just remove them and let them be defaults (default=100).
Just FYI on the odd imap-login vsz_limit, if I don't specify a vsz_limit for either pop3-login or imap-login, they show up as '64 B' for me too. That appears to be what's hardcoded as the default in ./src/imap-login/imap-login-settings.c and ./src/pop3-login/pop3-login-settings.c. Should that be jacked up?
On Tue, 2010-11-16 at 11:27 -0800, Mark Moseley wrote:
Just FYI on the odd imap-login vsz_limit, if I don't specify a vsz_limit for either pop3-login or imap-login, they show up as '64 B' for me too. That appears to be what's hardcoded as the default in ./src/imap-login/imap-login-settings.c and ./src/pop3-login/pop3-login-settings.c. Should that be jacked up?
Yeah, you're right. Fixed: http://hg.dovecot.org/dovecot-2.0/rev/ddd929c68c0f
participants (4)
-
Daniel L. Miller
-
Marc Perkel
-
Mark Moseley
-
Timo Sirainen