Changeset 1713

Show
Ignore:
Timestamp:
02/17/03 02:58:10 (12 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:
3 modified

Legend:

Unmodified
Added
Removed
  • lm-sensors/trunk/doc/FAQ

    r1526 r1713  
    134134  6.6 How to submit a patch 
    135135  6.7 How to REALLY help 
     136  6.8 How to block spam on the project mailing list 
    136137 
    1371387 Version 1 Specific Questions 
     
    13721373experience necessary :) 
    13731374 
     13756.8 How to block spam on the project mailing list 
     1376================================================= 
     1377 
     1378   Sorry, we know the spam is a hassle.  It would be nice to have a 
     1379moderator who can screen everything, but that takes too much time and 
     1380delays emails.  Right now there is a procmail script which tags likely 
     1381spam and puts in a X-SBClass: header.  If it is followed by 'Spam', then 
     1382it is almost certainly spam, if it is followed by 'Blocked', then it 
     1383scores high as being potential spam.  You should be able to set some 
     1384rules in your mail client to throw those emails into a seperate folder. 
     1385It's not bullet proof (some legit mails get tagged wrong, and vice 
     1386versa), but it seems to be about 95% accurate in our experience. 
     1387 
    137413887 Version 1 Specific Questions 
    13751389****************************** 
  • lm-sensors/trunk/doc/lm_sensors-FAQ.html

    r1526 r1713  
    177177<li><a href="#Section%206.6">6.6 How to submit a patch</a> 
    178178<li><a href="#Section%206.7">6.7 How to REALLY help</a> 
     179<li><a href="#Section%206.8">6.8 How to block spam on the project mailing list</a> 
    179180</ul> 
    180181<li><a name="toc_Version%201%20Specifics"></a> 
     
    17991800<li><a accesskey=6 href="#Section%206.6">Section 6.6</a>:   How to submit a patch 
    18001801<li><a accesskey=7 href="#Section%206.7">Section 6.7</a>:   How to REALLY help 
     1802<li><a accesskey=8 href="#Section%206.8">Section 6.8</a>:   How to block spam on the project mailing list 
    18011803</ul> 
    18021804 
     
    18781880<p><hr> 
    18791881Node:<a name="Section%206.7">Section 6.7</a>, 
     1882Next:<a rel=next accesskey=n href="#Section%206.8">Section 6.8</a>, 
    18801883Previous:<a rel=previous accesskey=p href="#Section%206.6">Section 6.6</a>, 
    18811884Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
     
    18951898<p>Send us email <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a> if you can help.  
    18961899No experience necessary :) 
     1900 
     1901<p><hr> 
     1902Node:<a name="Section%206.8">Section 6.8</a>, 
     1903Previous:<a rel=previous accesskey=p href="#Section%206.7">Section 6.7</a>, 
     1904Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
     1905<br> 
     1906 
     1907<h3>6.8 How to block spam on the project mailing list</h3> 
     1908 
     1909<p>Sorry, we know the spam is a hassle.  It would be nice to have a 
     1910moderator who can screen everything, but that takes too much time and 
     1911delays emails.  Right now there is a procmail script which tags likely 
     1912spam and puts in a X-SBClass: header.  If it is followed by 'Spam', then 
     1913it is almost certainly spam, if it is followed by 'Blocked', then it 
     1914scores high as being potential spam.  You should be able to set some 
     1915rules in your mail client to throw those emails into a seperate folder.  
     1916It's not bullet proof (some legit mails get tagged wrong, and vice 
     1917versa), but it seems to be about 95% accurate in our experience. 
    18971918 
    18981919<p><hr> 
  • lm-sensors/trunk/doc/lm_sensors-FAQ.texi

    r1526 r1713  
    13391339* Section 6.6::  How to submit a patch 
    13401340* Section 6.7::  How to REALLY help 
     1341* Section 6.8::  How to block spam on the project mailing list 
    13411342@end menu 
    13421343 
     
    13861387@command{cvs diff -u2}. Send us the patch in an email and tell us what it does. 
    13871388 
    1388 @node Section 6.7, , Section 6.6, Contribute 
     1389@node Section 6.7, Section 6.8, Section 6.6, Contribute 
    13891390@section How to REALLY help 
    13901391 
     
    14001401Send us email @email{sensors@@stimpy.netroedge.com} if you can help. 
    14011402No experience necessary :) 
     1403 
     1404 
     1405@node Section 6.8, , Section 6.7, Contribute 
     1406@section How to block spam on the project mailing list 
     1407 
     1408Sorry, we know the spam is a hassle.  It would be nice to have a  
     1409moderator who can screen everything, but that takes too much time and  
     1410delays emails.  Right now there is a procmail script which tags likely  
     1411spam and puts in a X-SBClass: header.  If it is followed by 'Spam', then  
     1412it is almost certainly spam, if it is followed by 'Blocked', then it  
     1413scores high as being potential spam.  You should be able to set some  
     1414rules in your mail client to throw those emails into a seperate folder.   
     1415It's not bullet proof (some legit mails get tagged wrong, and vice  
     1416versa), but it seems to be about 95% accurate in our experience. 
    14021417 
    14031418