add "report spam" link to mailing list footers #9629
Labels
No labels
announcement
authentication
automate
aws
backlog
blocked
bodhi
ci
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Initiative Worthy
Closed As
Insufficient data
Closed As
Invalid
Closed As
Spam
Closed As
Upstream
Closed As/Will Not
Can Not fix
cloud
communishift
copr
database
deprecated
dev
discourse
dns
downloads
easyfix
epel
factory2
firmitas
gitlab
greenwave
hardware
help wanted
high-gain
high-trouble
iad2
koji
koschei
lists
low-gain
low-trouble
mbs
medium-gain
medium-trouble
mini-initiative
mirrorlists
monitoring
Needs investigation
notifier
odcs
OpenShift
ops
OSBS
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
rdu-cc
release-monitoring
releng
repoSpanner
request-for-resources
s390x
security
SMTP
src.fp.o
staging
taiga
unfreeze
waiverdb
websites-general
wiki
No milestone
No project
No assignees
6 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/fedora-infrastructure#9629
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe what you would like us to do:
At least the Fedora Users list, and possibly all lists could do with a footer like this:
As a bonus, maybe a new template for mailing list spam reports, and link to that template?
When do you need this to be done by? (YYYY/MM/DD)
Whenever.
Thanks for bringing this up and always being helpful on the ${large_number}'s of lists you're on.
Should we be worried that this could lead to waves of duplicate reports?
For the few spam reports I've filed, I've marked them private so that I can include the full message without worrying that I'm just making the issues page another way for the spammer's message to be seen. If that's something we'd like to encourage, we'd perhaps want to change the footer to point to a documentation page which included the desired steps to take when reporting a message rather than dropping folks directly into the infrastructure issues queue.
Perhaps a better footer would be to point to a page on what to do if you see spam which included "don't reply to it on the list, for any reason :)" and then suggests folks report it to the list owners, who will know if they had already reported the message or not?
I despise spammers and want them addressed quickly and without mercy, but I am concerned that if we push folks to report issues that we could add burden to the already heavy load of the infrastructure team.
(I'm not an active member of the infrstructure team, just a fellow sysadmin and list admin on the users list.)
Currently the mail software is needing a complete revamp which is a delayed initiative. Templates and such would need to be dealt with as part of this initiative
Metadata Update from @humaton:
Actually we already modify this template:
roles/mailman/files/mailman-template-list-member-generic-footer.txt
So, perhaps another line that says: "Do not reply to spam on the list, report it at https://pagure.io/fedora-infrastructure' ?
Sounds good to me.
Pushed. Should be active after the playbook finishes.
Metadata Update from @kevin: