All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] mailinglist write access for non-subscribers
Date: Mon, 8 Feb 2016 13:37:57 +0100	[thread overview]
Message-ID: <20160208123757.GC29803@hermes.click-hack.org> (raw)
In-Reply-To: <56B87392.8040703@web.de>

On Mon, Feb 08, 2016 at 11:53:06AM +0100, Jan Kiszka wrote:
> On 2016-02-08 10:18, Henning Schild wrote:
> > On Mon, 8 Feb 2016 10:07:02 +0100
> > Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:
> > 
> >> On Mon, Feb 08, 2016 at 09:29:41AM +0100, Henning Schild wrote:
> >>> Hey guys,
> >>>
> >>> i have been discussing the huge ioremap problem with the guy that
> >>> wrote the patch-set introducing the problem. And i always had this
> >>> list on CC, unfortunately his replies did not end up on this list
> >>> because he is not subscribed.
> >>>
> >>> Is the list indeed configured like that? And is that not something
> >>> that should be changed?  
> >>
> >> The list is subscriber-only, and this is intentional. It avoids spam.
> > 
> > I personally think an open source community should first care about
> > beeing open and find other ways of dealing with spam, but fair enough.
> 
> FWIW, if we seriously want to work closer with the kernel community,
> this policy should be reconsidered. I know it's additional effort to
> establish some basic spam filters (unless they already exist anyway),
> but there is also quite some value in allowing cross-list postings with
> key communities.

Some kernel mailing lists are "subscriber only" too, probably for
the same reason (the linux arm kernel mailing list for instance).
People have complained about it, but so far it does not seem to be a
problem for the participants to the Linux ARM community.

The spammers know our domain (is there a domain they do not know
anyway), at any time, we have a dozen subscriptions pending with
invalid addresses to lists hosted by xenomai.org. So, if we open the
gates, they are going to use them.

I have no idea how many posts are rejected right now. What we can
propose is to manually moderate the posts by non-subscribers, if
this is too much work, we will revert the change, if it happens that
there is no spam, we will open the list completely.

The xenomai.org domain has some spam filtering already, though I am
not sure the mailing lists do not bypass the spam filtering, before
opening the mailing list, it has to be checked.

Regards.

-- 
					    Gilles.
https://click-hack.org


  reply	other threads:[~2016-02-08 12:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08  8:29 [Xenomai] mailinglist write access for non-subscribers Henning Schild
2016-02-08  9:07 ` Gilles Chanteperdrix
2016-02-08  9:18   ` Henning Schild
2016-02-08 10:53     ` Jan Kiszka
2016-02-08 12:37       ` Gilles Chanteperdrix [this message]
2016-02-08 13:02         ` Henning Schild
2016-02-08 19:55           ` Wolfgang Denk
2016-02-08 21:27             ` Gilles Chanteperdrix
2016-02-09 11:38             ` Henning Schild
2016-02-09 16:30               ` Wolfgang Denk
2016-02-09 19:05                 ` Gilles Chanteperdrix
2016-02-09 21:48                   ` Wolfgang Denk
2016-02-13 18:42                     ` Gilles Chanteperdrix

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=20160208123757.GC29803@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jan.kiszka@web.de \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.