public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jeffrey Altman <jaltman@secure-endpoints.com>
To: cygwin@cygwin.com
Subject: Re: My delayed complaint about spam on this list
Date: Mon, 04 Jun 2018 20:27:00 -0000	[thread overview]
Message-ID: <105651ef-fd15-5c6b-45f7-ede8c23a0ca2@secure-endpoints.com> (raw)
In-Reply-To: <38435875-e815-1676-ef42-223f9599ccfa@farance.com>

[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]

On 6/4/2018 4:13 PM, Frank Farance wrote:
> 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.  

My mail servers regularly categorize cygwin at cygwin.com mail as spam.

And then there is all of the mail that simply gets rejected because of
DMARC policies applied by the sender's domain.

> (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),

There are other alternatives.

I'm a member of a few mailing lists that accept e-mails from non-list
members but only after the non-list member successfully accesses a URL
that is mailed to the sender's address.

Would something like that be possible for the cygwin lists?

Jeffrey Altman



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4080 bytes --]

  reply	other threads:[~2018-06-04 20:27 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 [this message]
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=105651ef-fd15-5c6b-45f7-ede8c23a0ca2@secure-endpoints.com \
    --to=jaltman@secure-endpoints.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).