Closed Bug 352156 Opened 18 years ago Closed 18 years ago

legal@lists.mozilla.org: please bounce all messages from non-subscribers

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gerv, Assigned: justdave)

Details

Please change the legal@lists.mozilla.org mailing list to bounce all messages from non-subscribers, instead of holding them for moderation.

I've spend the past two months being regularly spammed by mailman, telling me to visit the moderation queue. When I do, I have to read the summaries of 70 bits of spam (in a really bad interface) and then discard them all. There has not been one instance of a non-subscriber posting a valid message.

A computer can do this job much better than me. Please ask one to do so :-)

Gerv
Uh, the "mozilla.legal" newsgroup (which is tied directly to legal@lists.mozilla.org) is mentioned in a ton of places. If the mailing list is restricted to subscribers-only, what happens to all the people that post via the newsgroup on Google Groups? I know I have posted via Google Groups to mozilla.legal before...
I don't believe Google Groups uses the mailing list mechanism in order to post to mozilla.legal. What makes you think it does?

Gerv
There's an option in the admin panel, that might be what you want.
Go to <https://lists.mozilla.org/admin/legal/?VARHELP=privacy/sender/generic_nonmember_action>.
If you set it to "Discard", that should prevent the flood of approval requests. Technically, I don't think it's a bounce, but it should accomplish what you want.
there's a reject option, too, I think you'd rather that if you want people to actually know that their message didn't get posted.
Assignee: server-ops → justdave
I'm not sure why I couldn't find the admin interface when I looked; but thanks, that'll do it. :-) I've selected "Reject", as recommended.

Gerv
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.