Distributed Spamikaze has a number of goals:

• Block a spam source before it has spammed me, by knowing that it already spammed some other Spamikaze installations.
• Figure out that many people get legitimate email from a certain IP address, so it should not be listed.
• When in doubt about an IP address, get a second opinion.
• Make it harder for a real spammer to get his/her IP addresses removed from all the lists.
• Make Spamikaze invulnerable to the DDoS attacks that sometimes take out centralised DNSBLs.

There is not yet a design that would fulfill all these criteria. The main problem seems to be that "block a spam source that spammed other Spamikaze instances" requires a push model, while getting a second opinion on an IP address is more suitable to be implemented as a pull model. If you have an idea on how to get this fixed, please write it down here: