zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: zsh-workers/37266 has a malicious attachment
Date: Wed, 2 Dec 2015 00:35:18 +0000	[thread overview]
Message-ID: <20151202003518.GD2462@tarsus.local2> (raw)
In-Reply-To: <20151202002119.GI6644@sym.noone.org>

Axel Beckert wrote on Wed, Dec 02, 2015 at 01:21:20 +0100:
> On Tue, Dec 01, 2015 at 11:33:19PM +0300, ZyX wrote:
> > 01.12.2015, 21:12, "Bart Schaefer" <schaefer@brasslantern.com>:
> > > On Dec 1, 12:24pm, Peter Stephenson wrote:
> > > Or maybe non-member posts could require approval, as with
> > > -announce.
> 
> That's much better.
> 

Apache lists permit posts by non-subscribers but require the first post
by a non-subscribed address to be manually approved.  (Subsequent posts
do not require approval.)  I think I only ever saw one false negative
there.  The only effect to posters is a delay the first time they post.

They implement that policy through 'ezmlm-make -+ -m -u'.

> > vim* lists uses google groups and moderation for new members and I
> > almost never see spam there.
> 
> Nevertheless using Google Groups as a mailing list has tons of other
> issues. IMHO it's by far not worth to drop a proper and working ML for
> crappy Google Groups. And you don't know how long they will exist.
> Just think about Google Wave, Google Reader and all the other nice
> services they already closed down.
> 
> Besides the nice X-Seq feature is surely not available on Google
> Groups.
> 

+1


  reply	other threads:[~2015-12-02  0:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 12:24 Peter Stephenson
2015-12-01 13:13 ` Markus Trippelsdorf
2015-12-01 18:11 ` Bart Schaefer
2015-12-01 20:33   ` ZyX
2015-12-02  0:21     ` Axel Beckert
2015-12-02  0:35       ` Daniel Shahaf [this message]
2015-12-03 11:38         ` Vincent Lefevre

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=20151202003518.GD2462@tarsus.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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