Alessandro Vesely writes:
> couriertcpd is the best place to implement throttling, hence the controls. This > is already actually implemented, but I keep forgetting to document it. So, now> I documented it.What did you add? Any pointer?
The -maxperip and -maxperc options to couriertcpd have been implemented for many years, you could set them in the imapd config file right now.
What I did add was a makeimapaccess wrapper, that's analogous to makesmtpaccess, and sets up the access file used by the couriertcpd instance for imapd, and imapd-ssl.
An access file can set the MAXCPERIP environment variable, for a connection from a particular IP address. This overrides the -maxperip setting for that IP address. The theory is to use -maxperip to throttle the maximum number of connections from all global IP addresses, and use MAXCPERIP to give a larger limit to your webmail server, that uses IMAP sessions.
MAXCPERIP was someone else's patch, some time ago. It's also been here for a while, just not documented, and the makeimapaccess script now provides a standardized way to set it up, instead of having everyone roll their own implementation.
pgpY5iQ1jCzIC.pgp
Description: PGP signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
