This might be a quite obvious solution but people seem to be happy with the performance of Bayesian filter when training it properly. Here are two articles I found explaining some good points to keep in mind while training the filter - edgewall-ticket-10314 <https://trac.edgewall.org/ticket/10314> and trac-wiki-spamfilters <https://trac.edgewall.org/wiki/SpamFilter#Bayes>; just wanted to make sure we are not being bitten due to bad training.
Also, if the spammers, assuming they are bots, are able to solve recaptcha, we can try keycaptchas <https://trac.edgewall.org/wiki/SpamFilter#Captcha> supported by Trac which are relatively harder to solve. If they are being hit manually by someone, the ip-throttling <https://trac.edgewall.org/wiki/SpamFilter#IPThrottling> technique might tackle such a situation (but then they'll use proxies, sigh!). Well, this is a tricky experimenting business but I hope something out of this works. On Saturday, 6 August 2016 18:26:34 UTC+5:30, Tim Graham wrote: > > Yes, the bayesian spam filter is giving some false positives and the > weighting is such that even if you submit the captcha, your comment still > might be considered spam (spammers were completing the captchas to submit > their content). You could look into if there's some other spam prevention > measures in Trac that might be more effective. > > On Saturday, August 6, 2016 at 7:55:18 AM UTC-4, akki wrote: >> >> Hi >> >> Recently, I would say since the past week, many of my activities on Trac >> are being reported as spam. Even trying to add myself to cc takes me to an >> error page. >> >> I got the following message when I last tried to modify a ticket. I was >> changing the summary of one of the tickets: >> >>> >>> >>> Submission rejected as potential spam >>> >>> - Akismet says content is spam >>> >>> >>> - SpamBayes determined spam probability of 93.46% >>> >>> >> I sometimes also get a page with a captcha but without a submit button >> and it redirects me to another TracError page if I submit it anyways by >> pressing the return key. >> >> >> Please take the necessary steps to mitigate this problem and let me know >> if there is something I could help with. >> >> Thanks >> >> On Thursday, 7 July 2016 08:03:54 UTC+5:30, Tim Graham wrote: >>> >>> In the past couple hours, code.djangoproject.com experienced a spam >>> attack of new tickets and wiki pages. After running without the spam filter >>> for at least a couple months (I forget exactly when I deactivated it but it >>> was sometime after we switched to requiring authenticated users to file a >>> ticket), I've reactivated it. If you find your submissions inappropriately >>> marked as spam, let me know so we can tune the settings. >>> >> -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a359b711-8101-46ca-a91d-ae1b59cf7997%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
