http://bugzilla.spamassassin.org/show_bug.cgi?id=3917
------- Additional Comments From [EMAIL PROTECTED] 2004-11-21 12:57 ------- I went back to my last attachment, which is in perl. With a sleep(5) after the sending of the message to $client, followed by print $client "this is a test\n"; it ends up with a broken pipe error when trying to do that last print. That implies that perl is doing its own buffering of the data sent out over the socket and autoflush does not seem to force it to send after every print. If there is a sleep(1) after a print, then the data is flushed. But without that sleep call it appears that perl is buffering the print statements, resulting in a single long send that dies when it is finally sent out. If it turns out that the only workaround that lets us have a server on Windows in perl is to break up the messages and insert calls to sleep, I'm inclined once again to just say that the server does not work in Windows. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
