On Sun, Jul 14, 2013 at 12:23 PM, Aymeric Augustin <aymeric.augus...@polytechnique.org> wrote: > Hello, > > For some reason, ticket #542 has been collecting spam comments that bypassed > Trac's antispam. Since receiving spam on django-updates and deleting it > manually gets tedious after 100 messages, I hacked Trac to prevent further > comments on this ticket. > > I'm positive that Trac's antispam works in general: the monitoring views > shows that it fends off over 200 spams every day. However, these comments > weren't blocked and they don't appear in the monitoring view. I can't explain > that. Please contact me privately if you can help!
Thanks for that, I myself deleted 10+ such comments and was starting to feel like the the dumb side of the battle because the spammer side most surely was a script :) This is what I found: * Feeding the comments contents to our Trac instance Bayes anti-spam component test form says it would be effectively be identified as spam with a 100% confidence score. * Strangely enough, looking at the anti-spam monitoring log, there is no trace of these attempts (what would mean it isn't even detected as a comment worth being analyzed in search of spam), but I saewat least another attempt by another spammer being successfully rejected. Would it be worth look at the web server log to see if these comments were effectively created by HTTP POST requests at all? Thanks, -- Ramiro Morales @ramiromorales -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
