Hi Murray,
At 16:23 11-04-2011, Murray S. Kucherawy wrote:
>This typically means that, during the end-of-message phase of
>milter, the MTA gave up waiting for the filter to say something and
>closed the connection; eventually the filter did have something to
>say, but the socket joining them had been closed by then. It
>certainly should be unusual. It should also be the case that
>progress messages from the filter should keep the read timeout from
>hitting, but there's a second EOM timeout that can't be avoided,
>though that's pretty long by default (a full minute?).
The processing after the EOM should be quite fast. There is an
overall timeout of 5 minutes which is configurable. The progress
messages restart the timeout period. What is that second EOM timeout?
Regards,
-sm
Received on Mon Apr 11 2011 - 23:49:54 PST
This archive was generated by hypermail 2.2.0+W3C-0.50 : Sun May 15 2011 - 15:59:41 PST