X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-2.html;h=feb9bdf8a3ccbc19b3db61ac60ef65e3810a68be;hb=b34f092aea53555f7dcea38612def9692f8dba1d;hp=af3f76b349d9431f230f005e10a70dfbcbe7d33b;hpb=0ab180769648dfc2bde399c12b1b76c0f78e7648;p=spider.git diff --git a/html/adminmanual-2.html b/html/adminmanual-2.html index af3f76b3..feb9bdf8 100644 --- a/html/adminmanual-2.html +++ b/html/adminmanual-2.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Other filters @@ -13,13 +13,13 @@ Previous Contents
-

2. Other filters

+

2. Other filters

-

2.1 Filtering Mail +

2.1 Filtering Mail

In the /spider/msg directory you will find a file called badmsg.pl.issue. Rename -this to badmsg.pl and edit the file. The original looks something like this .... +this to badmsg.pl and edit the file. The original looks something like this ....

@@ -61,38 +61,39 @@ package DXMsg;
 );
-

+

+

I think this is fairly self explanatory. It is simply a list of subject headers that we do not want to pass on to either the users of the cluster or the other cluster nodes that we are linked to. This is usually because of -rules and regulations pertaining to items for sale etc in a particular country. -

-

-

2.2 Filtering words from text fields in Announce, Talk and DX spots +rules and regulations pertaining to items for sale etc in a particular country.

+ + +

2.2 Filtering words from text fields in Announce, Talk and DX spots

From version 1.48 onwards the interface to this has changed. You can now use the commands set/badword to add words that you are not prepared to see on the cluster, unset/badword to allow that word again and -show/badword to list the words that you have set. -

+show/badword to list the words that you have set.

+

If you have a previous /spider/data/badwords, the first time you start the node, it will read and convert this file to the new commands. The old style -file will then be removed. -

-

2.3 Stopping (possibly bad) DX Spots from Nodes or Spotters +file will then be removed.

+ +

2.3 Stopping (possibly bad) DX Spots from Nodes or Spotters

There are a number of commands that control whether a spot progresses -any further by regarding it as "bad" in some way. -

+any further by regarding it as "bad" in some way.

+

A DX Spot has a number of fields which can be checked to see whether they contain "bad" values, they are: the DX callsign itself, the Spotter and -the Originating Node. -

+the Originating Node.

+

There are a set of commands which allow the sysop to control whether a -spot continues:- +spot continues:-

@@ -101,34 +102,38 @@ set/badspotter
 set/badnode
+

These work in the same as the set/badword command, you can add any words or callsigns or whatever to the appropriate database. For -example, to stop a spot from a particular node you do: +example, to stop a spot from a particular node you do:

 set/badnode gb7djk gb7dxc
-

a bad spotter: +

+

a bad spotter:

 set/badspotter b0mb p1rat nocall
-

and some bad dx: +

+

and some bad dx:

 set/baddx video wsjt
+

You can remove a word using the appropriate unset command (unset/baddx, unset/badspotter, unset/badnode) or list them using one of show/baddx, show/badspotter and -show/badnode. -

+show/badnode.

+
Next Previous