Cool. Let's hope this works. I just thought of something, too: Apache Bloodhound is supposed to be "Trac + What-You-Really-Need" bundled together. Given the explosion of BH registrations over the past two weeks, it seems this might be one of those "necessary" plugins to bundle.
Arguably: in a LAN/workplace setting, this isn't needed. But any public-facing installation apparently needs some kind of captcha/filtering on user creation. Empirical evidence amply demonstrates this need :-) Cheers, -g On Sun, Jan 25, 2015 at 6:31 PM, Ryan J Ollos <[email protected]> wrote: > On Sun, Jan 25, 2015 at 1:59 PM, John Chambers <[email protected]> wrote: > > > I am not sure what the options are here as I am no expert in bloodhound / > > trac admin. But I am happy to get advice from others on here who are and > > implement the desired solution asap. > > > > Cheers > > > > John > > > > SpamFilterPlugin (1) (needs to be installed) together with > AccountManagerPlugin (2) (already installed) should provide some good > options. In particular, there is a RegistrationFilterAdapter in > AccountManager that passes registration information through the > SpamFilterPlugin. The author of SpamFilterPlugin has been active in > tweaking the configuration on trac-hacks.org to get rid of spam. We can > probably just carry over the configuration from that site and see how > effective it is once we train the filter. There is some relevant discussion > in (3), (4), (5). I'm happy to relay more information once you get > comfortable with administering issues.apache.org/bloodhound and are ready > to start installing and configuring additional feature. > > - Ryan > > (1) http://trac.edgewall.org/wiki/SpamFilter > (2) http://trac-hacks.org/wiki/AccountManagerPlugin > (3) trac-hacks.org/ticket/12153 > (4) trac-hacks.org/ticket/10092 > (5) trac-hacks.org/ticket/11742 >
