http://bugzilla.spamassassin.org/show_bug.cgi?id=4260
------- Additional Comments From [EMAIL PROTECTED] 2005-05-08 18:52 ------- Very strange results: I'm running mass-check on about 11,000 messages. Previous results showed the first two bogus rr messages between 50% and 60%, then about two more between 605 and 70%, and then some more (I don't have the exact number handy right now, but I think another 8 or so) in the last deciles. This was unchanged with the last patch. I modified connect_sock to use a random port between 1024 and 65535 each time it creates a socket. The currently checked in code creates a new socket with each message. The result of the one test run I did was two bogus rr messages between 40% and 50%, and no others for the rest of the run. I'm going to try to think of how there could have been a collision that showed up so soon and then no others. The answer may be to give up on trying to avoid port/ID collisions and just use a hash to allow us to drop the bogus packets immediately. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
