Activity log for bug #114820

Date Who What changed Old value New value Message
2007-05-15 14:39:12 Björn Tillenius bug added bug
2007-05-15 14:40:18 Björn Tillenius malone: status Unconfirmed Confirmed
2007-05-15 14:40:18 Björn Tillenius malone: importance Undecided High
2007-05-15 14:40:18 Björn Tillenius malone: statusexplanation Setting to high, since even though this has happened only once, people get upset when they get spammed like this.
2007-05-15 14:40:18 Björn Tillenius malone: assignee bjornt
2007-05-15 14:40:50 Björn Tillenius bug assigned to launchpad-answers (upstream)
2007-05-15 14:41:52 Björn Tillenius launchpad-answers: status Unconfirmed Confirmed
2007-05-15 14:41:52 Björn Tillenius launchpad-answers: importance Undecided High
2007-05-15 14:41:52 Björn Tillenius launchpad-answers: statusexplanation This bug affects the answer tracker as well.
2007-05-24 15:33:01 Francis J. Lacoste launchpad-answers: importance High Medium
2007-05-24 15:33:01 Francis J. Lacoste launchpad-answers: statusexplanation This bug affects the answer tracker as well.
2009-02-02 22:05:55 Diogo Matsubara bug added subscriber Rodney Dawes
2009-05-16 02:25:29 Curtis Hovey launchpad-answers: importance Medium Low
2009-09-08 07:03:37 Björn Tillenius malone: assignee Björn Tillenius (bjornt)
2010-12-05 05:15:02 Curtis Hovey tags email
2011-12-19 09:11:44 Robert Collins description At the moment, it's possible for a bug to be flooded by bug comments, if an (ill-behaving) autoresponder is subscribed to a bug. This happened on bug 74252, and even though we'll fix so that we'll drop that kind of comments, this could happen again. If something like that happens, it requires an admin to be alerted so that he can fix it, and it's not trivial to fix since there's no way of unsubscribing someone from a bug (using the web ui). We should have some kind of limit, per bug and day, so that you can only post a certain number of comments to a bug (via e-mail), after that you get unsubscribed. One option is to have limit of comments per day, but that might punish legit users (for example, if there's a busy discussion on the bug. Another solution would be to limit the number of consecutive comments on a bug, so that you can only post X number of comments in a row. At the moment, it's possible for a bug to be flooded by bug comments, if an (ill-behaving) autoresponder is subscribed to a bug. This happened on bug 74252, and even though we'll fix so that we'll drop that kind of comments, this could happen again. If something like that happens, it requires an admin to be alerted so that he can fix it. We should detect and prevent this automatically. One approach would be to have some kind of limit, per bug and day, so that you can only post a certain number of comments to a bug (via e-mail), after that you get blocked/unsubscribed. One option is to have limit of comments per day, but that might punish legit users (for example, if there's a busy discussion on the bug. Another solution would be to limit the number of consecutive comments on a bug, so that you can only post X number of comments in a row. Another would be to detect replies that are identical / near identical and collapse or filter them.
2011-12-31 19:52:19 Robert Collins visibility private public
2011-12-31 20:23:12 Robert Collins tags email lp-answers lp-bugs email lp-answers lp-bugs notifications
2012-01-05 03:03:09 Robert Collins summary Stop e-mail floods automatically email floods (e.g. from broken NDR's, holiday bots, or just escalating flame wars) require admin intervention to halt/fix
2012-01-05 03:24:00 Robert Collins removed subscriber Launchpad Security
2018-09-24 12:54:56 Marcelo Atie removed subscriber Marcelo Atie