SpamikazeWiki:

The current implementation of Spamikaze has only a primitive way of avoiding false positives: querying one or more WhiteLists of known mail servers (eg. whitelist.surriel.com) and avoiding the listing of those IP addresses. Not only is it a lot of work to manually maintain such a whitelist, but such a whitelist is also bound to be incomplete and/or inaccurate.

Spamikaze's goal would be to only block those IP addresses that send out a lot of spam and little legitimate email; that way the users of Spamikaze powered DNSBLs would get little spam, while losing only very little legitimate email. There are various ideas on how to identify both spammy IP addresses (that should be blocked) and IP addresses that are the source of lots of legitimate email (and should not be blocked). Please add your idea to this list, so we can discuss them all and decide what to do:

Rik's idea

This method should be best for large sites, or DNSBLs that get a reasonable number of queries.

enhancements

optimizations

lonki's idea

This method should be best for small (or even personal) Spamikaze installations.

Nico's Idea

Using a greylisting method reduces the amount of spam tremendously without (almost) any false positives.

Such a greylist system also produces a record of servers which deliver large amounts of mail over a period of time as well as servers who try to initially send mail, get temporary rejected and never try again to the same recipient. Such servers are obvious sources for being blacklisted.

SpamikazeWiki: FalsePositives (last edited 2017-12-29 04:15:27 by localhost)