+ 9\b9.\b. M\bMa\bai\bil\bl
+
+ DXSpider deals seamlessly with standard AK1A type mail. It supports
+ both personal and bulletin mail and the sysop has additional commands
+ to ensure that mail gets to where it is meant. DXSpider will send
+ mail almost 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.
+
+ The cluster mail is automatically deleted after 30 days unless the
+ sysop sets the "keep" flag using the _\bm_\bs_\bg command.
+
+ 9\b9.\b.1\b1.\b. P\bPe\ber\brs\bso\bon\bna\bal\bl m\bma\bai\bil\bl
+
+ Personal mail is sent using the _\bs_\bp command. This is actually the
+ default method of sending mail and so a simple _\bs for send will do. A
+ full list of the send commands and options is in the _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\bs_\be_\bt
+ section, so I will not duplicate them here.
+
+
+ 9\b9.\b.2\b2.\b. B\bBu\bul\bll\ble\bet\bti\bin\bn m\bma\bai\bil\bl
+
+ Bulletin mail is sent by using the _\bs_\bb command. This is one of the
+ most common mistakes users make when sending mail. They send a
+ bulletin mail with _\bs or _\bs_\bp instead of _\bs_\bb and of course the message
+ never leaves the cluster. This can be rectified by the sysop by using
+ the _\bm_\bs_\bg command.
+
+
+ Bulletin addresses can be set using the Forward.pl file.
+
+
+ 9\b9.\b.3\b3.\b. F\bFo\bor\brw\bwa\bar\brd\bd.\b.p\bpl\bl
+
+ DXSpider receives all and any mail sent to it without any alterations
+ needed in files. Because personal and bulletin mail are treated
+ differently, there is no need for a list of accepted bulletin
+ addresses. It is necessary, however, to tell the program which links
+ accept which bulletins. For example, it is pointless sending
+ bulletins addresses to "UK" to any links other than UK 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 ...
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ #
+ # this is an example message forwarding file for the system
+ #
+ # The format of each line is as follows
+ #
+ # type to/from/at pattern action destinations
+ # P/B/F T/F/A regex I/F [ call [, call ...] ]
+ #
+ # type: P - private, B - bulletin (msg), F - file (ak1a bull)
+ # to/from/at: T - to field, F - from field, A - home bbs, O - origin
+ # pattern: a perl regex on the field requested
+ # action: I - ignore, F - forward
+ # destinations: a reference to an array containing node callsigns
+ #
+ # if it is non-private and isn't in here then it won't get forwarded
+ #
+ # Currently only type B 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
+ #
+ # If the BBS list is undef or 0 and the action is 'F' (and it matches the
+ # pattern) then it will always be forwarded to every node that doesn't have
+ # it (I strongly recommend you don't use this unless you REALLY mean it, if
+ # you allow a new link with this on EVERY bull will be forwarded immediately
+ # on first connection)
+ #
+
+ package DXMsg;
+
+ @forward = (
+ );
+
+
+
+
+ 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.
+
+
+ To force the cluster to reread the file use load/forward
+
+
+
+ 9\b9.\b.4\b4.\b. T\bTh\bhe\be m\bms\bsg\bg c\bco\bom\bmm\bma\ban\bnd\bd
+
+ The _\bm_\bs_\bg 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.
+
+ Here is a full list of the various options ...
+
+
+
+
+
+
+
+
+
+
+
+ MSG TO <msgno> <call> - change TO callsign to <call>
+ MSG FRom <msgno> <call> - change FROM callsign to <call>
+ MSG PRrivate <msgno> - set private flag
+ MSG NOPRrivate <msgno> - unset private flag
+ MSG RR <msgno> - set RR flag
+ MSG NORR <msgno> - unset RR flag
+ MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
+ MSG NOKEep <msgno> - unset the keep flag
+ MSG SUbject <msgno> <new> - change the subject to <new>
+ MSG WAittime <msgno> - remove any waiting time for this message
+ MSG NOREad <msgno> - mark message as unread
+ MSG REad <msgno> - mark message as read
+ MSG QUeue - queue any outstanding bulletins
+ MSG QUeue 1 - queue any outstanding private messages
+
+
+
+
+ These commands are simply typed from within the cluster as the sysop
+ user.
+
+
+ 9\b9.\b.5\b5.\b. M\bMe\bes\bss\bsa\bag\bge\be s\bst\bta\bat\btu\bus\bs
+
+ You can check on a message from within the cluster by using the
+ command _\bs_\bt_\ba_\bt_\b/_\bm_\bs_\bg. 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 ...
+
+
+
+ G0VGS de GB7MBC 28-Jan-2001 1308Z >
+ stat/msg 6869
+ From: GB7DJK
+ Msg Time: 26-Jan-2001 1302Z
+ Msgno: 6869
+ Origin: GB7DJK
+ Size: 8012
+ Subject: AMSAT 2line KEPS 01025.AMSAT
+ To: UK
+ Got it Nodes: GB7BAA, GB7ADX
+ Private: 0
+ Read Confirm: 0
+ Times read: 0
+ G0VGS de GB7MBC 28-Jan-2001 1308Z >
+
+
+
+
+
+ 9\b9.\b.6\b6.\b. F\bFi\bil\blt\bte\ber\bri\bin\bng\bg m\bma\bai\bil\bl
+
+ This is described in the section on _\bO_\bt_\bh_\be_\br _\bf_\bi_\bl_\bt_\be_\br_\bs so I will not
+ duplicate it here.
+
+
+ 9\b9.\b.7\b7.\b. D\bDi\bis\bst\btr\bri\bib\bbu\but\bti\bio\bon\bn l\bli\bis\bst\bts\bs
+
+ 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 _\bd_\bi_\bs_\bt_\br_\bo. You put
+ any distibution lists in here. For example, here is a file called
+ SYSOP.pl that caters for the UK sysops.
+
+
+ qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
+ GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
+ GB7DXK GB7DXI GB7DXS)
+
+
+
+
+ Any mail sent to "sysop" would only be sent to the callsigns in this
+ list.
+
+
+ 9\b9.\b.8\b8.\b. B\bBB\bBS\bS i\bin\bnt\bte\ber\brf\bfa\bac\bce\be
+
+ 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.
+
+
+ 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.
+
+
+ 1\b10\b0.\b. D\bDa\bat\bta\bab\bba\bas\bse\bes\bs
+
+ Spider allows the creation of local or remote databases. It supports
+ chained databases, allowing several different databases to be scanned
+ with one simple command. Importing of databases is limited at present
+ to the standard AK1A databases such as OBLAST and the DB0SDX QSL
+ database but will expand with time.
+
+
+ 1\b10\b0.\b.1\b1.\b. C\bCr\bre\bea\bat\bti\bin\bng\bg d\bda\bat\bta\bab\bba\bas\bse\bes\bs
+
+ Creating a database could not be more simple. All the commands are
+ sent from the cluster prompt as the _\bs_\by_\bs_\bo_\bp user.
+
+ To create a database you use the command _\bd_\bb_\bc_\br_\be_\ba_\bt_\be. It can be used in
+ 3 different ways like so ..
+
+