On Freitag, 8. Juni 2007 Tom Allison wrote: > But is DCC going to want you sweeping 1000's of emails a minute > against their servers to see if they're spam yet?
I meant you calculate the DCC checksum on arrival as usual, and store it in a field. Every hour or so, you make a GROUP BY to check how often each signature got hit. And then, if you've got some extreme values (e.g. 30% of all e-mail in the last hour had the same checksum), you check this one checksum again against DCC. There's a high probability they list it as spam already, so you can reprocess your e-mail locally. That way, it's only one extra lookup on DCC. 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
