public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Frank Farance <frank@farance.com>
To: cygwin@cygwin.com
Subject: Re: My delayed complaint about spam on this list
Date: Mon, 04 Jun 2018 20:13:00 -0000	[thread overview]
Message-ID: <38435875-e815-1676-ef42-223f9599ccfa@farance.com> (raw)
In-Reply-To: <6962864c-4426-6a65-e9c5-ec540a2a5738@gmail.com>

On 2018-06-04 15:47, James Darnley wrote:
> 
> It isn't very nice to put "please email cygwin@cygwin.com" in error and warning messages then deny people the opportunity to send the email. "Please register first" is annoying as shit.  I have certainly not reported bugs to lists that make me do that.  The same applies to bug trackers.
> 
> > If you would like to reply to me, please send your response to me directly, DO NOT SEND TO THE LIST.  I will summarize back to the list. (Think: Old-School 1980s USENET unix-wizards kinda framework.)
> 
> No thanks.  I wish to discuss this openly.

James-

First, my offer to have responses sent to me was a courtesy to the list ... some people would prefer to have this kind of Mailing List Mechanics discussion off line.  No problem having it discussed openly, I'm fine with that, too.

Second, as a mailing list admin myself, at some time we're going to have to deal with spam as some of the members E-mail systems will start tagging normal cygwin stuff as spam, which is the kind of stuff members don't have control over in medium-to-large organizations.  Again, I've heard all these *legitimate* concerns over several decades.

Third, I believe a registration mechanism (just your E-mail address) is necessary for discussion: How would you be getting follow-up messages if you're not on the list?  And E-mail clients may prefer Reply-To-List rather than Reply-All, which means even if people were CCing you, at some point you start missing discussion from others.

So given the choice between:

(1) getting rid of spam by restricting senders to members of the list (which, as you state, might lose people like you)

versus

(2) reducing spam for the 1500 members on the list (yet still lose you because you need to become a member of the list to see the responses from others),

THEN: in both cases we still wind up losing you (either you don't give your E-mail address to the list server or you're not included in the follow-up E-mails because you're not a member), ... YET in the latter case we reduce spam ...

THUS, cygwin should restrict sending to just the members because (1) it will reduce spam, and (2) we're still going to lose people like you who don't want to put their name on the list - regardless of which spam reduction mechanisms is chosen.

Make sense?

-FF

-- 
______________________________________________________________________
Frank Farance, Farance Inc.    T: +1 212 486 4700   M: +1 917 751 2900
mailto:frank@farance.com       http://farance.com
Standards/Products/Services for Information/Communication Technologies

--
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

  reply	other threads:[~2018-06-04 20:13 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 [this message]
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
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=38435875-e815-1676-ef42-223f9599ccfa@farance.com \
    --to=frank@farance.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).