From: Borzenkov Andrey <Andrey.Borzenkov@siemens.com>
To: "'Roman Neuhauser'" <neuhauser@bellavista.cz>, zsh-users@sunsite.auc.dk
Subject: RE: viruses (was Re: Meeting notice)
Date: Fri, 1 Nov 2002 16:39:40 +0300 [thread overview]
Message-ID: <6134254DE87BD411908B00A0C99B044F03A0B4D1@MOWD019A> (raw)
In-Reply-To: <20021101131309.GD18364@freepuppy.bellavista.cz>
> # william@hq.newdream.net / 2002-10-31 20:59:36 -0800:
> > Appeal to whomever runs this list....
> >
> > I know this has been hashed out repeatedly in the past, but this is
> > getting ridiculous. While I like this list, the volume of spam /
viruses
> > I get from it exceeds the actual list traffic.
>
> through the list? i filter this list into its mailbox on the
> Delivered-To: header, so anything that goes to the list should end
> up in that mailbox, and i don't remember a single spam or virus
> getting in the folder. I don't use anything like SA, nor any AV,
> just a few maildrop rules... Hm, but they route quite a few emails
> to /dev/null, so that might be it: aol, juno, msn, yahoo, to name
a
> few.
>
Not everybody is using client that allows easy filtering. In any case,
you still have to download message which means extra traffic and often
extra cost.
Unfortunately, zsh workers do not own list server in any way and IIRC
list server maintainers have been quite unresponsive in the past. To
workers: what about relocating lists to sourceforge? To my impression,
lists hosted there do not suffer from spam so much.
-andrey
next prev parent reply other threads:[~2002-11-01 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0H4V009M2HYBNA@mta4.srv.hcvlny.cv.net>
2002-11-01 4:59 ` Will Yardley
2002-11-01 13:13 ` Roman Neuhauser
2002-11-01 13:31 ` Vincent Lefevre
2002-11-01 13:39 ` Borzenkov Andrey [this message]
2002-11-01 17:45 ` Oliver Kiddle
2002-11-01 17:57 ` Clint Adams
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=6134254DE87BD411908B00A0C99B044F03A0B4D1@MOWD019A \
--to=andrey.borzenkov@siemens.com \
--cc=neuhauser@bellavista.cz \
--cc=zsh-users@sunsite.auc.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).