zsh-workers
 help / color / mirror / code / Atom feed
From: ZyX <kp-pav@yandex.ru>
To: Bart Schaefer <schaefer@brasslantern.com>,
	Zsh Hackers' List <zsh-workers@zsh.org>
Cc: Geoff Wing <mason@primenet.com.au>
Subject: Re: zsh-workers/37266 has a malicious attachment
Date: Tue, 01 Dec 2015 23:33:19 +0300	[thread overview]
Message-ID: <6641449001999@web29j.yandex.ru> (raw)
In-Reply-To: <151201101131.ZM32158@torch.brasslantern.com>

01.12.2015, 21:12, "Bart Schaefer" <schaefer@brasslantern.com>:
> On Dec 1, 12:24pm, Peter Stephenson wrote:
> }
> } ...probably obvious enough to everyone here, but as it got flagged up by
> } our email system I thought it was worth reporting more widely.
> } Subject line is "Your e-ticket #0000228935".
>
> The number of spam/malicious messages making it to the list has been
> slowly creeping up the last several months. We may have to consider
> closing zsh-workers to non-subscribers.
>
> Curiously zsh-users doesn't seem to have the same problem (yet), so if
> we can close -workers while still allowing the cross-posting, we won't
> lose much.
>
> Or maybe non-member posts could require approval, as with -announce.

vim* lists uses google groups and moderation for new members and I almost never see spam there. Most likely though this is the result of the following combination:

1. Google anti-spam algorythms.
2. Requirement to have Google account to become a member (not necessary Google mail though).
3. Denied non-member posting.
4. Presence of pre-moderation for all members that write posts for the first time.

Fourth should be the most effective. I mean, has the least number of false negatives and positives (“positive” is “spam” marker), though only as long as you do not consider denying non-member posts as adding false positives.

>
> --
> Barton E. Schaefer


  reply	other threads:[~2015-12-01 20:44 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 [this message]
2015-12-02  0:21     ` Axel Beckert
2015-12-02  0:35       ` Daniel Shahaf
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=6641449001999@web29j.yandex.ru \
    --to=kp-pav@yandex.ru \
    --cc=mason@primenet.com.au \
    --cc=schaefer@brasslantern.com \
    --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).