https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6187
--- Comment #2 from Mark Martinec <mark.marti...@ijs.si> 2009-09-03 05:29:43 PST --- > The ping method of Mail::SpamAssassin::Client send an extra $EOL > after the $EOL that terminates the PING command. That seems consistent with other command (request header + empty body). > spamd breaks the connection after answering PONG to the PING. Seems consistent with other commands. > If spamd has answered and hung up before the extra $EOL is sent, the ping > method gets a broken pipe even though tyhe connection is fine and it got a > PONG. > > For any client using Mail::SpamAssassin::Client and prudently doing a ping > before deciding that the connection is usable, this is obviously a problem. Right, that is a problem. Just don't know what the proper solution is (your proposed patch doesn't seem to be the right solution). I wonder if this handshake issue can be a problem with other commands too. Seems to me the proper solution would be to let the client side terminate the connection (for all commands), unless there is a serious breakage in the protocol (garbage or timeout) so that server may hang up on a problem client. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
