#5411 Fedora notifications sends unwanted emails
Closed: Fixed Opened by jgrulich.

= bug description =
Since yesterday I started receiving all possible email notifications, like from copr, abrt, koji, bugzilla, badges from all Fedora users. That means I received thousands emails I didn't want to receive at all. This is really annoying.


Sorry for the inconvenience that sounds pretty annoying indeed.

To track this down, we will need a little more info, such as one of these emails (including the headers).

Thanks

Screenshot of email headers:
https://jgrulich.fedorapeople.org/fedora-notifications.png

Email:
https://jgrulich.fedorapeople.org/fedora-notifications.txt

Is that what you need?

So, somehow all of the rules in the "Events of packages I own" filter had become non-negated, so the filter that says "related to my user" was set to match for every user except for you.

All filters for reference:
{{{
id | created_on | filter_id | code_path | _arguments | negated
--------+----------------------------+-----------+--------------------------------------+------------------------------+---------
216559 | 2015-08-27 19:41:05.13849 | 24496 | fmn.rules:bodhi_masher_start | {} | t
101622 | 2015-02-12 19:34:06.530516 | 24496 | fmn.rules:koji_instance | {"instance": "ppc,s390,arm"} | t
101623 | 2015-02-12 19:34:06.588636 | 24496 | fmn.rules:copr_build_start | {} | t
101624 | 2015-02-12 19:34:06.649286 | 24496 | fmn.rules:copr_chroot_start | {} | t
101625 | 2015-02-12 19:34:06.708296 | 24496 | fmn.rules:copr_worker_create | {} | t
101626 | 2015-02-12 19:34:06.769273 | 24496 | fmn.rules:koji_scratch_build_started | {} | t
101627 | 2015-02-12 19:34:06.827128 | 24496 | fmn.rules:koji_build_started | {} | t
101628 | 2015-02-12 19:34:06.893411 | 24496 | fmn.rules:koji_rpm_sign | {} | t
101629 | 2015-02-12 19:34:07.067858 | 24496 | fmn.rules:koji_tag | {} | t
101630 | 2015-02-12 19:34:07.257312 | 24496 | fmn.rules:koji_untag | {} | t
101631 | 2015-02-12 19:34:07.315777 | 24496 | fmn.rules:koji_repo_done | {} | t
101632 | 2015-02-12 19:34:07.578045 | 24496 | fmn.rules:koji_repo_init | {} | t
101633 | 2015-02-12 19:34:07.691831 | 24496 | fmn.rules:koji_package_list_change | {} | t
101634 | 2015-02-12 19:34:07.747383 | 24496 | fmn.rules:summershum_catchall | {} | t
184993 | 2015-05-05 20:19:22.734611 | 24496 | fmn.rules:faf_report_threshold1 | {} | t
184994 | 2015-05-05 20:19:23.082674 | 24496 | fmn.rules:faf_problem_threshold1 | {} | t
242759 | 2015-11-16 22:08:07.317643 | 24496 | fmn.rules:mdapi_repo_update | {} | t
101621 | 2015-02-12 19:34:06.474083 | 24496 | fmn.rules:user_filter | {"fasnick": "jgrulich"} | t
101620 | 2015-02-12 19:34:06.413224 | 24496 | fmn.rules:user_package_filter | {"fasnick": "jgrulich"} | t
309483 | 2016-02-18 17:48:32.760373 | 24496 | fmn.rules:taskotron_result_new | {} | t

}}}

I just set the one with id 101620 to non-negated.

I have thought on this when I initially experienced FMN filter list and seen few people facing issues to use that interface. That is why I have rarely touched to my FMN filters. I kept most default settings. I even don't know if such changes trigger some popup message like "you really want to change this field?". If they are not doing then it should be implemented.

Metadata