public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: James Darnley <james.darnley@gmail.com>
To: cygwin@cygwin.com
Subject: Re: My delayed complaint about spam on this list
Date: Mon, 04 Jun 2018 19:47:00 -0000	[thread overview]
Message-ID: <6962864c-4426-6a65-e9c5-ec540a2a5738@gmail.com> (raw)
In-Reply-To: <cbba9e63-da57-a38c-f1bb-874e478a40f7@farance.com>


[-- Attachment #1.1: Type: text/plain, Size: 1435 bytes --]

On 2018-06-04 21:30, Frank Farance wrote:
> Hi, I enjoy reading the cygwin E-mails, one of the few E-mail lists I
> regularly follow.  And I've administered multiple E-mail lists over
> two-plus decades.
> 
> I've seen a bunch of spam, and it's continued for a while (beyond my
> expectation that it would have already ended).  This kinda spam is
> typically solved by having the E-mail list restricted: only members can
> submit to the list.  Maybe this has been done already ... but if not,
> please enable this mailing list feature.  Now if those members start
> submitting spam, then you can give them warnings and (ultimately) they
> can lose their membership.  And if people start forging E-mail
> addresses, you can turn on various SPF-like features to make sure the
> E-mail is coming from a that source (or an equivalent feature might work
> well, too).

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.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 603 bytes --]

  reply	other threads:[~2018-06-04 19:47 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 [this message]
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
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=6962864c-4426-6a65-e9c5-ec540a2a5738@gmail.com \
    --to=james.darnley@gmail.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).