Status (by robm at Fri Sep 19 07:37 UTC)
Due to a bug in some newly deployed code, some users were having problems reporting spam/non-spam for about 8 hours.
Any messages reported would have been correctly learned to the users personal spam/non-spam database, but after that a timeout would have occured causing an error reponse screen.
The bug would have affected people reporting spam/non-spam who had not already reporting 200 spam and 200 non-spam messages previously. You can see how many messages you’ve reported as spam/non-spam on the Options -> Spam/Virus Protection screen.
The bug has been fixed.
