On 04/05/2017 11:06 AM, Dusty Mabe wrote:
Adding in fedora-devel
On 04/05/2017 10:23 AM, Dusty Mabe wrote:
I've identified that we have not been getting notifications from pagure for the past few days. I'm working with pingou to resolve this.
We were not getting pagure notifications to our cloud mailing list.
It turns out this is related to a global "ban rule" on our mailing lists that matches ^.*+.*\d{3,}@ against address or messageID.
One example message id from a message that was discarded is: DISCARD: <atomic-wg-ticket-0f65eb6b28c3467abb6d6e478d8f8e58-435261@pagure rule_hits': ['banned-address']
Most emails get through because they don't contain 3 consecutive digits, but some get banned because they do. This means we have been missing some notifications randomly over time. For this list we just happened to have been unlucky enough over the past few days for it to happen to us many times and for us to notice.
Patrick is tracking this down now.
Patrick is done with his investigation/fix:
The summary is that some of the Pagure reply-to headers were matching an antispam filter that was added to a limited set of lists. Patrick has put in a fix and all email notifications from pagure should now all be making it to the lists.
Dusty