/usr/share/doc/fbbdoc/html/fmtmulti.htm is in fbbdoc 1:1999-2.1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>MULTI-server</title>
</head>
<body background="/back_fbb.jpg">
<p> </p>
<h1 align="Center"> MULTI server<small>.</small> </h1>
<p> </p>
<pre>MULTI.EXE, server for FBB-BBS.<br>(By LA6CU, Per)<br><br>This server is used to send personal copies of special messages. The <br>original is addressed to a special "call", and then there is automatically<br>made personal copies to everyone that shall have one.<br><br>MULTI may work in 2 ways. You may use one of them, or both. I use both at<br>the same time.<br><br>New in version 3.00:<br>The server may use different languages. There is a new file MULTI.TXT (reside<br>in SYSTEM-directory) that holds all languages. There is one "module" for<br>each language. See the text in MULTI.TXT for more info.<br><br><br>1: WITH DAT-FILES:<br>-------------------<br><br>Installation:<br><br>MULTI.EXE is put in the same directory as SERV.EXE. MULTI will read from<br><a href="fmtinit.htm">INIT.SRV</a>...<br><br>In INIT.SRV, MULTI is included together with <a href="fmtreqfi.htm">REQFIL</a>, <a href="fmtreqdi.htm">REQDIR</a> etc. Example:<br>#<br>------<br>#<br>REQFIL REQFIL<br>REQDIR REQDIR<br>CLUB MULTI<br>TEST MULTI<br>#<br><br>In this example all messages sent to<br>SP CLUB<br>will be copied to all callsigns in the file CLUB.DAT, while messages sent to<br>SP TEST<br>will be copied to all callsigns in the file TEST.DAT.<br><br>CLUB.DAT and TEST.DAT (in this example) must stay in the FBB-directory.<br>You must make one such .DAT-file for every to-field you define in INIT.SRV.<br><br>The .DAT-files must consist of callsigns (@BBS and H-addresses allowed) for <br>all those that shall have a copy.<br><br>There are 4 different copy-types.<br>A (action) : This is the callsign that will receive the message, or<br> perform the action described in the message.<br>C (copy) : This callsign receives a copy of the message.<br>I (information) : This callsign receives a copy for information.<br>H (hidden) : This callsign receives a copy, but his callsign will not<br> appear in the footnotes of the message, telling who has<br> received a copy.<br> <br>There may be more than one callsign on each line (starting with A, I, C or H)<br>separated by a comma. There may be maximum 100 callsigns altogether. <br>Comment-lines are extras, they MUST start with a #<br><br>From version 3.00 there will also be a separate line with a letter <br>corresponding to the language the server will use. What letter corresponds<br>to what language, is explained in MULTI.TXT.<br><br>Example of CLUB.DAT:<br><br>E <----- Use ENGLISH language for CLUB-server<br>A LA6CU, LA1B, LA2D <----- Copies to the people doing the job<br>A LA6GDA <----- " " " " " " "<br> May be several lines if there is not <br> enough room in one line. <br>I LA5RBA <----- LA5RBA is informed on the matter<br>C LA6IM @ LA6IM <----- LA6IM receives a copy for updating his<br> node-lists<br>H LA2GIA <----- LA2GIA receives a copy, but will not appear<br> in the list of callsigns at the end of<br> each message.<br><br>Beware: The .DAT-files shall consist of callsigns and comments, nothing <br> else ! No /EX, no * and no *** end of file.<br><br>MULTI will NOT send a copy back to the originator, even if he also is in<br>the .DAT-file. This to avoid "looping" of messages.<br>MULTI will send an acknowledge-message back to the originator, telling <br>him that the copying was successful, and show him a list of all callsigns<br>that will receive such a copy.<br><br>R:lines on incoming messages are removed, until there has arrived 2 lines<br>without R: After that. R:lines are accepted again. This is done to make it<br>possible also to forward messages back the same route, and at the same time<br>make it possible to include R:lines in the message itself.<br><br>R:lines are NOT checked to prevent forward to BBSs that are already in<br>these R:lines, because a message to a MULTI-server only will be processed<br>at the end-BBS anyway.<br><br>MULTI needs very little memory (I have not checked how much..), but I have<br>been told that it needs less than 35k. MULTI does not write to screen.<br><br>MULTI.EXE must be in the same directory as SERV.EXE.<br>From version 3.00 the .DAT-files must be in the SYSTEM-directory.<br>MULTI.TXT must also be in SYSTEM-directory.<br><br>MULTI makes a temporary file MULTI.TMP on disk, and delete it afterwards.<br>Everything else is done in memory, and the result is placed in MAIL.IN, as<br>all servers do.<br><br><br>2: WITH ALL CALLSIGNS DIRECTLY IN THE ORIGINAL-MESSAGE.<br>--------------------------------------------------------<br><br>MULTI still works exactly as before, with the same installation. But after<br>a request from F6ABJ and F6FBB I have made a modification so that users<br>themselves can decide what callsigns will receive a copy. This is done<br>by including the callsigns in the message itself.<br><br>In INIT.SRV, MULTI is still included like before (see further up). But<br>in addition, you now must have 1 extra line, like this:<br><br>#<br>------<br>#<br>REQFIL REQFIL<br>REQDIR REQDIR<br>CLUB MULTI<br>TEST MULTI<br>MULTI MULTI <---- This line is new.<br>#<br><br>From version 3.00 SP MULTI uses the default language (see MULTI.TXT).<br>Other languages may be configured. For example you may have:<br>MULTI MULTI (for default language)<br>MULTIE MULTI (for english language)<br>MULTIF MULTI (for french language)<br>MULTIH MULTI (for netherlands language)<br>MULTIN MULTI (for norwegian language)<br>So, you may send the same message SP MULTI, SP MULTIE, SP MULTIF, SP MULTIH,<br>SP MULTIN etc. The first 5 letters must always be MULTI, when used without<br>DAT-file. Default language will typically be english (SP MULTI), but the<br>users will have the possibility to use others, as configured.<br><br>Users will now be able to send messages to MULTI, like this:<br>SP MULTI The program will now collect the info on who will receive a <br>copy, from the message itself, and not from a seperat .DAT-file like <br>SP CLUB or SP TEST still will do.<br><br>There are 4 different copy-types.<br>A (action) : This is the callsign that will receive the message, or<br> perform the action described in the message.<br>C (copy) : This callsign receives a copy of the message.<br>I (information) : This callsign receives a copy for information.<br>H (hidden) : This callsign receives a copy, but his callsign will not<br> appear in the footnotes of the message, telling who has<br> received a copy.<br>(In addition one may use CC: instead of only C for Copy. Special request..)<br><br>There may be more than one callsign on each line (starting with A, I, C or H)<br>separated by a comma. There may be maximum 100 callsigns altogether. <br>Comment-lines are extras, they MUST start with a #<br><br>Example:<br>SP MULTI<br>Digipeater upgrade <----- Title of message<br>A LA6CU, LA1B, LA2D <----- Copies to the people doing the job<br>A LA6GDA <----- " " " " " " "<br>I LA5RBA <----- LA5RBA is informed on the matter<br>C LA6IM @ LA6IM <----- LA6IM receives a copy for updating his<br> node-lists<br>H LA2GIA <----- LA2GIA receives a copy, but will not appear<br> in the list of callsigns at the end of<br> each message.<br>--------- <----- After the last callsign, there must be a<br> string of at least 5 '-' before the<br> actual message.<br> <br>Then follows the contents of the message, and end with Ctrl-Z or /EX.<br><br>As usual, the sender will receive a message saying that the copies were<br>made. The messages to all the other callsigns will be identical, and look<br>like this:<br><br>Message via LA6CU MULTI-server (v3.00) :<br><br>Contents of message<br><br>============================================================================<br>For action : LA6GDA, LA6CU, LA1B, LA2D.<br>For copy : LA6IM.<br>For information : LA5RBA.<br>============================================================================<br><br>All copies are identical, but A, C and I determines in which line in the<br>footnotes the callsigns will appear. A callsign after an H will not <br>appear in the footnotes.<br><br>73 de Per, LA6CU.<br><br><br>
<font color="#800000">This page was last updated 17-Apr-99</font>
</pre>
</body>
</html>
|