zsh-users
 help / color / mirror / code / Atom feed
From: Borzenkov Andrey <Andrey.Borzenkov@siemens.com>
To: "'Karsten Thygesen'" <karthy@karthy.net>,
	"'Roman Neuhauser'" <neuhauser@bellavista.cz>
Cc: "'zsh users'" <zsh-users@sunsite.dk>, staff@sunsite.dk
Subject: RE: qconfirm in front of zsh-users@
Date: Fri, 31 Jan 2003 09:40:24 +0300	[thread overview]
Message-ID: <6134254DE87BD411908B00A0C99B044F03A0B62C@mowd019a.mow.siemens.ru> (raw)
In-Reply-To: <86hec1hwo2.fsf@karthy.karthy.net>


> 
>  Roman>     1) zsh-users@ (that's what we specifically talked about,
>  Roman> could cover -workers@ if needed) will be protected by
>  Roman> qconfirm, which means that non-subscribers will be required to
>  Roman> confirm their posts.
> 
> Is that really required based on traffic since saturday? Last
> saturday, we installed Messagewall for all sunsite mails, so the
> spam/vira level should have dropped to a pretty low level. So is the
> request still valid? Have you seen a lot spam since saturday?
> 

the spam volume has decreased but it is still there. Lists known to me that
do use confirmation do not have spam at all. Some other high-volume lists
(lkml as the very good example) have much better signal to noise ratio
comparing with zsh lists.

-andrey


  parent reply	other threads:[~2003-01-31  7:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-21 15:24 Roman Neuhauser
2003-01-21 15:52 ` Borzenkov Andrey
2003-01-21 16:00 ` Peter Stephenson
2003-01-21 17:25   ` Oliver Kiddle
2003-01-21 17:44   ` Paul Lew
2003-01-22  6:28     ` Borzenkov Andrey
2003-01-22  7:16       ` Paul Lew
2003-01-22 11:55         ` Cosmo
2003-01-22  7:46       ` Will Yardley
2003-01-22 13:13       ` Roman Neuhauser
2003-01-22 18:22 ` Karsten Thygesen
2003-01-23  1:41   ` Mads Martin Joergensen
2003-01-31  6:40   ` Borzenkov Andrey [this message]
2003-01-31 11:49     ` 'Roman Neuhauser'
2003-01-31 15:33       ` Cosmo

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=6134254DE87BD411908B00A0C99B044F03A0B62C@mowd019a.mow.siemens.ru \
    --to=andrey.borzenkov@siemens.com \
    --cc=karthy@karthy.net \
    --cc=neuhauser@bellavista.cz \
    --cc=staff@sunsite.dk \
    --cc=zsh-users@sunsite.dk \
    /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).