-<UL>
-<LI>Login as root</LI>
-<LI>Get the additional CPAN modules and install them (root)</LI>
-<LI>Create the "sysop" user and set a password (root)</LI>
-<LI>Put the Spider tarball in sysop and untar it (root)</LI>
-<LI>ln -s sysop/spider /spider (root)</LI>
-<LI>groupadd -g 251 spider (root)</LI>
-<LI>Add any more users you need to the group entry in /etc/group (root)</LI>
-<LI>Set the permissions on the spider tree (root)</LI>
-<LI>Fix permissions on ax25_call and netrom_call (root)</LI>
-<LI>Login as the sysop user</LI>
-<LI>cd to /spider (sysop)</LI>
-<LI>mkdir local (sysop)</LI>
-<LI>mkdir local_cmd (sysop)</LI>
-<LI>cp perl/DXVars.pm.issue local/DXVars.pm (sysop)</LI>
-<LI>cd to /spider/local and edit DXVars to set your details (sysop)</LI>
-<LI>cd ../perl (sysop)</LI>
-<LI>./create_sysop.pl (sysop)</LI>
-<LI>./cluster.pl (sysop)</LI>
-</UL>
-<P>Spider should now be running and you should be able to login using the
-client program.
+<BLOCKQUOTE><CODE>
+<PRE>
+
+# the list of regexes for messages that we won't store having
+# received them (bear in mind that we must receive them fully before
+# we can bin them)
+
+
+# The format of each line is as follows
+
+# type source pattern
+# P/B/F T/F/O/S regex
+
+# type: P - private, B - bulletin (msg), F - file (ak1a bull)
+# source: T - to field, F - from field, O - origin, S - subject
+# pattern: a perl regex on the field requested
+
+# Currently only type B and P msgs are affected by this code.
+#
+# The list is read from the top down, the first pattern that matches
+# causes the action to be taken.
+
+# The pattern can be undef or 0 in which case it will always be selected
+# for the action specified
+
+
+
+package DXMsg;
+
+@badmsg = (
+'B', 'T', 'SALE',
+'B', 'T', 'WANTED',
+'B', 'S', 'WANTED',
+'B', 'S', 'SALE',
+'B', 'S', 'WTB',
+'B', 'S', 'WTS',
+'B', 'T', 'FS',
+);
+</PRE>
+</CODE></BLOCKQUOTE>
+</P>
+
+<P>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.</P>
+
+
+<H2><A NAME="ss2.2">2.2</A> <A HREF="adminmanual.html#toc2.2">Filtering words from text fields in Announce, Talk and DX spots</A>
+</H2>
+
+<P>From version 1.48 onwards the interface to this has changed. You can now
+use the commands <EM>set/badword</EM> to add words that you are not prepared
+to see on the cluster, <EM>unset/badword</EM> to allow that word again and
+<EM>show/badword</EM> to list the words that you have set.</P>
+
+<P>If you have a previous <EM>/spider/data/badwords</EM>, 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.</P>
+
+<H2><A NAME="ss2.3">2.3</A> <A HREF="adminmanual.html#toc2.3">Stopping (possibly bad) DX Spots from Nodes or Spotters</A>
+</H2>
+
+<P>
+There are a number of commands that control whether a spot progresses
+any further by regarding it as "bad" in some way.</P>
+
+<P>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.</P>
+
+<P>There are a set of commands which allow the sysop to control whether a
+spot continues:-</P>