Date: 2004-04-18T15:23:42 Editor: NoelBergman <[EMAIL PROTECTED]> Wiki: Apache James Wiki Page: NoFastFail URL: http://wiki.apache.org/james/NoFastFail
no comment Change Log: ------------------------------------------------------------------------------ @@ -1,6 +1,6 @@ The community behind the James server is currently not supporting fast-failing (or at most minimal support). Fast-failing means that when someone connects to your SMTP server, you reject the connection, sender, or email during the SMTP session rather than accept it first and reject it later. -Many people request this feature, so I'm writing up why we have decided against it. Note that I am presenting my personal (Serge Knystautas) view that is not necessarily shared 100% by the community (and, in fact, there is a proposal that will allow much more robust fast-fail in future versions of James). However, I present my complete biased philosophy so you can hear the argument in lieu of trying to explain the pragmatic, moderate stance of the community that is a balance of many voices. +Many people request this feature, so I'm writing up why we have decided against it. Note that I am presenting my personal (Serge Knystautas) view that is not necessarily shared 100% by the community (and, in fact, there is a proposal that will allow robust fast-fail in future versions of James). However, I present my complete biased philosophy so you can hear the argument in lieu of trying to explain the pragmatic, moderate stance of the community that is a balance of many voices. First I will list '''the reasons people typically want fast-fail''': * '''Doesn't this open me up to a denial-of-service situation where my mail server will be less available or slower?'''
