Bernd Wurst writes:
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.
I don't believe that this PAM feature works with Courier. IIRC, this PAM module hooks into the pam_open_session() and pam_close_session() API calls.
courier-authlib is now running as a separate process. Once authdaemond validates the login ID and the password, authdaemond has no further knowledge of the client session. It will have no further knowledge when the login session has been terminated. As such, authdaemond has no means of invoking pam_open_session() and pam_close_session() in an intelligent manner, so anything that keys off the session feature of PAM is not going to work with Courier.
pgpQQgV36FFMr.pgp
Description: PGP signature
------------------------------------------------------------------------------ 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
