[Tracker-discuss] On spammish submissions

[Paul Dubois]

For my 2 cents worth, preventing registration (even including a manual
review) is a much narrower job with less activity. Manual screening of
submissions is not practical.

One should also add defenses on the mailing lists that are the TARGET
of the mail from the tracker, since they need those anyway
irregardless of the tracker.

On 3/21/07, "Martin v. Löwis" <martin at v.loewis.de> wrote:
> > The same basic approach would work here.  Admins would get emails for
> > anything above the "okay" threshold and could decide what, if anything,
> > needed doing.  In the Admin menu you might have "Edit Spam", "Edit Ham" and
> > "Retrain" items.  If necessary you'd add the questionable input to the spam
> > or ham data and poke the retrain button.
>
> I'm somewhat skeptical that an approach involving manual review by
> administrators could work. I'd rather find a means to not let spambots
> register in the first place.
>
> OTOH, allowing issue submission to proceed, but adding a SPAM button
> (accessible to developers) might work. This button would expire the
> issue, disable the poster's account, and add the data to the spam
> database. However, I would hope it would rarely happen if we
> can manage to not let spambots register in the first place. So it
> might be a lot of effort for little gain (OTOH, it might also be
> useful to other roundup installations if sufficiently generalized).
>
> Regards,
> Martin
>
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>