Currently, there's no way for users to report msg/file instances that
have been misclassified by spambayes. There is a property for it on
file and msg, but no frontend.

Coordinators should be alerted when a msg/file is marked as misclassified, to
allow them to reclassify the msg/file quickly. This can be done with a detector.

David, I hope you won’t mind me adding you to nosy.  What should we do with this problem?  When a message gets misclassified as spam, what is the user to do?

Reclassification requires elevated tracker privileges, for a good reason (can't have spambots reclassifying their own messages :)

If triage people don't have access to this function that should probably be changed.  At that point we could document that the way to request reclassification is to post a new message asking for the reclassification.  Then a triage person can fix it.

(The interface, by the way, is accessed from the 'view' of the message, if you have the appropriate privileges.)

> Reclassification requires elevated tracker privileges, for a good reason
Right.  Is there a list of users with admin rights somewhere?

> If triage people don't have access to this function that should probably be
> changed. [...] (The interface, by the way, is accessed from the 'view' of the
> message, if you have the appropriate privileges
I can’t test right now, I don’t remember the id of my message that was classified as spam.  Will test as soon as possible.

AFAIK reclassification requires "Coordinator" privileges, and there are probably a dozen of coordinators.  I think it would be OK to allow all "Developers" to reclassify messages.

I recently saw a developer asking on #python-dev if someone with enough privileges could reclassify a message, but developers that are not on IRC would have to know who has the privileges and send them a mail (or ask to tracker-discuss or something).

Allowing all developers to reclassify messages sounds good.

The attached patch should enable developers to reclassify spam.
I'm not sure what's the best way to test it though (I would need either a spammy message and a non-coordinator account).

Ezio: I think this is fine (except perhaps that developers may be unaware what exactly the ham/spam classification means). To test it, you'll find plenty messages in the tracker. To change your roles, just use roundup-admin on the command line (I think dropping the coordinator role can actually be done through the UI - regaining would require to log in with the "admin" account, which we don't use in the web interface).

Applied in 5872f58e0e4e.