Bug tracker spam filter is broken.

[tdhutt@…]

I just created a new ticket, and the spam filter is broken in at least 3 ways:

1. It marked my message as spam when it very obviously wasn't.
2. It asked me to "respond to the following." which was presumably meant to be followed by a captcha, but there wasn't actually anything to respond to.
3. I clicked "back" and resubmitted the form and it worked! Surely if it thinks I am a spammer and can't answer the (non-existant) captcha I shouldn't be allowed to do that?

[Aymeric Augustin]

Thanks for the report. The core team is aware of the problem: Trac's spam filter isn't fantastic.

However, we don't have a better alternative, and we prefer to keep it possible to contribute without creating an account.

And we focus our energy on improving Django rather than improving Trac :)

I recommend to create an account; you'll hardly ever encounter the spam filter when you're logged in.

[Aymeric Augustin]

Erm, it appears I spoke too fast. The spam plugin is really broken. This may be a consequence of the upgrade to Trac 1.0.

[Aymeric Augustin]

The problem is that code.djangoproject.com uses HTTPS, but reCaptcha is served over HTTP, and browsers refuse to load mixed content.

I've resolved this problem by switching to a different captcha.