SpamikazeWiki
  • Comments
  • Immutable Page
  • Menu
    • Navigation
    • RecentChanges
    • FindPage
    • Local Site Map
    • Help
    • HelpContents
    • HelpOnMoinWikiSyntax
    • Display
    • Attachments
    • Info
    • Raw Text
    • Print View
    • Edit
    • Load
    • Save
  • Login

Spamikaze

  • Spamikaze front page

  • About Spamikaze

  • MailingList

  • Spamikaze DNSBLs

Documentation

  • Installation

  • Configuration

  • Operations

  • Web Scripts

  • WhiteLists

Developers

  • GitHub repository

  • DevelopmentTodo

  • DatabaseDesign

  • DatabaseModule

  • FalsePositives

  • DistributedSpamikaze

Wiki

  • EditorsGroup

  • Side Bar

  • Hosted at WikiWall

Navigation

  • RecentChanges
  • FindPage
  • HelpContents
Revision 1 as of 2005-04-04 22:52:29
SpamikazeWiki:
  • DistributedSpamikaze

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:

  • MoinMoin Powered
  • Python Powered
  • GPL licensed
  • Valid HTML 4.01