Special handling of the frequent Connection reset

Bad guys don't terminate the connection with a QUIT command, but simply 
disconnect when they see that they have no luck with the server. This is 
so frequent that it fills my log. Its logged on warn level, but until 
recently only if debug logging was switched on. In any case I don't want 
to see a stack trace even on debug level. Because of its regular 
appearance, this is something like a pseudo SMTP statement. Moreover, in 
such cases not one but two events are logged, it is a bit misleading 
(SubEthaSMTP tries to send an error message).
The attached patch logs these events separately. The logging event does 
include the exception for safety, but filtering the unique message text 
the logger can and should be configured to strip the stack trace.

Original issue reported on code.google.com by hontvari@flyordie.com on 28 Sep 2009 at 1:07

Attachments:

badguy-quit.patch

voodoodyne / subethasmtp

Special handling of the frequent Connection reset #18