On 5/11/05, Daniel Perry <[EMAIL PROTECTED]> wrote: > James recieves data command. Responds accordingly. > James starts receiving data. Once hit's maximum limit, an exception causes > james to send a 552 error (immediately). > Now, this is where i might be missing somthing, but James then seems to > return to reading commands, but as the state MESG_FAILED is set, > parseCommand skips logging, and doesnt return 500 error messages!
Yes, that sounds right. > If i am right, it should: > Notice to size limit has been reached, and stop buffering the message. > Continue reading the message until <crlf>.<crlf> is reached > Send 552 error! > Reset state, and continue to accept other messages. IMHO when the limit is reached, we should either (soft fail) listen to everything and ignore the data as you describe above, or (hard fail) kill the connection. Right now what we does not make a lot of sense, since we haven't reduced bandwidth. -- Serge Knystautas Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
