Hi. I have noticed a strange behaviour for courier imap. It has occured 2 times in about 2 weeks, so I have no clue how to get it reproduced.
Courier is set up to allow 200 connections in total and at maximum 50 connections per IP address. Our user accounts are configured (via PAM) to allow a maximum of 300 processes running for each user account. Now I saw that a user was no longer able to log in (SSH or IMAP) because his account was full with imapd-Processes. There were about 300 imapd-Processes for his account and no new processes could be created. According to the courier configuration, this cannot happen as new connections should be denied when 200 processes are running (in total). As this single user connects only from one IP address, his limit should be triggered much earlier. As I cannot reproduce this and are not sure where to start debugging, I want to ask if someone have had a similar problem with courier or if anyone could give me a hint where to start debugging.
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
