> That said, reading RFC5321, part 4.1.1.10, it says (in part): > 4.1.1.10. QUIT (QUIT)
> This command specifies that the receiver MUST send a "221 OK" reply, > and then close the transmission channel. which means that the server, after sending the 221 reply should take care of closing the connection on its side > So to me, this says that after ASSP sends the 221 reply to the > client, it should ensure the reply was sent (I know when I wrote > an SMTP proxy once, I had problems because I would send > the 221 reply and close the connection immediately, and the > 221 reply would not make it out before the connection was > closed), and then close the channel - not wait for the client to > close it. there shouldn't be any problem as long as the linger time is respected and as far as I can tell, the perl code handling the sockets already does that and ensures that the buffers get correctly flushed before closing the socket; by the way, willing to be totally sure, one may add a timeout to the code, send out the "221" reply and wait until either the remote end closes the socket or the timeout expire and in the latter case proceed closing it ... but in general I don't think this should be needed ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
