Changeset 1713

Timestamp:

02/17/03 02:58:10 (10 years ago)

Author:

mds

Message:

add Phil's note about spam blocking to the FAQ so we don't lose it.

Location:

lm-sensors/trunk/doc

Files:

• FAQ (modified) (2 diffs)
• lm_sensors-FAQ.html (modified) (4 diffs)
• lm_sensors-FAQ.texi (modified) (3 diffs)

lm-sensors/trunk/doc/FAQ

@@ -134 +134 @@
   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
@@ -1372 +1373 @@
 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
 ******************************

lm-sensors/trunk/doc/lm_sensors-FAQ.html

@@ -177 +177 @@
 <li><a href="#Section%206.6">6.6 How to submit a patch</a>
 <li><a href="#Section%206.7">6.7 How to REALLY help</a>
+<li><a href="#Section%206.8">6.8 How to block spam on the project mailing list</a>
 </ul>
 <li><a name="toc_Version%201%20Specifics"></a>
@@ -1799 +1800 @@
 <li><a accesskey=6 href="#Section%206.6">Section 6.6</a>:   How to submit a patch
 <li><a accesskey=7 href="#Section%206.7">Section 6.7</a>:   How to REALLY help
+<li><a accesskey=8 href="#Section%206.8">Section 6.8</a>:   How to block spam on the project mailing list
 </ul>
 
@@ -1878 +1880 @@
 <p><hr>
 Node:<a name="Section%206.7">Section 6.7</a>,
+Next:<a rel=next accesskey=n href="#Section%206.8">Section 6.8</a>,
 Previous:<a rel=previous accesskey=p href="#Section%206.6">Section 6.6</a>,
 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a>
@@ -1895 +1898 @@
 <p>Send us email <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a> if you can help. 
 No experience necessary :)
+
+<p><hr>
+Node:<a name="Section%206.8">Section 6.8</a>,
+Previous:<a rel=previous accesskey=p href="#Section%206.7">Section 6.7</a>,
+Up:<a rel=up accesskey=u href="#Contribute">Contribute</a>
+<br>
+
+<h3>6.8 How to block spam on the project mailing list</h3>
+
+<p>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.
 
 <p><hr>

lm-sensors/trunk/doc/lm_sensors-FAQ.texi

@@ -1339 +1339 @@
 * 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
 
@@ -1386 +1387 @@
 @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
 
@@ -1400 +1401 @@
 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.