summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMartin Pool <mbp@samba.org>2003-02-19 00:47:41 +0000
committerMartin Pool <mbp@samba.org>2003-02-19 00:47:41 +0000
commitf5cc7f35e9b8feed0f274affc46fcc65f2e77466 (patch)
tree1253f28e06361f8c97703bf356eff703281f6873
parenta0913929ef6f1e34ff2654e8773c8bf45c6230af (diff)
downloadsamba-f5cc7f35e9b8feed0f274affc46fcc65f2e77466.tar.gz
samba-f5cc7f35e9b8feed0f274affc46fcc65f2e77466.tar.bz2
samba-f5cc7f35e9b8feed0f274affc46fcc65f2e77466.zip
Remove old listproc address; update instructions for subscribing to
the mailing list. (This used to be commit cab94c8a315ba7ad68e71c62c0d5fa3ab9a90661)
-rw-r--r--README60
1 files changed, 52 insertions, 8 deletions
diff --git a/README b/README
index b4bd9a0f57..cdc7e9e2a9 100644
--- a/README
+++ b/README
@@ -135,19 +135,63 @@ http://lists.samba.org/
MAILING LIST
------------
-There is a mailing list for discussion of Samba. To subscribe send
-mail to listproc@samba.org with a body of "subscribe samba Your Name"
-Please do NOT send this request to the list alias instead.
+Please do NOT send subscription/unsubscription requests to the lists!
-To send mail to everyone on the list mail to samba@listproc.anu.edu.au
+There is a mailing list for discussion of Samba. For details go to
+<http://lists.samba.org/> or send mail to <samba-subscribe@lists.samba.org>
There is also an announcement mailing list where new versions are
-announced. To subscribe send mail to listproc@samba.org with a
-body of "subscribe samba-announce Your Name". All announcements also
-go to the samba list.
+announced. To subscribe go to <http://lists.samba.org/> or send mail
+to <samba-announce-subscribe@lists.samba.org>. All announcements also
+go to the samba list, so you only need to be on one.
For details of other Samba mailing lists and for access to archives, see
-http://lists.samba.org/
+<http://lists.samba.org/>
+
+
+MAILING LIST ETIQUETTE
+----------------------
+
+A few tips when submitting to this or any mailing list.
+
+1. Make your subject short and descriptive. Avoid the words "help" or
+ "Samba" in the subject. The readers of this list already know that
+ a) you need help, and b) you are writing about samba (of course,
+ you may need to distinguish between Samba PDC and other file
+ sharing software). Avoid phrases such as "what is" and "how do
+ i". Some good subject lines might look like "Slow response with
+ Excel files" or "Migrating from Samba PDC to NT PDC".
+
+2. If you include the original message in your reply, trim it so that
+ only the relevant lines, enough to establish context, are
+ included. Chances are (since this is a mailing list) we've already
+ read the original message.
+
+3. Trim irrelevant headers from the original message in your
+ reply. All we need to see is a) From, b) Date, and c) Subject. We
+ don't even really need the Subject, if you haven't changed
+ it. Better yet is to just preface the original message with "On
+ [date] [someone] wrote:".
+
+4. Please don't reply to or argue about spam, spam filters or viruses
+ on any Samba lists. We do have a spam filtering system that is
+ working quite well thank you very much but occasionally unwanted
+ messages slip through. Deal with it.
+
+5. Never say "Me too." It doesn't help anyone solve the
+ problem. Instead, if you ARE having the same problem, give more
+ information. Have you seen something that the other writer hasn't
+ mentioned, which may be helpful?
+
+6. If you ask about a problem, then come up with the solution on your
+ own or through another source, by all means post it. Someone else
+ may have the same problem and is waiting for an answer, but never
+ hears of it.
+
+7. Give as much *relevant* information as possible such as Samba
+ release number, OS, kernel version, etc...
+
+8. RTFM. Google. groups.google.com.
NEWS GROUP