From: James Pearson <james-p@moving-picture.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Spam in the NFS list
Date: Tue, 13 May 2003 15:44:48 +0100 [thread overview]
Message-ID: <3EC104E0.C869CB23@moving-picture.com> (raw)
In-Reply-To: 1052835763.14888.33.camel@comp6161.potsdam.edu
Does anyone on this list object to the list becoming closed?
James Pearson
Matthew Keller wrote:
>
> Generally, open source development lists stay open- Especially Source
> Forge lists. I'm the "list mom" for a couple, and anytime I bring up the
> idea of closing the list I get a barrage of "I don't want to subscribe
> to the evil/facist SourceForge service". This is, of course, moot for
> most people, and *I* prefer closed lists, but there are all sorts of
> people out there. Just something to think about.
>
> On Tue, 2003-05-13 at 09:44, Jake Gold wrote:
> > Is there any reason for leaving the list open to email from non-subscribed users?
> >
> > Most of the technical lists that I'm on have adopted a subscriber-only email policy with little resistance from their members...
> >
> > (This is assuming these spammers aren't subscribing and then sending mail. Which, I'd guess, is rather unlikely...)
>
> --
> Matthew Keller
> Enterprise Systems Analyst
> Computing & Technology Services
> State University of New York @ Potsdam
> Potsdam, NY USA
> http://mattwork.potsdam.edu/
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-05-13 14:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 10:43 Spam in the NFS list James Pearson
2003-05-13 12:18 ` Matthew Keller
2003-05-13 13:44 ` Jake Gold
2003-05-13 14:22 ` Matthew Keller
2003-05-13 14:44 ` James Pearson [this message]
2003-05-13 14:33 ` H. J. Lu
2003-05-13 23:22 ` Neil Brown
2003-05-13 14:48 ` Bogdan Costescu
2003-05-13 16:03 ` Bryan O'Sullivan
2003-05-13 16:45 ` Andreas Metzler
2003-05-13 17:16 ` Bogdan Costescu
2003-05-14 10:17 ` Philippe Gramoullé
2003-05-13 22:39 ` Steven N. Hirsch
2003-05-13 23:36 ` Neil Brown
2003-05-14 10:05 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 15:45 Jose Santiago
[not found] <E19Fb4m-0001Wq-00@sc8-sf-list2.sourceforge.net>
2003-05-13 15:48 ` Klaus Steinberger
2003-05-13 17:12 ` Santiago Flores
2003-05-14 14:53 Lever, Charles
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=3EC104E0.C869CB23@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=nfs@lists.sourceforge.net \
/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