On 2008-07-11 05:00:06 -0500, Jared Johnson wrote: > I've noticed that our qpsmtpd-based product is not handling extremely > large messages particularly well. This was brought on by a flood of > delay notices for a 495MB message sent outbound through a server not > under our control. There are a number of fixes in the pipeline, but > it occurs to me that the most appropriate thing would be to drop a > connection and stop listening when we have received what we consider > to be too much data after the DATA command.
That's an extremely bad idea. If you just drop the connection in the
middle of a transfer, the client will register a temporary failure and
send the message again. And again, and again, and again, ...
The best thing you can do is receive the message completely and then
reject it with a 5xx reply. If the client supports the SIZE extension,
you can also tell it in advance the largest message size you are
prepared to accept and then the client won't even send the message if it
is larger. Unfortunately some clients still don't support it.
hp
--
_ | Peter J. Holzer | Openmoko has already embedded
|_|_) | Sysadmin WSR | voting system.
| | | [EMAIL PROTECTED] | Named "If you want it -- write it"
__/ | http://www.hjp.at/ | -- Ilja O. on [EMAIL PROTECTED]
signature.asc
Description: Digital signature
