http://bugzilla.spamassassin.org/show_bug.cgi?id=2070
------- Additional Comments From [EMAIL PROTECTED] 2004-03-08 07:07 ------- For reference, the TIME_WAIT state is an RFC requirement for TCP stacks. It's not a spamd bug, but a OS enforced protocol requirement. Applications cannot "leave" a socket in TIME_WAIT.. the OS's TCP stack forces them there and it is outside of the applications control. In many OSes you can modify the duration of the TIME_WAIT state, but it is criticaly important that the state exist. It's there to deal with any late arriving duplicate packets. The old standard was 240 seconds of time wait. Many newer OSes use 60 seconds. Stevens has shown you can safely do 12 seconds, see TCP/IP illustrated vol 3 for more detail. Linux boxes can modify the duration using /proc. Windows boxes can modify it in the registry: http://www.winguides.com/registry/display.php/878/ I'd advise the sa-dev team close this bug as INVALID. It's not a bug, it's a misunderstanding of TCP/IP (and a quite common misunderstanding). ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
