Steve,
I've been running James in production, and have not had a problem. Spam is
more of an issue that DoS. And I limit the size of messages.
Besides which, what you consider DoS, someone else might consider a normal
load. I think it is more important for James to scale and degrade
gracefully.
However, there will likely be some additional fast-fail cases. But at least
initially, the ones I would consider are those that do not require any
content analysis. In other words, the only one currently not in place would
be IP based blocking, which has to be done in a special manner to retain RFC
compliance. This is a non-trivial enhancement because you may have multiple
IP black lists and white lists, and each one may have multiple zones.
Hacked up IP blocking solutions are already available. If we are going to
make the change, I want to make it *right*.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
