[wp-meta] [Making WordPress.org] #5534: Add limits to prevent high-triggering notifications

Making WordPress.org noreply at wordpress.org
Wed Dec 9 05:52:47 UTC 2020

#5534: Add limits to prevent high-triggering notifications
 Reporter:  dd32     |      Owner:  (none)
     Type:  defect   |     Status:  new
 Priority:  high     |  Milestone:
Component:  General  |   Keywords:
 Currently WordPress.org notifications accept whatever is given to it, but
 that can cause notifications which trigger on most support threads.

 For example, there's a user with a matcher for 'WordPress', and two for
 other common terms such as 'Help', 'Login', 'Music', 'Google', '404',

 In addition to those, it's also not uncommon for spam accounts (and
 pentesters alike) to inject spam notifications whilst looking for forms on
 WordPress.org that will accept their input.

 The ultimate result of these is that WordPress.org sends far more emails
 than it should, which causes processing delays on every new support reply,
 and causes more people to mark WordPress.org emails as spam / unsolicited
 which affects our ability for legitimate emails to be received.

 There's two options I can think of to help out here:
  1. Require an email confirmation before enabling a notification
  2. Disable notifications which trigger too often, ie. If it exceeds 10
 per day, disable it.

Ticket URL: <https://meta.trac.wordpress.org/ticket/5534>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list