fedora-infrastructure

#12811 spam on devel list perhaps causing many gmail subscribers to be disabled
Closed: Fixed with Explanation by kevin. Opened by kevin.

Closed: Fixed with Explanation
Reopen Issue

There were 3 spams that posted to the devel list last night somehow, it's not fully clear. They seem to have been doing something clever with bounces and mailer-daemon <> addresses. ;(

I deleted these spams, but quite possibly that caused gmail to start rejecting emails to gmail users with a:

"bounced (host gmail-smtp-in.l.google.com[172.253.62.26] said: 552-5.7.0 This message was blocked because its content presents a potential 552-5.7.0 security issue. To review our message content and attachment content 552-5.7.0 guidelines, go to 552 5.7.0 "

This caused mailman to disable about 340 gmail users on the devel list.

So, things we need to do:

  1. Track down how this spam got through. I have already added some header rules to try and catch it if it happens again, but we should figure out how it even got through to the lists.

  2. Once we are sure gmail is accepting lists.fedoraproject.org emails ok again, we should see if we can re-enable those users who were disabled.

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: Needs investigation, high-trouble, lists, medium-gain

Metadata Update from @kevin:
- Issue assigned to kevin

ok. I am pretty sure the spam was what caused google to reject emails for a time.

I went back and looked at how mailman handles things, and what it will do is if there's a number of bounces they will disable delivery to the user. It will send 3 notices to the user telling them they have been disabled. If those 3 bounce or aren't handled, it will unsubscribe them.

So, the first notices have gone out already I think. Shall we just trust people who wish to keep getting emails will just enable again?
Or should we try and do something to mass re-enable? I worry about any such thing affecting users that deliberately set their delivery to disabled for whatever reason.

Keeping this open for now about that, and also to track down how the spam got to the list.

I will be +1 for trusting people to re-enable it by themselves.

ok then. Lets close this and trust people will re-enable.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)
Metadata

Needs investigation high-trouble lists medium-gain

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.