<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
<TITLE>The DXSpider Administration Manual v1.50: Mail</TITLE>
<LINK HREF="adminmanual-4.html" REL=next>
<LINK HREF="adminmanual-2.html" REL=previous>
<A HREF="adminmanual-2.html">Previous</A>
<A HREF="adminmanual.html#toc3">Contents</A>
<HR>
-<H2><A NAME="s3">3. Mail</A></H2>
+<H2><A NAME="s3">3.</A> <A HREF="adminmanual.html#toc3">Mail</A></H2>
<P>DXSpider deals seamlessly with standard AK1A type mail. It supports both
personal and bulletin mail and the sysop has additional commands to ensure
immediately, assuming that the target is on line. However, only one
mail message is dealt with at any one time. If a mail message is already
being sent or recieved, then the new message will be queued until it has
-finished.
+finished.</P>
<P>The cluster mail is automatically deleted after 30 days unless the sysop
-sets the "keep" flag using the <EM>msg</EM> command.
-<P>
-<H2><A NAME="ss3.1">3.1 Personal mail</A>
+sets the "keep" flag using the <EM>msg</EM> command.</P>
+
+<H2><A NAME="ss3.1">3.1</A> <A HREF="adminmanual.html#toc3.1">Personal mail</A>
</H2>
<P>Personal mail is sent using the <EM>sp</EM> command. This is actually the
default method of sending mail and so a simple <EM>s</EM> for send will do.
A full list of the send commands and options is in the <EM>command set</EM>
-section, so I will not duplicate them here.
-<P>
-<H2><A NAME="ss3.2">3.2 Bulletin mail</A>
+section, so I will not duplicate them here.</P>
+
+<H2><A NAME="ss3.2">3.2</A> <A HREF="adminmanual.html#toc3.2">Bulletin mail</A>
</H2>
<P>Bulletin mail is sent by using the <EM>sb</EM> command. This is one of the
most common mistakes users make when sending mail. They send a bulletin
mail with <EM>s</EM> or <EM>sp</EM> instead of <EM>sb</EM> and of course
the message never leaves the cluster. This can be rectified by the sysop
-by using the <EM>msg</EM> command.
-<P>
-<P>Bulletin addresses can be set using the Forward.pl file.
-<P>
-<H2><A NAME="ss3.3">3.3 Forward.pl</A>
+by using the <EM>msg</EM> command.</P>
+
+<P>Bulletin addresses can be set using the Forward.pl file.</P>
+
+<H2><A NAME="ss3.3">3.3</A> <A HREF="adminmanual.html#toc3.3">Forward.pl</A>
</H2>
<P>DXSpider receives all and any mail sent to it without any alterations needed
ones. The file that does this is called forward.pl and lives in /spider/msg.
At default, like other spider files it is named forward.pl.issue. Rename it
to forward.pl and edit the file to match your requirements.
-The format is below ...
+The format is below ...</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
);
</PRE>
</CODE></BLOCKQUOTE>
+</P>
<P>Simply insert a bulletin address and state in the brackets where you wish
that mail to go. For example, you can see here that mail sent to "UK" will
-only be sent to the UK links and not to PA4AB-14.
-<P>
-<P>To force the cluster to reread the file use load/forward
-<P>
+only be sent to the UK links and not to PA4AB-14.</P>
+
+<P>To force the cluster to reread the file use load/forward</P>
+
<P>NB: If a user tries to send mail to a bulletin address that does not exist
-in this file, they will get an error.
-<P>
-<H2><A NAME="ss3.4">3.4 The msg command</A>
+in this file, they will get an error.</P>
+
+<H2><A NAME="ss3.4">3.4</A> <A HREF="adminmanual.html#toc3.4">The msg command</A>
</H2>
<P>The <EM>msg</EM> command is a very powerful and flexible tool for the
sysop. It allows the sysop to alter to and from fields and make other
-changes to manage the cluster mail.
-<P>Here is a full list of the various options ...
+changes to manage the cluster mail.</P>
+<P>Here is a full list of the various options ...</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
MSG QUeue 1 - queue any outstanding private messages
</PRE>
</CODE></BLOCKQUOTE>
-<P>These commands are simply typed from within the cluster as the sysop user.
-<P>
-<H2><A NAME="ss3.5">3.5 Message status</A>
+</P>
+<P>These commands are simply typed from within the cluster as the sysop user.</P>
+
+<H2><A NAME="ss3.5">3.5</A> <A HREF="adminmanual.html#toc3.5">Message status</A>
</H2>
<P>You can check on a message from within the cluster by using the command
<EM>stat/msg</EM>. This will give you additional information on the
message number including which nodes have received it, which node it
was received from and when etc. Here is an example of the output of
-the command ...
+the command ...</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
G0VGS de GB7MBC 28-Jan-2001 1308Z >
</PRE>
</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss3.6">3.6 Filtering mail</A>
+</P>
+
+<H2><A NAME="ss3.6">3.6</A> <A HREF="adminmanual.html#toc3.6">Filtering mail</A>
</H2>
<P>This is described in the section on <EM>Other filters</EM> so I will not
-duplicate it here.
-<P>
-<H2><A NAME="ss3.7">3.7 Distribution lists</A>
+duplicate it here.</P>
+
+<H2><A NAME="ss3.7">3.7</A> <A HREF="adminmanual.html#toc3.7">Distribution lists</A>
</H2>
<P>Distribution lists are simply a list of users to send certain types of
mail to. An example of this is mail you only wish to send to other
sysops. In /spider/msg there is a directory called <EM>distro</EM>. You
put any distibution lists in here. For example, here is a file called
-SYSOP.pl that caters for the UK sysops.
+SYSOP.pl that caters for the UK sysops.</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
GB7DXK GB7DXI GB7DXS)
</PRE>
</CODE></BLOCKQUOTE>
-<P>Any mail sent to "sysop" would only be sent to the callsigns in this list.
-<P>
-<H2><A NAME="ss3.8">3.8 BBS interface</A>
+</P>
+<P>Any mail sent to "sysop" would only be sent to the callsigns in this list.</P>
+
+<H2><A NAME="ss3.8">3.8</A> <A HREF="adminmanual.html#toc3.8">BBS interface</A>
</H2>
<P>Spider provides a simple BBS interface. No input is required from the sysop
of the cluster at all. The BBS simply sets the cluster as a BBS and pushes
any required mail to the cluster. No mail can flow from Spider to the BBS,
-the interface is one-way.
-<P>
+the interface is one-way.</P>
+
<P>Please be careful not to flood the cluster network with unnecessary mail.
Make sure you only send mail to the clusters that want it by using the
-Forward.pl file very carefully.
-<P>
+Forward.pl file very carefully.</P>
+
<HR>
<A HREF="adminmanual-4.html">Next</A>
<A HREF="adminmanual-2.html">Previous</A>