One of our community member institutions are running a Sakai cluster
using James. They use a Big-IP load balancer. When performing Big-
IP health checks every few seconds against various points in their
test system the testing generated numerous TCP connections.
There testing filled up the available number of connections to James,
and Sakai's email handling effectively shut down. They quickly
changed to SMTP checking and restarted, solving the immediate
problem, but there remains a concern about a potential "denial of
service" issue with the James component, since anyone can perform
that style of TCP check. Is there some way to configure James to not
be vulnerable in this way?
Cheers,
Anthony Whyte
Sakai Foundation
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
