#10762 Please remove spam from devel list and block spammer
Closed: Fixed 2 years ago by kevin. Opened 2 years ago by gotmax23.


The emails have multipled! There are now 9 spam emails on devel@ from this sender.

I put the contents of the email in Google Translate it appeared to say "I am a 3464365" in Chinese. This type of content is flooding subscribers of the dev list with no real purpose.

Metadata Update from @smooge:
- Issue assigned to smooge

2 years ago

I am taking this ticket and cleaning.

Banning pkce4jms@bccto.cc globally
Unsubscribing pkce4jms@bccto.cc from fedocal.lists.fedorahosted.org
Unsubscribing pkce4jms@bccto.cc from devel.lists.fedoraproject.org

New address seems to be thsekyxn@bccto.cc . I guess you are aware of that one as well?

bccto.cc seems to be some form of a temporary email service, so it might be better to just blanket-ban the whole domain...

I am trying to do so but the mailman3 admin interface we have is a very old one and the tools available are poor.

Please ban their domain entirely: *@bccto.cc.

All spam that I could get to via app has been deleted from archive. I have put in a block on that domain but there are probably several hundred others they will start using tomorrow. I am turning this over to people who have more time to fix this.

I have put in a block on that domain but there are probably several hundred others they will start using tomorrow.

Some service block registration from any temporary email accounts. I think there is a database or API providing such data. Fedora should also use it.

Could you find out about such services? Or a list which the Fedora regular admins could add?

Metadata Update from @smooge:
- Assignee reset

2 years ago

I am dropping from ticket so CPE people can take it over.

Well, I am not sure there's too much more we can do here.

I did blocklist the spammers domain from today.

I think added checks would take changes upstream in noggin and mailman...

I'll leave this open a bit, but probibly will close it out soon.

Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

2 years ago

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

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog