From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: nfs@lists.sourceforge.net
Subject: Re: ADMINSTRIVIA - Intent to open nfs@lists.sourceforge.net to non-subscribers.
Date: Wed, 21 Sep 2005 12:16:47 -0400 [thread overview]
Message-ID: <1127319409.9932.213.camel@pc.local> (raw)
In-Reply-To: <17201.34296.859729.69509@cse.unsw.edu.au>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
On Wed, 2005-09-21 at 18:10 +0200, Neil Brown wrote:
>
> If you have a violent objection to this, please write now.
Not really violent.
> I don't believe a fear of 'SPAM' is a reasonable objection as there
> are plenty of tools available that reduce SPAM substantially.
Indeed, and better done as far upstream as possible. i.e. don't
distribute spam for every recipient to have to deal with. It's better
if the distribution point deals with it.
b.
--
My other computer is your Microsoft Windows server.
Brian J. Murrell
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-21 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 16:10 ADMINSTRIVIA - Intent to open nfs@lists.sourceforge.net to non-subscribers Neil Brown
2005-09-21 16:16 ` Brian J. Murrell [this message]
2005-09-22 8:56 ` H. J. Lu
2005-10-06 13:41 ` J. Bruce Fields
2005-10-06 22:46 ` Neil Brown
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=1127319409.9932.213.camel@pc.local \
--to=brian@interlinx.bc.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.