On Freitag, 8. Juni 2007 Tom Allison wrote: > > - there are distributed checksums like DCC, pyzor, razor > > This makes sense, but how do you want to support it?
If you'd store the checksum(s) of these projects within searchable, indexable DB fields per each e-mail, you could make easy spam checking yourself. Imagine every 30 minutes you recheck the last received e-mails, and you find that 30% of them have the same DCC checksum. There's a BIG chance that those messages are spam. The point is it must be cheap (in terms of I/O and CPU) to find out which e-mails you want to doublecheck, as you can't reprocess all messages (at least not an ISP). So there's not really a lot of support to implement in dbmail. Just one/some fields per e-mail with checksum(s). A field spam_score would also be good. But it'd be good to speak with developers of SA, DCC and so on before, maybe they've got their own ideas already. mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846 914 666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: EA39 8918 EDFF 0A68 ACFB 11B7 BA2D 060F 1C6F E6B0 // Keyserver: www.keyserver.net Key-ID: 1C6FE6B0
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
