[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs]  wording
[Savannah-cvs]  wording
Wed, 1 Nov 2017 22:08:25 -0400 (EDT)
Date: 2017-11-01 22:08:20 -0400 (Wed, 01 Nov 2017)
--- trunk/sviki/ListHelperAntiSpam.mdwn 2017-09-16 15:22:25 UTC (rev 347)
+++ trunk/sviki/ListHelperAntiSpam.mdwn 2017-11-02 02:08:20 UTC (rev 348)
@@ -2,10 +2,9 @@
If you're using a mailman list on lists.gnu.org for your project(\*),
-it's possible to configure mailman to automatically delete most spam.
-This is done by default for lists created through Savannah. The system
-is called listhelper, and its home page is
+most incoming spam can be automatically deleted. This is done by
+default for lists created through Savannah. The system is called
+listhelper, and its home page is <http://listhelper.nongnu.org/>.
Here is how to set it up (again, this is done by default):
@@ -21,14 +20,14 @@
> - ensure generic\_nonmember\_action=hold
> - (recommended) ensure default\_member\_moderation=yes ([\*\*])
-If you change these settings, we will assume you want to delete all the
-spam yourself and not use listhelper.
+If you change these settings, we will assume you want to delete all spam
+yourself and not use listhelper.
(\*) Actually, the spam removal via listhelper@ is not tied to gnu.org
-in any way. A few people are using it for handling non-GNU mailman lists
-as well. If you'd like to do that, email us. On the other hand, the
-shared moderation help via listhelper-moderate requires a script and
-cron job on the target system.
+in any way. A few people are using it for handling mailman lists outside
+of Savannahd and GNU as well. If you'd like to do that, email us. On the
+other hand, the shared moderation help via listhelper-moderate requires
+a script and cron job on the target system.
(\*\*) Actually, respond\_to\_post\_requests has nothing to do with the
listhelper system. But it's important to do, because it reduces
@@ -41,11 +40,23 @@
widespread. The cost is manually approving new members' first message
-How it works, what list owners have to do
+Any list @(non)gnu.org can use <mailto:address@hidden> as
+an administrator or moderator to help spread the moderation load. Human
+volunteers with listhelper will then try to approve real messages and
+delete missed spam.
-Without going into every detail, the result is that message that remain
-in the hold queue will be piped through a conservatively-configured
+By the way, there is no difference between listhelper[-moderate]
address@hidden and @nongnu.org. We tend to use @gnu.org for GNU lists and
address@hidden for non-GNU lists, but we aren't rigorous about it, and it
+makes no practical difference.
+How it works
+The general idea is that messages that end up in mailman's hold queue
+for the list will be piped through a conservatively-configured
spamassassin, and 95+% of spam will be automatically deleted after a
short delay (usually measured in minutes, unless things get backlogged).
@@ -60,31 +71,16 @@
approved addresses, which continue go through without delay.
Extensive suggestions and comments about many other Mailman
-configuration settings, based on experiences using listhelper over the
-years, are at
-<http://listhelper.nongnu.org/mailmanconf.html>. Many of those settings
-are made by default.
+configuration settings, based on list(helper) experiences over the
+years, are at <http://listhelper.nongnu.org/mailmanconf.html>. Many of
+those settings are made by default for Savannah lists.
-Please feel free to add other GNU lists, we don't need to be explicitly
+Please feel free to add other GNU lists; we don't need to be explicitly
informed. And of course we're happy to answer any questions. And if you
need help moderating the list, likewise let us know.
-Shared moderation: lists @(non)gnu.org can use
-<mailto:address@hidden> as an administrator or moderator to
-help spread the moderation load. (There is no difference between
-listhelper[-moderate] @gnu.org and @nongnu.org. We tend to use @gnu.org
-for GNU lists and @nongnu.org for non-GNU lists, but we aren't rigorous
-about it, and it makes no practical difference.)
-On lists.gnu.org, there is a cron entry (for user
-which lists the lists with recent pending messages. (There are many
-other cron entries which are a standard part of mailman installation.)
The system was set up by Bob Proulx, with kibitzing from Karl Berry. We
all attempt to review both the spam and nonspam that goes through the
system, to try to catch misclassified messages. (Very few real messages
@@ -92,19 +88,22 @@
We do not claim this is anything like an optimal or efficient system.
-But it is what we could do now, without requiring deep mail system
+But it is what we could do, without requiring deep mail system
infrastructure changes. Maybe someday a better system will be possible.
Nearly every list on lists.gnu.org is checked to some extent. The known
exceptions are those which explicitly did not want any checking, such as
-fsfe-uk, bug-freedink, Aubrey's lists (slib|jacal|scm|wb)-[\*], FSF
-member/campaign lists, etc. The exception list is given in the file
-`~list/etc/ignorelists.egrep` on lists. We spend about 15 minutes a day
-x 2 volunteers dealing with the normal flow, on average.
+fsfe-uk, bug-freedink, FSF member/campaign lists, etc. The exception
+list is given in the file `~list/etc/ignorelists.egrep` on lists. We
+spend about 15 minutes a day x 2 volunteers dealing with the normal
+flow, on average.
+On lists.gnu.org, there is a cron entry for user list
+which lists the lists with recent pending messages. (There are many
+other cron entries which are a standard part of mailman installation.)
The email-based trackers at <http://debbugs.gnu.org> (see the section in
[[SavaneTasks]] for a bit more) are filtered via the debbugs front-end
Mailman, but still go through listhelper and mailman if it passes that.
|[Prev in Thread]
||[Next in Thread]|
- [Savannah-cvs]  wording,