SA Bugzilla – Bug 218
Local checksum db, count of deliveries, threshold
Last modified: 2002-06-15 03:58:08 UTC
I'd like to see capability for a local checksum database for ALL inbound messages that spamd could use for a test. Have some sort of config option that would allow you to set a threshold for number of identical deliveries. The reason - recently we were targetted with a specific piece of hate mail that was directed at all of our membership. Since this was directed hate mail, and not spammed widely, it most likely would not have been caught by normal rules or razor. Having the capability to check a local checksum would definately help. I'm not sure how beneficial it would actually be though, would need to be investigated.
Subject: Re: New: Local checksum db, count of deliveries, threshold On Wed, 17 Apr 2002, bugzilla-daemon@hughes-family.org wrote: > http://www.hughes-family.org/bugzilla/show_bug.cgi?id=218 [...] > I'd like to see capability for a local checksum database for ALL > inbound messages that spamd could use for a test. Have some sort of > config option that would allow you to set a threshold for number of > identical deliveries. This is what the Distributed Checksum Clearinghouse[1] does. They offer the server to you for the purpose of running a local filter based on their technique as well as participating in the larger network of servers sharing information. [...] > Having the capability to check a local checksum would definately help. > I'm not sure how beneficial it would actually be though, would need to > be investigated. Adding the DCC filtering, using only a local server, would allow you to do this with existing code. :) Daniel Footnotes: [1] <http://www.rhyolite.com/anti-spam/dcc/>
Subject: [SAdev] Re: New: Local checksum db, count of deliveries, threshold On Wed, 17 Apr 2002, bugzilla-daemon@hughes-family.org wrote: > http://www.hughes-family.org/bugzilla/show_bug.cgi?id=218 [...] > I'd like to see capability for a local checksum database for ALL > inbound messages that spamd could use for a test. Have some sort of > config option that would allow you to set a threshold for number of > identical deliveries. This is what the Distributed Checksum Clearinghouse[1] does. They offer the server to you for the purpose of running a local filter based on their technique as well as participating in the larger network of servers sharing information. [...] > Having the capability to check a local checksum would definately help. > I'm not sure how beneficial it would actually be though, would need to > be investigated. Adding the DCC filtering, using only a local server, would allow you to do this with existing code. :) Daniel Footnotes: [1] <http://www.rhyolite.com/anti-spam/dcc/> -- Listen to the victim, abused by the system The basis is racist, you know that we must face this. "It can't happen here". Oh yeah? "Take a look around at the cities and the towns." -- Pop Will Eat Itself, _Ich Bin Ein Auslander_ (Dos Dedos Mis Amigos) _______________________________________________ Spamassassin-devel mailing list Spamassassin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spamassassin-devel
Very cool. I assumed that DCC was similar to Razor where it only tracked known spam.
Subject: Re: Local checksum db, count of deliveries, threshold On Wed, 17 Apr 2002, bugzilla-daemon@hughes-family.org wrote: > Very cool. I assumed that DCC was similar to Razor where it only > tracked known spam. No. I considered implementing it until I happened across a side note on their site that lead to the explanation. The main problem it has is false positives -- because it has no ability to decide what is or isn't SPAM, it's very prone to false positives. So, if you want it to work correctly you have a couple of choices as I see them: 1) Whitelist everything that is sensible bulk email. 2) Submit anything that scores above 0 (or 1, 2, etc) to a local DCC. The second option seems the most reasonable to me. That way you get things that /may/ be SPAM added to the DCC processing which, if they really are bulk, means that they will be noticed as such eventually. This can all be done with procmail and friends, though adding support to SpamAssassin for the client side[1] might make life easier. Daniel Footnotes: [1] Which has already been suggested, if (possibly) not listed in bugzilla.
Yeah, Bug #71 is the DCC support one. Also, I proposed a spam score cache back in bug #128. This is probably a duplicate of one or both of them. Dan.
I'm going to close this out because as Daniel says, this is probably a dupe of one of those two bugs. Alternatively, it could also be that Razor2 solves this problem in yet another way. In any case, implementing it as part of SA would be so close to duplicating DCC/Razor functionality that I don't think it makes sense for us to do it.