From 9340a00473f9d24701d7e14fd91c53c88afed281 Mon Sep 17 00:00:00 2001 From: "Mark D. Studebaker" Date: Mon, 17 Feb 2003 01:58:10 +0000 Subject: [PATCH] add Phil's note about spam blocking to the FAQ so we don't lose it. git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@1713 7894878c-1315-0410-8ee3-d5d059ff63e0 --- doc/FAQ | 14 ++++++++++++++ doc/lm_sensors-FAQ.html | 21 +++++++++++++++++++++ doc/lm_sensors-FAQ.texi | 17 ++++++++++++++++- 3 files changed, 51 insertions(+), 1 deletion(-) diff --git a/doc/FAQ b/doc/FAQ index 8c11f29f..221999a9 100644 --- a/doc/FAQ +++ b/doc/FAQ @@ -133,6 +133,7 @@ lm_sensors 6.5 How to access mailing list archives 6.6 How to submit a patch 6.7 How to REALLY help + 6.8 How to block spam on the project mailing list 7 Version 1 Specific Questions 7.1 My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it. What's wrong? @@ -1371,6 +1372,19 @@ Send us the patch in an email and tell us what it does. Send us email if you can help. No experience necessary :) +6.8 How to block spam on the project mailing list +================================================= + + Sorry, we know the spam is a hassle. It would be nice to have a +moderator who can screen everything, but that takes too much time and +delays emails. Right now there is a procmail script which tags likely +spam and puts in a X-SBClass: header. If it is followed by 'Spam', then +it is almost certainly spam, if it is followed by 'Blocked', then it +scores high as being potential spam. You should be able to set some +rules in your mail client to throw those emails into a seperate folder. +It's not bullet proof (some legit mails get tagged wrong, and vice +versa), but it seems to be about 95% accurate in our experience. + 7 Version 1 Specific Questions ****************************** diff --git a/doc/lm_sensors-FAQ.html b/doc/lm_sensors-FAQ.html index de60a0eb..5e1d8e9a 100644 --- a/doc/lm_sensors-FAQ.html +++ b/doc/lm_sensors-FAQ.html @@ -176,6 +176,7 @@ and
  • 6.5 How to access mailing list archives
  • 6.6 How to submit a patch
  • 6.7 How to REALLY help +
  • 6.8 How to block spam on the project mailing list
  • 7 Version 1 Specific Questions @@ -1798,6 +1799,7 @@ Up:Top
  • Section 6.5: How to access mailing list archives
  • Section 6.6: How to submit a patch
  • Section 6.7: How to REALLY help +
  • Section 6.8: How to block spam on the project mailing list

    @@ -1877,6 +1879,7 @@ directory, and make your changes. Generate the diff with

    Node:Section 6.7, +Next:, Previous:Section 6.6, Up:Contribute
    @@ -1895,6 +1898,24 @@ Up:Contribute

    Send us email sensors@stimpy.netroedge.com if you can help. No experience necessary :) +

    +Node:Section 6.8, +Previous:Section 6.7, +Up:Contribute +
    + +

    6.8 How to block spam on the project mailing list

    + +

    Sorry, we know the spam is a hassle. It would be nice to have a +moderator who can screen everything, but that takes too much time and +delays emails. Right now there is a procmail script which tags likely +spam and puts in a X-SBClass: header. If it is followed by 'Spam', then +it is almost certainly spam, if it is followed by 'Blocked', then it +scores high as being potential spam. You should be able to set some +rules in your mail client to throw those emails into a seperate folder. +It's not bullet proof (some legit mails get tagged wrong, and vice +versa), but it seems to be about 95% accurate in our experience. +

    Node:Version 1 Specifics, Next:, diff --git a/doc/lm_sensors-FAQ.texi b/doc/lm_sensors-FAQ.texi index 30ac572f..2b82b93f 100644 --- a/doc/lm_sensors-FAQ.texi +++ b/doc/lm_sensors-FAQ.texi @@ -1338,6 +1338,7 @@ and reference your ticket number in the subject. * Section 6.5:: How to access mailing list archives * Section 6.6:: How to submit a patch * Section 6.7:: How to REALLY help +* Section 6.8:: How to block spam on the project mailing list @end menu @@ -1385,7 +1386,7 @@ directory, and make your changes. Generate the diff with @command{diff -u2 -r DIR1 DIR2}. Or you can generate the diff in CVS with @command{cvs diff -u2}. Send us the patch in an email and tell us what it does. -@node Section 6.7, , Section 6.6, Contribute +@node Section 6.7, Section 6.8, Section 6.6, Contribute @section How to REALLY help Believe it or not, what we really need help with are: @@ -1401,6 +1402,20 @@ Send us email @email{sensors@@stimpy.netroedge.com} if you can help. No experience necessary :) +@node Section 6.8, , Section 6.7, Contribute +@section How to block spam on the project mailing list + +Sorry, we know the spam is a hassle. It would be nice to have a +moderator who can screen everything, but that takes too much time and +delays emails. Right now there is a procmail script which tags likely +spam and puts in a X-SBClass: header. If it is followed by 'Spam', then +it is almost certainly spam, if it is followed by 'Blocked', then it +scores high as being potential spam. You should be able to set some +rules in your mail client to throw those emails into a seperate folder. +It's not bullet proof (some legit mails get tagged wrong, and vice +versa), but it seems to be about 95% accurate in our experience. + + @node Version 1 Specifics, Document Revisions, Contribute, Top @chapter Version 1 Specific Questions