From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: My delayed complaint about spam on this list
Date: Wed, 06 Jun 2018 11:42:00 -0000 [thread overview]
Message-ID: <5bc6bbe4-ca9d-053b-6ef3-02b12d7d643e@redhat.com> (raw)
In-Reply-To: <dc60851c-b32c-cf6f-6ae0-0bbadf430818@farance.com>
On 06/05/2018 07:18 PM, Frank Farance wrote:
> Someone suggested a moderator (or multiple moderators) that would
> approve messages from outsiders. That sounds like the easiest approach
> because it anyone can write to the list and there would be just a short
> delay for those people who aren't subscribers, but the main benefit
> would be the lack of spam.
The GNU mailing lists use a mailman instance, and many of them are set
up to use a spam filter front end coupled with a human moderator that
must whitelist ALL first-time posters (whether or not the poster is
subscribed; subscription is not a prerequisite), and I help moderate
some of those lists. Once you've been whitelisted, further messages from
you have no delay unless they are overlarge or trigger the spam filter.
Cygwin lists are hosted by ezmlm-idx, not mailman, so I'm not sure what
knobs it has, and whether those knobs are similar to what mailman
provides. So I'm not even sure if it is technically possible to make a
change to a moderator queue. But as long as we're requesting changes,
I'd ALSO like to get rid of the reply-to munging, as reply-to-all is the
only sane policy for a list that allows posts from non-subscribers
(that's another topic that has been frequently posted on this list).
HOWEVER, per https://sourceware.org/lists.html#faq, this list is run by
sourceware.org overseers, and they don't read THIS list, so complaining
HERE won't make a single difference. If you want a new list policy, you
must first contact overseers and convince them to make the change.
>
> So here's my question (and it assumes that there would be volunteer(s)
> to moderate):
Since I already moderate various GNU lists, adding a Cygwin moderation
queue to my plate is no big deal, so I'd volunteer (provided that the
technology for moderating can be managed completely by email, rather
than requiring me to periodically visit a webpage without an email
reminder).
>
> Question: "Would a moderation system work where subscribers could send
> messages directly, but non-subscribers would need a moderator to approve
> the message?"
Even if the overseers can't turn on human moderation, they are also the
right people to complain to about spam blocking not being effective enough.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-06-06 11:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 16:24 Confirm your subscription Kunal Ghosh
2018-06-04 19:31 ` My delayed complaint about spam on this list Frank Farance
2018-06-04 19:47 ` James Darnley
2018-06-04 20:13 ` Frank Farance
2018-06-04 20:27 ` Jeffrey Altman
2018-06-04 21:55 ` Duncan Roe
2018-06-05 12:26 ` cyg Simple
2018-06-05 17:38 ` Erik Soderquist
2018-06-06 0:04 ` Steven Penny
2018-06-06 0:18 ` Frank Farance
2018-06-06 1:01 ` Steven Penny
2018-06-06 15:50 ` Andrey Repin
2018-06-06 11:42 ` Eric Blake [this message]
2018-06-04 20:21 ` Vince Rice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5bc6bbe4-ca9d-053b-6ef3-02b12d7d643e@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).