From: James Colannino <lkml@colannino.org>
To: linux-kernel@vger.kernel.org
Subject: Spam on the list
Date: Thu, 14 Oct 2004 08:51:10 -0700 [thread overview]
Message-ID: <416EA06E.3050608@colannino.org> (raw)
I was just thinking that the list receives a lot of spam. Shouldn't the
list be locked down to be posted to by subsribers only as to curb the
bulk of that spam? That's how most mailing lists I'm on are and it
works well. Please don't flame me for this... :) Just thought I'd
mention it.
James
--
My blog: http://www.crazydrclaw.com/
My homepage: http://james.colannino.org/
"You can only find truth with logic if you have already found truth without it." --G. K. Chesterton
next reply other threads:[~2004-10-14 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 15:51 James Colannino [this message]
2004-10-14 16:03 ` Spam on the list Ken Brush
2004-10-14 16:03 ` Richard B. Johnson
2004-10-14 18:41 ` Norbert van Nobelen
2004-10-14 20:58 ` Lee Revell
2004-10-14 21:25 ` Rafael J. Wysocki
2004-10-14 22:40 ` 2.8.6.1 deadlock and ext3/i2o corruption (Was: Spam on the list) Nate Riffe
2004-10-14 16:05 ` Spam on the list Jesper Juhl
2004-10-14 17:04 ` Ben Pfaff
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=416EA06E.3050608@colannino.org \
--to=lkml@colannino.org \
--cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox