Hi, So actually this can't really prevent "floods", I mean there's a difference between getting 100 connections from an IP in a period of 1 day and getting 100 connections in a period of 1 minute. The first doesn't constitute a problem, the second represents a flood problem.
It's quite an important distinction and it's important to try and prevent floods. Is the only way, then, to differentiate between the two to have a global filter running which keeps track of connections? > > I couldn't find this in the documentation, what is the > > setting for this upper limit on number of connections? > > MAXPERC and MAXPERIP variables, set in the configuration > file. > > > Also, this limit is based on certain window of time? > > What time frame constitutes "too many connections"? > > The time frame is "at any given time". Connections from > the same IP address or the same /24 where there are > already the maximum number of existing connections, are > rejected. ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
