similar to: Sizing login_process_size and login_processes_count?

Hello, as described in [253363], login_process_size of 32M is not enough on 64-bit versions of Fedora and RHEL (and possibly other distributions as well). [253363] https://bugzilla.redhat.com/show_bug.cgi?id=253363 As I understand it, there's an intersegment gap between read-only/executable and writable segments of shared libs. That's probably a security feature or something. I found a

Our imap/pop service is moving from UW imap to dovecot 0.99.11 on RHEL4. This is for around 200 users with lots of different email clients, e.g.: Windows: outlook, outlook Express, eudora, thunderbird, netscape OS X: mail, eudora, thunderbird Unix/Linux: evolution, thunderbird, pine, mutt Web: squirrelmail Apart from the example configuration file, I can't find

I'm currently runing UW-IMAP (compiled vanilla) with procmail and mbox and am making my usual careful crawl (at turtle speed) through figuring out DC config. Some questions: a) I have something like 3-4 root imapd sessions so I presume that the default *login_processes_count* = 3 will be OK. I'm less clear about login_max_processes_count and login_max_connections = 256. A common

I got Dual Core Intel Xeon CPU 3.00GHz, over 1000 mailbox and almost 1 dovecot login / second (peak time). Server stats says that load is continually over 2 and cpu usage is 60%. top says that imap is making this load. virtual users are in mysql database and mysqld is running on another server (this server is ok). Do I need better CPU or is there something going on that I do not understand? #

Hi, I'm working for tuning a busy cluster of dovecot servers. Heach server as 4 core, 8GB of RAM and provide POP3 and IMAP access to mailbox. OS is Debian 6.0 and dovecot version is 1.2.15. I am unsure how to set "login_max_processes_count" and "login_max_connections" for reach the best situation when login_process_per_connection is set to no. I don't know what

Hi, I have test dovecot on one of my pop3/imap proxies (from rc10 to rc15). I immediately get a lot of error messages like this one : Nov 27 15:10:45 mproxy1 dovecot: pop3-login: file client.c: line 423 (client_unref): assertion failed: (client->destroyed) Nov 27 15:10:45 mproxy1 dovecot: child 21677 (login) killed with signal 6 A lot means one every 2 or 3 seconds. Any suggestion ?

Hi, It happens when I try to convert this config (with the dovecot 2.0 beta4 release) : test-mail:/tmp# dovecot -n -c ./dovecot.old.conf # 1.2.11: ./dovecot.old.conf # OS: Linux 2.6.26-2-686-bigmem i686 Debian 5.0.4 log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot_info.log protocols: imap listen: 127.0.0.1:30143 disable_plaintext_auth: no login_dir: /var/run/dovecot/login

Hi, I am having some trouble with dovecot (0.99.14) and maildir. Some users are reporting that sometimes, they don't get (pop3, various clients) new mails for a while even though they should. I checked and confirmed this: mails were delivered by MTA (sendmail, procmail). But when the problem existed, the new mails were in cur/, not new/ and dovecot would not report any new messaged to the

Hi all, I have some problem with dovecot in RHEL4. IMAP server is dropping connection after woorking for some time. It seems that the login process count keeps increasing?(stale login process are not removed) Any points to sort the problem? -- Adarsh

Hello, dovecot crashes when it receives -HUP signal. It happens always if there was some activity - for example, if I start dovecot, check any account through POP3 and then send -HUP to dovecot process, it crashes with the following log entry: segfault at 00000008 eip 0804d3fb esp bfdd3860 error 4 If there were no activity at all since starting, it does not crash. my dovecot -n output: #

Hi using dovecot 1.0.10 with pop/imap, using maildir, with 2000+ users mostly using pop but many using imap. Once in a great while I have problems with dovecot pop timing out. If I telnet to port 110 it just takes forever to come up or it doesn't at all, the samething happens on the imap port although 110 is always worst. At 1st when troubleshooting I was not sure what was causing the

I have a Dovecot server set up as a proxy and getting a ton of these errors, but I'm not sure where to begin troubleshooting it. I'm hearing frequently that Outlook users who use IMAP with SSL are getting disconnected often as a result. Any suggestions?... Sep 29 11:12:07 director4 dovecot: imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure

Hello there, I have been trying to make the patch work for libwrap(TCP Wrappers) posted on http://dovecot.org/patches <http://dovecot.org/patches%20Patch%20of%201.1> Patch of 1.1 but could not get it work. Any help will be highly appreciated. After compiling and running it I get error "Error: login_tcp_wrappers can't be used because Dovecot wasn't built with

Hi, I'm running Dovecot 1.1.3 on FreeBSD 7.0. In the past couple days, I've been seeing errors like this: Sep 9 08:43:51 sysvol dovecot: pop3-login: socketpair() failed: No buffer space available Sep 9 08:43:51 sysvol dovecot: pop3-login: socket(default) failed: No buffer space available Sep 9 08:43:51 sysvol dovecot: pop3-login: Can't connect to auth server at default: No

Am 20.07.2012 01:25, schrieb Edward Cavill: > Hi in the wiki, using 64 without the trailing M gives an error. > > <code> > The dovecot configuration file is located at /etc/dovecot.conf. The > following lines should be added, edited or uncommented: > > login_process_size = 64 > > [root at localhost etc]# /etc/init.d/dovecot start > Starting Dovecot Imap:

re: > # Maximum number of login processes to create. The listening process count > # usually stays at login_processes_count, but when multiple users start logging > # in at the same time more extra processes are created. To prevent fork-bombing > # we check only once in a second if new processes should be created - if all > # of them are used at the time, we double their amount

Hello all, Although i'm aware that version 1.0.15 is rather old, that's what is used in Lenny, so... Either way, the setup is rather simple, regular dovecot install, with maildirs residing on a "local" ext3 filesystem accessed through FC to a SAN (2Gbps link). The server has 2 cores (with HT), so "almost" 4 cores and 3GB of ram. A couple weeks ago we had a major

After updating my system from OpenSSL 0.9.8j to 0.9.8k Dovecot has stopped functioning properly with TLS sessions. The version of Dovecot does not seem to matter as I tried 1.1.11 - 1.1.14. Other programs using SSL/TLS such as Postfix and lightty still work fine when built with the newer release of OpenSSL. The IMAP client doesn't matter. For the time being I have gone back to .13 linked

Hi, I am trying to use the command: doveconf -n -c dovecot-1.conf > dovecot-2.conf to upgrade my dovecot.conf file, but it fails (see below). Judging from the message that vsz_limit is the new setting for login_process_size, I have retried using login_process_size=256 rather than login_process_size=64 (which was the initial value), but the error persists. Please advise. Thanks, Nick

Hi, We are migrating from a windows server and i have very few stats as to what our current concurrent usage stats are other than about 50,000 active users and 90,000 email messages a day inbound 20,000 outbound. Anyone got some tips for tuning dovecot to handle this load? Below is my config - do the values of login_process_size etc sound correct? Also my logs seem to be written out as root