supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Laurent Bercot <ska-supervision@skarnet.org>
To: supervision@list.skarnet.org
Subject: Re: Hassle with 'subscribers only' policy
Date: Sat, 27 Sep 2008 17:10:28 +0200	[thread overview]
Message-ID: <20080927151028.GA17003@skarnet.org> (raw)
In-Reply-To: <loom.20080926T084407-428@post.gmane.org>

> Hi, I personally really dislike this 'subscribers only' post policy.  For
> mailing list subscriptions, I use different (private) mail addresses than those
> I use for posting.  When sending mail, I use different addresses in the envelope
> and the header's From:.  With the current 'subscribers only' policy, I have to
> go through several steps to finally have a mail posted to this list, this one
> now goes through gmane.  I was very pleased with the confirmation requests sent
> to the envelope sender, this was just a single easy extra step, and the message
> was done.
> 
> Furthermore, this mailing list is mentioned on the runit web page as contact
> address for contributed run scripts.  I received a complaint, and support it,
> that contributing is made rather difficult, because it's that hard to get the
> mail delivered, the contributor finally gave up.

 I totally understand, and agree with the fact the 'subscribers only'
policy is a hassle.
 However, as you surely have noticed, this policy, coupled with subscription
moderation, has totally eliminated spam.
 Beforehand, the mailing-list was horrendously plagued with spam, to the
point that several users complained, and talked me into changing the policy.
You can even find the relevant posts in the mailing-list archives.

 Confirmation requests sent to the envelope sender for every message
doesn't work reliably enough anymore. Some robots are intelligent enough
now to detect confirmation requests and reply to them; confirmation
requests may reduce list spam, but do not eliminate it, far from it.

 It's really a choice between user convenience and security - as is the
case with most systemm administration stuff.
 I don't want to change the policy every few months because people
complain. If I listen to you and change it back to non-subscribers-only,
we'll get spam again, and subscribers will protest. I don't think there's
a solution that makes everyone happy, as long as IM2000 isn't out.

 Of course, your opinion weighs a lot, since you're the runit author
and people mostly use this list to talk about runit; but still, I'm
inclined to keep things the way they are now - else it will be a
neverending back-and-forth movement.

 What do the users hate less? Spam, or lack of convenience ?

-- 
 Laurent


      reply	other threads:[~2008-09-27 15:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26  8:52 Gerrit Pape
2008-09-27 15:10 ` Laurent Bercot [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=20080927151028.GA17003@skarnet.org \
    --to=ska-supervision@skarnet.org \
    --cc=supervision@list.skarnet.org \
    /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).