search for: login_processes_count

Any suggestions on sizing login_process_size and login_processes_count for a server expected to be doing 100 to 200 simultaneous connections? Is there a way to separate login_processes_count between imap and pop? I would like to have at least 50 imap processes ready, but we rarely have any more than 5 to 10 pop connections. Would be a shame to have 40+ pop login...

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 until the limit set by > # thi...

...ax_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 value to set login_max_processes_count. For example is better the first or the second configuration? login_process_per_connection=no login_processes_count=4 login_max_processes_count=8 login_max_connections=512 login_process_size=128 login_process_per_connection=no login_processes_count=4 login_max_processes_count=16 login_max_connections=256 login_process_size=128 Which is a suggested ratio from login_max_processes_count and login_max_connections...

Hi list! I'm a little confused. I have set "login_process_per_connection = yes" and "login_processes_count = 1", and this is how my pstree looks when nobody is connected: dovecot -,- dovecot-auth `- imap-login However, when I connect with a client it looks like this: dovecot -,- dovecot-auth |- imap `- 2*[imap-login] I would expect it to only have...

...imap-login processes getting a lot of file descriptors in use. We initially spawn off 10 imap-login processes and have each handling 256 connections. Full "dovecot -n" at the end of the message, but the relevant settings here are: login_process_size = 64 login_process_per_connection = no login_processes_count = 10 login_max_processes_count = 128 login_max_connections = 256 We have grown to suspect it is to do with one of the imap-login processes having a large number of files open. Killing the process seems to get rid of the problem. For example currently we have 11 imap-login processes running, one...

Hi, Im using dovecote as my IMAP interface. However i do have a lot of imap instances. its only 7 user using the system as i get this. please advice. 1230 ? S 0:00 imap-login 1309 ? S 0:00 imap-login 1387 ? S 0:00 imap-login 1388 ? S 0:00 imap-login 1389 ? S 0:00 imap-login 1390 ? S 0:00 imap-login 1391 ? S

...nable to dlopen(/lib/security/pam_ck_connector.so): libdbus-1.so.3: failed to map segment from shared object: Cannot allocate memory Feb 10 08:29:06 home dovecot-auth: PAM adding faulty module: /lib/security/pam_ck_connector.so English, please? :) Strangely, it seemed to disappear after increasing login_processes_count, login_max_processes_count and/or auth_worker_max_count. -- Vegard Svanberg <vegard at svanberg.no> [*Takapa at IRC (EFnet)]

Hi. Does someone make update for `Multiple IP(or Host) listen in dovecot.conf'? I made trivial patch so. But this patch doesn't solve `Support listening in multiple sockets' in TODO. It appends only the capability as multiple listen in dovecot.conf. So, `login_processes_count' becomes ambiguous. In CASE1, login_processes_count = 2, forked imap-login processes are 8. -- samples dovecot.conf applied this patch are following. CASE 1: listen = 127.0.0.1, 192.168.0.10, imap-server1, imap-server2.example.com or CASE 2: protocol imap { listen = 127.0.0.1:143,...

..., mutt Web: squirrelmail Apart from the example configuration file, I can't find any guides for optimal values to use for dovecot's many configuration options. A few that look like they might need changing are: login_process_size = 32 login_process_per_connection = yes login_processes_count = 3 mbox_dotlock_change_timeout = 30 auth_count = 1 client_workarounds = Does anyone have any pointers to reasonable values for those or other settings? Thanks -- Ian

Hello, We are running Dovecot 1.0.0 (Debian Etch, Backports.org, OpenSSL) in a production environment and we experience sporadic SSL connection problems. At the moment, it's difficult to tell if the server goes back to normal operation after some time or if it can be reproduces at any time because we have to restart it as soon as we get Nagios alerts. Some tests with openssl s_client have

...MailDir's stored in NFS location -- User Authenticated using MySQL my dovecot.conf looks like base_dir = /var/run/dovecot/ protocols = imap pop3 listen = *, [::] log_path =/var/log/dovecot.log info_log_path = /var/log/dovecot-info.log ssl_disable = yes login_process_per_connection = no login_processes_count = 10 login_max_processes_count = 128 login_max_connections = 256 login_greeting = Dovecot ready. mail_location = maildir:~/ mail_debug = yes mmap_disable = yes dotlock_use_excl = yes mail_nfs_index = yes lock_method = dotlock mail_drop_priv_before_exec = yes first_valid_uid = 195 max_mail_processes...

...login_executable(pop3): /usr/local/dovecot-1.1.15/libexec/dovecot/pop3- login login_log_format_elements: user=<%u> method=%m REMOTE=%r LOCAL=%l %c login_process_per_connection: no login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_processes_count: 10 login_max_processes_count: 256 verbose_proctitle: yes mail_location: maildir:/home/email/%u/Maildir mailbox_idle_check_interval: 60 mmap_disable: yes fsync_disable: yes mail_executable(default): /usr/local/dovecot-1.1.15/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot-1.1.15/libe...

..._dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login login_greeting: Server ready. login_processes_count(default): 50 login_processes_count(imap): 50 login_processes_count(pop3): 5 login_processes_count(managesieve): 5 login_max_processes_count: 2048 max_mail_processes: 2048 mail_max_userip_connections(default): 25 mail_max_userip_connections(imap): 25 mail_max_userip_connections(pop3): 10 mail_max_us...

...no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting: D-V1 NP09 ready. login_process_size: 384 login_processes_count: 55 login_max_processes_count: 450 mail_location: maildir:/home/%1u/%u/Maildir maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/loc...

Is this the best way to get dovecot's pop3 process to run under xinetd? This is what I did after I installed postfix and dovecot. I am using Debian. I am using the dovecot local delivery agent. ---------first the dovecot configuration and version information------------------ dovecot -n output: # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 pop3s

...t at warsaw Maildir # dovecot -n # 1.0.13: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S ssl_listen: * login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_process_per_connection: no login_processes_count: 15 login_max_processes_count: 512 max_mail_processes: 4096 mail_privileged_group: mail mail_location: maildir:/var/mail/Maildir/%u maildir_copy_with_hardlinks: yes auth default: worker_max_count: 100 passdb: driver: pam args: cache_key=%u dovecot userdb: driver: passwd Any...

Hello, when running diff for 'dovecot -n' outputs from beta10 and beta11(for the same config file), I noticed that 'dovecot -n' beta11 output does not show anymore the following parameters, which are set to non-default values(and which 'dovecot -a' shows): login_processes_count login_max_processes_count first_valid_uid first_valid_gid cache_size cache_ttl cache_negative_ttl mode(from auth default section) And by the way, parameters from lda section are not showed both with -a and -n. But it is so already for a long time, so I assume that it is OK :) Regards, Ar...

...al/cert/mailper/chain.pem auth_debug = yes disable_plaintext_auth = no ## tuning ## login_process_size = 64 login_max_processes_count = 196 login_max_connections = 384 auth_worker_max_count = 30 ## fin tuning ## protocol imap { mail_plugins = quota imap_quota ## tuning ## login_processes_count = 4 ## fin tunning ## } protocol pop3 { mail_plugins = quota ## tuning ## login_processes_count = 3 ## fin tunning ## } auth_cache_size = 4096 auth_cache_ttl = 1800 protocol lda { mail_plugins = quota sieve postmaster_address = root at examp...

....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 login_executable: /usr/lib/dovecot/imap-login login_user: aquaray login_greeting: Mail - test v2 login_process_per_connection: no login_process_size: 96 login_processes_count: 20 login_max_processes_count: 196 max_mail_processes: 10024 mail_max_userip_connections: 10000 verbose_proctitle: yes first_valid_uid: 89 mail_location: maildir:~/:INDEX=/var/mail/dovecot_indexes/%1d/%d/%n fsync_disable: yes maildir_very_dirty_syncs: yes mbox_write_locks: fcntl dotlock mail_drop_p...

...x_processes_count and max_mail_processes settings # OS: AIX 3 0001112AD300 syslog_facility: local0 protocols: imap listen: *:2222 ssl: no disable_plaintext_auth: no login_dir: /usr/ladmin2/var/run/dovecot/login login_executable: /usr/ladmin2/libexec/dovecot/imap-login login_greeting: Dovecot ready. login_processes_count: 30 max_mail_processes: 4096 mail_location: mbox:%h/new:INBOX=/var/spool/mail/14/%u mmap_disable: yes dotlock_use_excl: no mbox_write_locks: fcntl mbox_lazy_writes: no mail_plugins: mbox_snarf imap_client_workarounds: delay-newmail auth default: mechanisms: plain gssapi krb5_keytab: /etc/krb5...