Due to a change in ssl handling in dovecot between hardy and dapper. The default configuration in dovecot can prevent server loads to rise and become non-responsive when using dovecot. In dapper the login_max_processes_count was not being enforced, however in hardy it is. The attached patch displays in the error log that max login count has been reached, it also puts a comment in the dovecot example configuration file.
Testcase (Should be done in a virtual machine)
1. Install dovecot.
2. Configure ssl with dovecot
3. Run the create users script.
4. Set the login_max_process_count option to 4.
5. Run the client login script.
Due to a change in ssl handling in dovecot between hardy and dapper. The default configuration in dovecot can prevent server loads to rise and become non-responsive when using dovecot. In dapper the login_max_ processes_ count was not being enforced, however in hardy it is. The attached patch displays in the error log that max login count has been reached, it also puts a comment in the dovecot example configuration file.
Testcase (Should be done in a virtual machine)
1. Install dovecot. process_ count option to 4.
2. Configure ssl with dovecot
3. Run the create users script.
4. Set the login_max_
5. Run the client login script.