Re: Spam on ticket #542

2013-07-15 Thread Aymeric Augustin
On 15 juil. 2013, at 03:20, Ramiro Morales wrote: > Would it be worth look at the web server log to see if these comments > were effectively created by HTTP POST requests at all? As far as I can tell, the spammer is using regular requests. While he has a browser-like user-agent, he's using HTTP

Re: Spam on ticket #542

2013-07-15 Thread Florian Apolloner
On Monday, July 15, 2013 3:20:16 AM UTC+2, Ramiro Morales wrote: > > Would it be worth look at the web server log to see if these comments > were effectively created by HTTP POST requests at all? > That's what I did to figure out the ip (which I blocked via iptables before Aymeric played with

Re: Spam on ticket #542

2013-07-14 Thread Ramiro Morales
On Sun, Jul 14, 2013 at 12:23 PM, Aymeric Augustin 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 furth

Re: Spam on ticket #542

2013-07-14 Thread Russell Keith-Magee
On Sun, Jul 14, 2013 at 11: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 mess

Spam on ticket #542

2013-07-14 Thread Aymeric Augustin
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 work