From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Allowing posts to cluster-devel@ from non-subscribers
Date: Fri, 28 Jul 2017 14:47:58 +0100 [thread overview]
Message-ID: <f1c742c7-41fd-e729-8f5f-ea0f408b1cbe@redhat.com> (raw)
In-Reply-To: <89173da6-1880-d363-9cdc-97b426ed6cf4@redhat.com>
On 27/07/17 10:20, Andrew Price wrote:
> Are there any strong objections to $subject? If not I'll go ahead and
> flip the switch.
Alasdair has voiced concerns about spam off-list which I think are
valid. We don't really want spam hitting the archives as it's difficult
to remove once it's there, and propagating spam can affect how filters
treat cluster-devel traffic as a whole.
He has also added some spam filtering rules to the list configuration
that will hopefully reduce the moderation burden. I will consider how
well they work after some time has passed and review whether it makes
sense to open the list up on that basis. If not then we should try to
get some moderators in different time zones to minimise the time
messages spend in the hold queue.
Cheers,
Andy
prev parent reply other threads:[~2017-07-28 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 9:20 [Cluster-devel] Allowing posts to cluster-devel@ from non-subscribers Andrew Price
2017-07-27 9:23 ` Steven Whitehouse
2017-07-28 13:47 ` Andrew Price [this message]
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=f1c742c7-41fd-e729-8f5f-ea0f408b1cbe@redhat.com \
--to=anprice@redhat.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 NNTP newsgroup(s).