From: Bart Veer <bartv@redhat.com>
To: overseers@sourceware.cygnus.com
Subject: Re: important people (!) unable to use sourceware
Date: Fri, 10 Mar 2000 03:35:00 -0000 [thread overview]
Message-ID: <200003101135.LAA21051@sheesh.cygnus.co.uk> (raw)
Message-ID: <20000310033500.wcqNelb3NRD7N_m57WzXD2cXDMzDVMH4V9t1ADmbGJg@z> (raw)
In-Reply-To: <20000309183047.A25896@shell17.ba.best.com>
>>>>> "Jason" == Jason Molenda <jason@molenda.com> writes:
<snip>
Jason> The spam blocking is critical for high-visiblity
Jason> large-subscriber mailing lists like cygwin and gcc. Every
Jason> spam note we get on cygwin is a major nuisance, and with
Jason> enough of them, it makes Cygnus look incompetant. Other
Jason> mailing lists with fewer subscribers and lower visibility
Jason> have more flexibility.
As far as the ecos-discuss mailing list is concerned, it would not be
that difficult for spam messages to outnumber the real traffic. I
consider strict spam blocking to be essential, even if inconveniences
some eCos users.
Bart
next prev parent reply other threads:[~2000-03-10 3:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Mark Galassi
2000-03-09 15:27 ` Mark Galassi
2000-12-30 6:08 ` Jason Molenda
2000-03-09 18:31 ` Jason Molenda
2000-12-30 6:08 ` Bart Veer [this message]
2000-03-10 3:35 ` Bart Veer
2000-12-30 6:08 ` Chris Faylor
2000-03-09 20:13 ` Chris Faylor
2000-12-30 6:08 ` Jim Kingdon
2000-03-09 16:13 ` Jim Kingdon
2000-12-30 6:08 ` Bob Manson
2000-03-09 19:35 ` Bob Manson
2000-12-30 6:08 ` Gerald Pfeifer
2000-03-09 15:45 ` Gerald Pfeifer
2000-12-30 6:08 ` Bob Manson
2000-03-09 19:25 ` Bob Manson
2000-12-30 6:08 ` Jason Molenda
2000-03-09 23:32 ` Jason Molenda
2000-12-30 6:08 ` Bob Manson
2000-03-10 14:40 ` Bob Manson
2000-12-30 6:08 ` Jim Kingdon
2000-03-10 7:32 ` Jim Kingdon
2000-12-30 6:08 ` Chris Faylor
2000-03-10 9:27 ` Chris Faylor
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=200003101135.LAA21051@sheesh.cygnus.co.uk \
--to=bartv@redhat.com \
--cc=overseers@sourceware.cygnus.com \
/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 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 read-only IMAP folder(s) and NNTP newsgroup(s).