http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4861
------- Additional Comments From [EMAIL PROTECTED] 2006-04-19 20:10 ------- More information from the dcc mailing list: Vernon suggests a 10 second or even 15 second timeout because the 5 second one we now use is only good for the best case response. I believe we used to have it set at 10 seconds and reduced it when DCC sped up their server response. According to Vernon, "The typical DCC response arrives in perhaps 300 milliseconds as can be seen in the ms RTT for the chosen (marked by '*') server in the output of `cdcc info`. Long delays are needed only when dccifd or dccproc fails to get any answer despite retransmissions and then tries some other server and still gets nothing, or when a client has sent more than 400,000 requests per day and the server DoS defenses are delaying responses by 4 seconds are many seconds needed." So I'll change the default to 10 seconds if nobody has any objections. Regarding use of dccifd for reporting, Vernon's only negative comment about that was regarding the undesireability of adding code to SpamAssassin, with its associated memory requirements, possibility of bugs, etc., that goes with any extra code, for a relatively rare code path. My view about it is that the report code almost duplicates the check code, so I would like to check in this version that does use dccifd if it is available, and then some time in the future optimize it by merging the ddcproc check and report fuctions into one sub, and do the same for dccifd check and report. I don't want to assume that reporting spam is so rare -- I can see someone using SpamAssassin with a spamtrap to report a lot of spam, and using dccproc instead of dccifd would load the DCC servers. I also want to add a test case for DCC. Vernon suggested that GTUBE would be ok as a test message, but the client ip address should be something that is invalid such as 255.255.2552.255, not for example a 192.168.*.* address which would end up causing problems for someone using DCC who has that address on an internal mail server and who does not configure DCC/SpamAssassin just right. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
