MULTI, server for FBB-BBS. (By LA6CU, Per) This server is used to send multi personal copies of messages. MULTI may work in 2 ways. 1: WITH DAT-FILES: created and installed on the bbs by the Sysop. In this case the original is adressed to a special "call", which is a file name of a data file created by the bbs Sysop containing the calls of everyone that shall have one. In this example all messages sent to SP CLUB will be copied to all callsigns in the file CLUB.DAT, while messages sent to SP TEST will be copied to all callsigns in the file TEST.DAT. The .DAT-files must consist of callsigns (@BBS and H-adresses allowed) for all those that shall have a copy. There are 4 different copy-types. A (action) : This is the callsign that will receive the message, or perform the action described in the message. C (copy) : This callsign receives a copy of the message. I (information) : This callsign receives a copy for information. H (hidden) : This callsign receives a copy, but his callsign will not appear in the footnotes of the message, telling who has received a copy. There may be more than one callsign on each line (starting with A, I, C or H) seperated by a comma. There may be maximum 100 callsigns altogether. Comment-lines are extras, they MUST start with a # From version 3.00 there will also be a seperate line with a letter corresponding to the language the server will use. What letter corresponds to what language, is explained in below. Example of CLUB.DAT: E <----- Use ENGLISH language for CLUB-server A LA6CU, LA1B, LA2D <----- Copies to the people doing the job A LA6GDA <----- " " " " " " " May be several lines if there is not enough room in one line. I LA5RBA <----- LA5RBA is informed on the matter C LA6IM @ LA6IM <----- LA6IM receives a copy for updating his node-lists H LA2GIA <----- LA2GIA receives a copy, but will not appear in the list of callsigns at the end of each message. Beware: The .DAT-files shall consist of callsigns and comments, nothing else ! No /EX, no * and no *** end of file. MULTI will NOT send a copy back to the originator, even if he also is in the .DAT-file. This to avoid "looping" of messages. MULTI will send an acknowledge-message back to the originator, telling him that the copying was successful, and show him a list of all callsigns that will receive such a copy. 2: WITH ALL CALLSIGNS DIRECTLY IN THE ORIGINAL-MESSAGE. -------------------------------------------------------- MULTI still works exactly as above. Users themselves can decide what callsigns will receive a copy. This is done by addressing the message to any one of the forms of MULTI as indicated below, which specifies the language to be used, and by including the callsigns in the message itself. From version 3.00 SP MULTI uses the default language. Other languages may be configured. For example you may have: MULTI MULTI (for default language) MULTIE MULTI (for english language) MULTIF MULTI (for french language) MULTIH MULTI (for netherlands language) MULTIN MULTI (for norwegian language) So, you may send the same message SP MULTI, SP MULTIE, SP MULTIF, SP MULTIH, SP MULTIN etc. The first 5 letters must always be MULTI, when used without DAT-file. Default language will typically be english (SP MULTI), but the users have the possibillity to use others, as configured. Users will now be able to send messages to MULTI, like this: SP MULTI The program will now collect the info on who will receive a copy, from the message itself, and not from a seperat .DAT-file like SP CLUB or SP TEST still will do. There are 4 different copy-types. A (action) : This is the callsign that will receive the message, or perform the action described in the message. C (copy) : This callsign receives a copy of the message. I (information) : This callsign receives a copy for information. H (hidden) : This callsign receives a copy, but his callsign will not appear in the footnotes of the message, telling who has received a copy. (In addition one may use CC: instead of only C for Copy. Special request..) There may be more than one callsign on each line (starting with A, I, C or H) seperated by a comma. There may be maximum 100 callsigns altogether. Comment-lines are extras, they MUST start with a # Example: SP MULTI Digipeater upgrade <----- Title of message A LA6CU, LA1B, LA2D <----- Copies to the people doing the job A LA6GDA <----- " " " " " " " I LA5RBA <----- LA5RBA is informed on the matter C LA6IM @ LA6IM <----- LA6IM receives a copy for updating his node-lists H LA2GIA <----- LA2GIA receives a copy, but will not appear in the list of callsigns at the end of each message. --------- <----- After the last callsign, there must be a string of at least 5 '-' before the actual message. Then follows the contents of the message, and end with Ctrl-Z or /EX. As ususal, the sender will receive a message saying that the copies were made. The messages to all the other calligns will be identical, and look like this: Message via LA6CU MULTI-server (v3.00) : Contents of message ============================================================================ For action : LA6GDA, LA6CU, LA1B, LA2D. For copy : LA6IM. For information : LA5RBA. ============================================================================ All copies are identical, but A, C and I determines in which line in the footnotes the callsigns will appear. A callsign after an H will not appear in the footnotes. ----- Note: Origional text modified by K2BJG. eof 2008-08-30