On 09/09/06 09:45, [EMAIL PROTECTED] wrote: > Hi. > > My two sites, trogger.de and trogger.info , were recently subjected to > a large trackback-spam attack. We're talking in the area of ten > thousand trackbacks within two or three days. Plus a couple hundred > spam somments in the same period. For the time being, I've disabled > trackbacks and anonymous comments. But that's just punishing the users > for the actions of a few freeloading idiots. > > Are there any technical countermeasures against trackback spam that > Djangonites have already successfully integrated into their Django > sites and used? > Using a keyword list would be one method (also easy to implement), but > then you're always playing catch-up with the spammers. > > Has someone already built an interface to Akismet or a similar service? >
Hi Daniel I haven't used this with django yet, but the approach outlined below has worked very well with a different blogging engine. - setup spambayes [1] on your server - train your site's content as "ham" - train some of those spammy comments/trackbacks as "spam" - run all incomming comments/trackbacks through spambayes - nuke messages marked as "spam" - store messages marked as "unsure" as disabled/draft. check these manually once in a while (I have a cronjob that sends me a mail if there are any) - store messages marked as "ham" as enabled/published Spambayes catches +- 99% of the junk. Zero false positives so far. [1] http://spambayes.sourceforge.net/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
