Hi Sam.

Am Montag 05 Juli 2010, 22:50:25 schrieb Sam Varshavchik:
> 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.

Okay, I don't know much about the internals of this but I see the effect.
When this one happens, there are many processes "/usr/bin/imapd" running with 
the UID set to the user.

These processes are counted for the user's limit and SSH or "su" logins are no 
longer possible. Local delivery processes are also no longer possible (I see 
an appropriate error message in the log of courierlocal).
IMAP logins are also no longer possible, the user said (I did not test this as 
I don't have the user's IMAP credentials).

But apart from this, how could it happen that my configured limit of maximum 
imap processes (MAXDAEMONS=200 and MAXPERIP=50) is not respected?

Attachment: 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

Reply via email to