Beijing Paradise BBS Backup

home *** CD-ROM | disk | FTP | other *** search

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / WMAIL230.ZIP / WMAIL.DOC < prev next >

Wrap

Text File | 1992-12-28 | 78.7 KB | 2,703 lines

Window Mail ───────────── Version 2.3 - December 1992 EchoMail Processor FTS compliant (C) Copyright 1990-92 Silvan Calarco, FidoNet 2:334/100.2 Documentation by: Franco Schinco, FidoNet 2:334/100.0 Silvan Calarco, FidoNet 2:334/100.2 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 Table of Contents INTRODUCTION................................................... 1 THANKS......................................................... 1 LICENSE AGREEMENT.............................................. 2 INSTALLATION................................................... 3 CONFIGURATION.................................................. 4 WMSETUP.EXE............................................... 4 File...................................................... 4 DOS Shell............................................ 4 Write setup.......................................... 4 Write areas.......................................... 4 Write route.......................................... 4 Import areas......................................... 5 Save options......................................... 5 Exit................................................. 5 Global.................................................... 6 User - Sysop......................................... 6 User - Key........................................... 6 Address - Main....................................... 6 Address - Aka 1-10................................... 6 ZoneGate - Zonegate 1-10............................. 6 Directory - Mail..................................... 6 Directory - Files.................................... 6 Directory - Packets.................................. 6 Directory - ARCmail.................................. 7 Directory - MsgBase.................................. 7 Directory - DupPath.................................. 7 Directory - BadEcho.................................. 7 Directory - Packer................................... 7 Directory - Stats.................................... 7 Directory - New areas................................ 8 Directory - Nodelist................................. 8 Origin 1-10.......................................... 8 Manager................................................... 8 Defaults - Put origin................................ 8 Defaults - Put tear line............................. 8 Defaults - Hide seen-by.............................. 8 Defaults - Strip 4d.................................. 8 Defaults - Add aka's................................. 9 Defaults - Put domain................................ 9 Defaults - Force public.............................. 9 Defaults - Force private............................. 9 Defaults - 4d point infos............................ 9 Packers - ARC........................................ 9 Packers - ARJ........................................ 9 Packers - LZH........................................ 9 Packers - PAK........................................ 9 Packers - ZIP........................................ 9 Packers - ZOO........................................ 9 Packers - SQZ....................................... 10 Packers - Default................................... 10 Unpackers - ARC..................................... 10 Unpackers - ARJ..................................... 10 Unpackers - LZH..................................... 10 Unpackers - PAK..................................... 10 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 Unpackers - ZIP..................................... 10 Unpackers - ZOO..................................... 10 Unpackers - SQZ..................................... 10 Nodes - Node........................................ 10 Nodes - Packer...................................... 10 Nodes - Packet Pw................................... 11 Nodes - Areafix Pw.................................. 11 Nodes - Level....................................... 11 Nodes - Aka......................................... 11 Nodes - Daily pkts.................................. 11 Areas - Status...................................... 11 Areas - Descr....................................... 11 Areas - Kind........................................ 11 Areas - Tag......................................... 11 Areas - Dir......................................... 11 Areas - Level....................................... 12 Areas - Origin...................................... 12 Areas - Flags - Put origin.......................... 12 Areas - Flags - Put tear line....................... 12 Areas - Flags - Hide seen-by........................ 12 Areas - Flags - Strip 4d............................ 12 Areas - Flags - Add aka's........................... 12 Areas - Flags - Put domain.......................... 12 Areas - Flags - Force public........................ 12 Defaults - Force private............................ 12 Defaults - 4d point infos........................... 13 Areas - Aka......................................... 13 Areas - Frwd. 1-3................................... 13 Misc..................................................... 13 General - Mailer.................................... 13 General - Fake net.................................. 13 General - Import dupes.............................. 13 General - Import bad................................ 13 General - Stats..................................... 14 General - Log file.................................. 14 General - Minimum space............................. 14 General - Swap...................................... 14 General - Use nodelist.............................. 14 General - Create areas.............................. 14 General - Honor RRRs................................ 14 General - Link tear line............................ 14 Files - Log File.................................... 14 Files - Style....................................... 15 Files - Level....................................... 15 Files - Rescan file................................. 15 Areafix - Kill msgs................................. 15 Areafix - Sort nodes................................ 15 Areafix - Short form................................ 15 Areafix - Allow rescan.............................. 15 Areafix - List file................................. 15 Areafix - Link nodes................................ 15 Areafix - Creating nodes............................ 16 Areafix - Alert nodes............................... 16 Areafix - Messages Flags - Crash.................... 16 Areafix - Messages Flags - Hold..................... 16 Areafix - Messages Flags - Kill/sent................ 16 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 Pack - Kill msgs.................................... 16 Pack - Route file................................... 16 Colors - Default.................................... 16 Colors - Mono....................................... 16 Colors - WMail 2.2.................................. 16 Colors - Customize.................................. 16 EXECUTION..................................................... 17 FUNCTIONS DESCRIPTION......................................... 18 USE OF WMAIL.................................................. 19 IMPORT................................................... 19 EXPORT................................................... 20 PACK..................................................... 21 SETMARK.................................................. 22 HIMARK................................................... 22 WRITESTATS............................................... 22 AREAFIX.................................................. 23 ROUTING....................................................... 24 Default routing.......................................... 24 System definitions....................................... 25 Routing commands......................................... 25 SCHEDULE ........................................... 25 SEND-TO ............................................ 26 HOLD ............................................... 26 UNHOLD ............................................. 26 ROUTE-TO ........................................... 26 NO-ROUTE ........................................... 26 ROUTE-FILES ........................................ 26 POLL ............................................... 26 EXCEPT ............................................. 27 CHANGE ............................................. 27 LEAVE .............................................. 27 UNLEAVE ............................................ 27 Specifications for node lists............................ 28 Note about points........................................ 28 Routing philosophy....................................... 28 Examples................................................. 29 HOW AREAFIX WORKS............................................. 30 OTHER FUNCTIONS............................................... 31 Return receipts.......................................... 31 Security................................................. 31 New areas creation....................................... 31 TECHNICAL NOTES............................................... 32 PKT with extended header................................. 32 Product Code............................................. 32 Areas.................................................... 32 New Areas................................................ 32 Nodes.................................................... 32 Dupes.................................................... 32 MSGID.................................................... 32 PID and Tear-line........................................ 32 Illegal registration keys................................ 32 Attack messages.......................................... 33 Directory creation....................................... 33 Memory occupation........................................ 33 ARCMail processing order................................. 33 Maximum message length................................... 33 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 Execution errors......................................... 33 Limitations in unregistered copies....................... 33 Limitations in point registered copies................... 33 QuickBBS files sharing................................... 34 ARCmail naming convention................................ 34 Video mode............................................... 34 Technical support........................................ 34 EXAMPLES OF BATCH FILES....................................... 35 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 INTRODUCTION WMail is a brand new Echomail management program, for PC-based system using mailers like Opus and BinkleyTerm, or FrontDoor and D'Bridge. Its main characteristics: - supports Fido compatible message base - supports QuickBBS compatible message base - contains Pack function, for EchoMail and NetMail - includes Areafix function - point management, through FakeNet or with 4-dimension address both in FrontDoor and BinkleyTerm modality - creates EchoMail traffic statistics every week/month/year - operates in FrontDoor manner or as Binkley and Opus - windows (not Windows :-) ) graphic interface - can have both Fido and QuickBBS areas formats in the same areas file - supports PassThru areas - supports AKAs and ZoneGates ~~~~~~~~ This user manual relies on the knowledge of the basic functioning concepts of a Bbs or a Point: for these things, you should read the documentation included in the mailers used for EchoMail transmission and in the Bbs management programs. THANKS I want to thank all Beta-Testers, who helped me very much in the development of WMail: Ugo Uggetti, Andrea Mennini, Massimo Gentilini, Marco Maccaferri, Cesare Dieni, Luca Leone, Roberto Piola, Alberto Enna, Gianfranco Lanzilli, Mario Battacchi, Francois Thunus. Special thanks are due to these people: - Franco Schinco, victim of the first WMail trials on his message base and author of this documentation. - Franco Carcillo, who encouraged me very strongly to complete the work. - Maurizio Codogno, who wrote the coding algorithm for the registration key and translated in English this documentation. - Luca Leone, who gave me all kinds of technical infos about FrontDoor functioning. - Marcello Ardini, who gave me useful ideas to better manage files. - ....all ye that I forgot, and whom my most sincere Grazie! is given. Pag. 1 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 LICENSE AGREEMENT WMail is neither Public Domain software nor Freeware: it is distributes as Shareware. So, after a trial period, the user is asked to register his/her copy sending the due amount of money to the author. Note that this version of WMail is not limited in lifetime: it will continue to work even without registration. Nevertheless, some secondary functions are only accessible after registering and receiving one key. To register WMail it is necessary fill in and send to the following address the form you can find in the distribution archive; an amount of money is also required, to be sent through a postal money order to the author. The registration key is valid for this and all future versions of WMail; two types of registration are possible, see registration form for any detail. Everyone can redistribute WMail, provided that the original archive is not changed in any way and no amount of money is required. In no circumstance at all WMail can be modified without author's permission; it is prohibited too to include this program, whole or in part, in other software. It is expressly forbidden distribute the personal registration key to other people. WMail can be used in commercial organizations only after regular registration. This license is considered accepted if the program is used: its violation will involve the withdrawal of the registration key and the rights to use the program. No WMail source, of whichever of its version, will be ever released. In no case the author shall be liable for data loss or whatever relative to WMail use; i.e., no guarantee at all is given about program functioning, except that it occupies disk space. Everyone who uses WMail and finds any functioning problem is kindly asked to report them at Fidonet address 2:334/100.2 : time permitting, everyone will be answered. Silvan Calarco, FidoNet 2:334/100.2 V. Leonardo da Vinci 177 10095 GRUGLIASCO (Torino) ITALIA Pag. 2 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 INSTALLATION In WMail distributing archive the following files are contained: WMAIL.EXE Executable program WMSETUP.EXE Configuration program WMUPDATE.EXE Upgrade program from version 2.2 WNODE22.ARJ Nodelist compiler WMAIL.DOC This documentation REGISTER.FRM Registration form HISTORY.DOC WMail previous versions WMSTRUCT.230 Structures of the files used by WMail README.1ST Note to upgrade from WMail 2.2 To install WMail: 1) Unpack WMAIL.EXE , WMAIL.OVR , WMSETUP.EXE in the directory where the current mailer is used. 2) Run the window setup WMSETUP.EXE and configure WMail for your system. 3) Correct or add in CONFIG.SYS the following line: FILES=30 (for a point environment) FILES=40 (or more, for a Bbs environment) 4) Add in your AUTOEXEC.BAT file the following line: SET WMAIL=path where path is the directory where WMail searches for the configuration file and memorizes dupes and statistics files. 5) Modify the batch file of EchoMail processing, so that they call WMail. Pag. 3 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 CONFIGURATION WMail gets the informations needed to know system configuration from a file called WMAIL.PRM, located in the directory pointed by the WMAIL system variable. This file is created from WMSETUP.EXE . Areas definition is taken from AREAS.PRM, used by WEdit 1.3 or greater too. WmSetup & WMail will look for AREAS.PRM in the directory pointed by the WMAIL system variable; if not found, il will be searched in the WEDIT system variable. Nodes definition is taken from NODES.PRM. WMSETUP.EXE Syntax : WMSETUP [switches] ? : Show a help screen. -Afile : Use file 'file' as areas file instead of AREAS.PRM. -Nfile : Use file 'file' as nodes file instead of NODES.PRM -Pfile : Use file 'file' as configuration file instead of WMAIL.PRM READAREAS file : Import textual file 'file' into binary areas configuration (AREAS.PRM). WRITEAREAS file: Export binary areas configuration (AREAS.PRM) to textual file 'file'. File * DOS Shell Allows to spawn a shell and temporarily leave WMSETUP.EXE . * Write setup Writes the present configuration in a text file. * Write areas Writes all defined areas in a AREAS.BBS style file. * Write route Writes a sample routing file for a point environment. Pag. 4 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 * Import areas Imports AREAS.BBS file in AREAS.PRM . * Save options Save the current configuration. * Exit Exits WMSETUP.EXE and saves WMAIL.PRM & AREAS.PRM . Pag. 5 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 Global * User - Sysop Specifies name (and surname) which will be substituted in NetMail inbound messages addresses to `Sysop'. * User - Key Specifies registration key number; if your WMail version is not registered, leave blank this field. * Address - Main Specifies the primary address associated to node or point. If you do not have such, DO NOT invent it! Ask rather one to the Net coordinator nearest to you. A fake or non-standard node number can cause serious problems to Echomail distribution network. * Address - Aka 1-10 Specifies all secondary matrix addresses, if assigned. Akas will be used to recognize the destination addresses of any incoming packet or message. * ZoneGate - Zonegate 1-10 Specifies the forward node, which is a gate to a different zone with respect to the one specified in Node instruction. All SEEN-BY lines from messages passed to ZoneGate will be stripped off. * Directory - Mail Specifies the path in which WMail will put NetMail inbound messages and will create attach messages for FrontDoor, if it is working in this manner. Final backslash can be omitted. * Directory - Files Specifies the path in which WMail will search for FrontDoor and .PKT files to elaborate in input phase. Final backslash can be omitted. * Directory - Packets Specifies path in which .PKT files to be compacted in Export Pag. 6 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 phase are created. It also specifies the path in which .OUT files are put, which will be further elaborated by PACK function, if WMail is configured in BinkleyTerm modality. If, on the contrary, it is configured in FrontDoor modality, it is best to use a ramdisk: in this way execution time is greatly reduced. Final backslash can be omitted. * Directory - ARCmail Specifies path in which ARCmail files created during Export phase will be stored. This instruction is only needed if WMail is used in environments which a packer is not required, e.g. with D'Bridge or FrontDoor. PLEASE NOTE: If WMail is used in Binkley modality (so that .OUT files are created for further elaboration with PACK), this field must remain blank. Final backslash can be omitted. * Directory - MsgBase Specifies the path in which WMail creates MSG*.BBS files, relative to QuickBBS data base. This instruction is only necessary if such areas are specified in AREAS.PRM . Final backslash can be omitted. * Directory - DupPath Specifies the path in which dupe messages are put. If not specified, these messages will be deleted during Import phase. Final backslash can be omitted. * Directory - BadEcho Specifies the path in which messages with bad data, relative to areas not present in AREAS.PRM or coming from nodes not listed in AREAS.PRM are put. If unspecified, these messages will be deleted during Import phase. Final backslash can be omitted. * Directory - Packer Specifies the path in which WMail searches for packers and unpackers. Final backslash can be omitted. * Directory - Stats Specifies the path in which WMail creates statistics files. Pag. 7 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 If unspecified, the current directory will be used. Final backslash can be omitted. * Directory - New areas Specifies the path from which subdirectories relatives to areas with tag not present in areas file will be created, if new Fido areas creation is set. Final backslash can be omitted. * Directory - Nodelist Specifies the path of nodelist files created from WNode. If not else configured, WNode will read this field before compiling the nodelist. Final backslash can be omitted. * Origin 1-10 Specifies a set of lines to be inserted as Origin in EchoMail messages who don't have it. NOTE: no control is made to check if this content plus FidoNet address, which WMail automatically inserts, exceed 79 characters. Manager * Defaults - Put origin If set to `Yes' all new areas will have `Put origin' flag set to `Yes'. * Defaults - Put tear line If set to `Yes' all new areas will have `Put tear line' flag set to `Yes'. * Defaults - Hide seen-by If set to `Yes' all new areas will have `Hide seen-by' flag set to `Yes'. * Defaults - Strip 4d If set to `Yes' all new areas will have `Strip 4d' flag set to `Yes'. Pag. 8 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 * Defaults - Add aka's If set to 'Yes' all new areas will have 'Add aka's' flag set to 'Yes'. * Defaults - Put domain If set to `Yes' all new areas will have `Put domain' flag set to `Yes'. * Defaults - Force public If set to `Yes' all new areas will have `Force public' flag set to `Yes'. * Defaults - Force private If set to `Yes' all new areas will have `Force private' flag set to `Yes'. * Defaults - 4d point infos If set to `Yes' all new areas will have `4d point infos' flag set to `Yes'. * Packers - ARC Defines name and command-line parameters of ARC packer. * Packers - ARJ Defines name and command-line parameters of ARJ packer. * Packers - LZH Defines name and command-line parameters of LZH packer. * Packers - PAK Defines name and command-line parameters of PAK packer. * Packers - ZIP Defines name and command-line parameters of ZIP packer. * Packers - ZOO Defines name and command-line parameters of ZOO packer. Pag. 9 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 * Packers - SQZ Defines name and command-line parameters of SQZ packer. * Packers - Default Press F1 to make current packer as default packer; it will be used when a node is not configured for packing. * Unpackers - ARC Defines name and command-line parameters of ARC unpacker. * Unpackers - ARJ Defines name and command-line parameters of ARJ unpacker. * Unpackers - LZH Defines name and command-line parameters of LZH unpacker. * Unpackers - PAK Defines name and command-line parameters of PAK unpacker. * Unpackers - ZIP Defines name and command-line parameters of ZIP unpacker. * Unpackers - ZOO Defines name and command-line parameters of ZOO unpacker. * Unpackers - SQZ Defines name and command-line parameters of SQZ unpacker. * Nodes - Node Specifies node for which packer, Areafix password and Areafix level are declared. * Nodes - Packer Allows to select which packer, among those above declared, should be used for that node in Export and Pack phases. Pag. 10 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 * Nodes - Packet Pw Specifies the password to check for in incoming packets and to put in exported packets. * Nodes - Areafix Pw Specifies the password which that node will have to use when sending messages to Areafix. * Nodes - Level Specifies the level of the node with respect to Areafix: a node can change areas file only for those areas whose level is less than or equal to the one specified in this field. * Nodes - Aka Specifies which AKA, among those above declared, is to be used to communicate with current node. * Nodes - Daily pkts Specifies if WMail must create an ARCMail file for every day or continue adding to the existing one, if any. * Areas - Status Specifies the status of the area. When set to 'Inactive', area will be ignored by WMail and WEdit. * Areas - Descr. Specifies area description. * Areas - Kind Specifies the kind of area: Local, NetMail, EchoMail or Passthru. Local and NetMail areas are ignored by WMail. * Areas - Tag Specifies the tag of the area. * Areas - Dir Specifies the path or msgbase board for the current area. Pag. 11 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 * Areas - Level Specifies the level of the area with respect to Areafix function. * Areas - Origin Allows to select which origin, among those above declared, should be used for this area. * Areas - Flags - Put origin If set to `Yes', WMail during Export phase will always substitute the possible origin found in the message with the selected one. * Areas - Flags - Put tear line If set to `Yes', WMail during Export phase will always substitute the possible tearline found in the message with the selected one. * Areas - Flags - Hide seen-by If set to `Yes', WMail will hide in imported messages Seen-by lines preceding them with a ^A. * Areas - Flags - Strip 4d If set to `Yes', WMail will remove from PATH lines 3d addresses indicating 4d points. This option has effect only on boss nodes. * Areas - Flags - Add aka's If set to 'Yes', WMail will add all aka's specified of the same zone in seen-by lines. * Areas - Flags - Put domain If set to `Yes', WMail will insert domain in message origin line. * Areas - Flags - Force public If set to `Yes', WMail will set as public any message imported. * Defaults - Force private Pag. 12 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 If set to `Yes', WMail will set as private any message imported. * Defaults - 4d point infos If set to `Yes', WMail will put point address in path and seen-by lines. This option has effect only on 4d points. * Areas - Aka Specifies Aka and domain to be used in present area. * Areas - Frwd. 1-3 Specify the nodes, in sequence as in a AREAS.BBS line, to which export current area. Misc * General - Mailer Specifies the modality WMail will operate in: BinkleyTerm, FrontDoor (also known as ARCmail modality). * General - Fake net Specifies fakenet used to individuate points: during Export phase, WMail will remove all SEEN-BY lines relative to nodes with net equal to the declared one, to avoid conflicts with official nodes of a net. In this way, points can be managed in a compatible way with EchoMail processors which cannot recognize 4-dimension address. WMail is so able to manage both modalities. This instruction has to be used both on boss node and on the point which uses fake address. * General - Import dupes If set to `Yes', WMail will put in the declared directory dupe messages; they will be otherwise deleted during Import phase. * General - Import bad If set to `Yes', WMail will put in the declared directory messages corrupted, relative to areas not present in areas definition or coming from nodes not listed in Frwd. 1-3 field of area; they will be otherwise deleted during Import phase. Pag. 13 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 * General - Stats If set to `Yes', WMail will generate monthly/weekly/yearly statistics. * General - Log file If set to `Yes', WMail will create a logfile. * General - Minimum space Specifies minimum space (in KBytes) on disk, under which WMail will make no operation. * General - Swap Specifies whether and how swap should be performed during packing and unpacking: EMS : swap on expanded memory Disk : swap on disk No : no swap If EMS swap was specified and there is not enough EMS present, swap will be made on disk, anyway. * General - Use nodelist If set to `Yes', WMail will use nodelist to indicate names of BBS to which it is exporting messages. * General - Create areas Specifies whether or not WMail would create subdirectories (or use unused QuickBBS msgbase boards) to areas with tags not present in areas definition, and found during import. * General - Honor RRRs Specifies whether or not WMail would reply to NetMail messages with Return Receipt Request flag set. * General - Link tear line If set to 'Yes' WMail will add its tear line to the existing one in the following way: Tl1+'+'+Tl2 . * Files - Log File Pag. 14 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 Specifies the name of log file. * Files - Style Specifies the writing style of log file: FrontDoor : logfile style like FrontDoor BinkleyTerm : logfile style like BinkleyTerm * Files - Level Indicates how much information should be reported in logfile. * Files - Rescan file Specifies the name of the file to consider for rescan (such as FDRESCAN.NOW). * Areafix - Kill msgs. If set to `Yes', WMail will delete messages to Areafix after processing them. * Areafix - Sort nodes If set to `Yes', WMail will sort nodes in Frwd. 1-3 field of areas definition during AREAS.PRM rewriting. * Areafix - Short form If set to `Yes', WMail will use in Frwd. 1-3 fields of areas definition the short address form: for example, 334/100 101 102 instead 334/100 334/101 334/102 . * Areafix - Allow rescan Specifies if user-requests areas rescan is allowed. * Areafix - List file Specifies the file sent together with the answer file when Areafix message has switch -L . * Areafix - Link nodes Specifies the list of the nodes to link to any new area automatically created either by areafix or during import. Pag. 15 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 * Areafix - Creating nodes Specifies the list of the nodes that can create new areas either with an areafix request or during import. * Areafix - Alert nodes Specifies the list of the nodes to alert of any areafix operation. * Areafix - Messages Flags - Crash Set crash bit in answer messages. * Areafix - Messages Flags - Hold Set hold bit in answer messages. * Areafix - Messages Flags - Kill/sent Set kill/sent bit in answer messages. * Pack - Kill msgs. If set to `Yes', WMail will kill messages with `In transit' flag after sending them, if mailer did not make it. * Pack - Route file Specifies the routing file name to be used in PACK function. * Colors - Default Set default colors for windows and texts. * Colors - Mono Set mono colors for windows and texts. * Colors - WMail 2.2 Set the same colors used by WMail 2.2 for windows and texts. * Colors - Customize Customize any color as you prefer. Pag. 16 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 EXECUTION WMail has 7 main functions : IMPORT EXPORT PACK SETMARK HIMARK WRITESTATS AREAFIX General syntax is : WMail <function> [switches] For each function, a help screen is available by digitizing: WMail <function> ? Pag. 17 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 FUNCTIONS DESCRIPTION -- IMPORT Function -- Unpacks received ARCmail and puts messages from .PKT in the appropriate areas. -- EXPORT Function -- Prepares .PKT with outbound messages and packs them as ARCmail. -- PACK Function -- Packs NetMail messages together with EchoMail ones and sets routing of the created files. -- SETMARK Function -- Sets High Water Mark (flag of last elaborated message) at specified message (only for Fido format areas). -- HIMARK Function -- Sets High Water Mark at last message present in area (only for Fido format areas). -- WRITESTATS Function -- Creates statistics files about Echomail traffic. -- AREAFIX Function -- Manages areas file (AREAS.PRM) in an automatic way. Pag. 18 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 USE OF WMAIL The following is a description of all switches allowed in the various functions. -- IMPORT WMail will automatically choose the unpacker to be used for the various ARCmail packets. Unpackers *must* be found in the Global - Directory - Packer path set in WMSETUP.EXE . Syntax : WMAIL IMPORT [switches] -Afile : Use file 'file' as areas file instead of AREAS.PRM. -D : Deletes messages without text part. -E : Exports messages to all other nodes. -Ffile : Create file `file' with the name of the areas in which messages came. -I : Import from BadEcho -Nfile : Use file 'file' as nodes file instead of NODES.PRM. -Pfile : Use file 'file' as configuration file instead of WMAIL.PRM -Q : Quiet mode; minimizes output information to video. -S : Sets up security. If some area is in Quickbbs format, it is advisable to use -E switch to speed Export procedure. Pag. 19 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 -- EXPORT Syntax : WMAIL EXPORT [switches] -Afile : Use file 'file' as areas file instead of AREAS.PRM. -Ffile : Forces WMail to scan only areas with tag specified in `file'. -Nfile : Use file 'file' as nodes file instead of NODES.PRM. -Pfile : Use file 'file' as configuration file instead of WMAIL.PRM -Q : Quiet mode; minimizes output information to video. -R : Exports private messages as NetMail. -S : Forces scan of the whole QuickBBS message base. If present, ECHOMAIL.BBS is deleted. Pag. 20 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 -- PACK Syntax : WMAIL PACK [switches] -Afile : Use file 'file' as areas file instead of AREAS.PRM. -C : Forces WMail not to compress generated packets. -F : Forces WMail not to rescan for every packet. -Nfile : Use file 'file' as nodes file instead of NODES.PRM. -Pfile : Use file 'file' as configuration file instead of WMAIL.PRM. -Q : Quiet mode; minimizes output information to video. -Stag : Executes schedule `tag' from routing file. WMail by default reads schedule '@'. Pag. 21 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 -- SETMARK Syntax : WMAIL SETMARK dir num_msg dir : Area path. num_msg : number of message where HWM is to be moved. -- HIMARK Syntax : WMAIL HIMARK dir dir : Area path. -- WRITESTATS Syntax : WMAIL WRITESTATS [switches] -Afile : Use file 'file' as areas file instead of AREAS.PRM -Y : Creates statistics file only for current year. -M : Creates statistics file only for current month. -Pfile : Use file 'file' as configuration file instead of WMAIL.PRM -W : Creates statistics file only for current week. Pag. 22 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 -- AREAFIX Syntax : WMAIL AREAFIX ADD node area1 area2 ... [switches] WMAIL AREAFIX DEL node area1 area2 ... [switches] WMAIL AREAFIX FIND node [switches] WMAIL AREAFIX EC [switches] │ ADD : Add node (Net/Node.Point) to stated areas. │ │ DEL : Delete node from stated areas. │ You can remove node from link by │ specifying 'ALL_AREAS' as area1. │ │ EC : Process NetMail messages addresses to │ Areafix and updates areas file. │ │ FIND : List areas hooked to specified node. -Afile : Use file 'file' as areas file instead of AREAS.PRM -Nfile : Use file 'file' as nodes file instead of NODES.PRM. -Pfile : Use file 'file' as configuration file instead of WMAIL.PRM -Q : Quiet mode; minimizes output information to video. Pag. 23 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 ROUTING Routing determines the kind of packets prepared from WMail during PACK phase, and nodes to which they will be sent. Note that a wrong routing procedure can cause calls not scheduled by mailer; be therefore careful about the structure of routing file and mailer events. Global routing commands are those which appear before every SCHEDULE declaration in route file. These are always used, so it is possible to specify situations identical for each event. Local routing commands are those which appear between two SCHEDULE declaration in route file. WMail determines which `block' of commands is to be used, by searching for the schedule corresponding to the letter specified with -S switch in command line. If no letter is specified, WMail search by default `@' schedule. Every line starting with a semicolon is considered a comment. Addresses specified in routing file can be written in short form, by using declaration ALL. To list several systems in a net, it is sufficient to specify net number for the first declared node. Routing language is completely case insensitive: SEND, send, and SenD are considered the same command. To preserve compatibility with FrontDoor, any character after '!' is ignored. -- Default routing WMail has some default rules for routing; they will be used if no other rule is specified for a particular message. Some of default rules cannot be substituted by routing commands. ■ Messages with crash, direct and hold flags set will not be routed towards other nodes. In Binkley modality they will never be packed as ARCmail; they will be exported as *.?UT packets. ■ Only normal messages, with no crash, direct and hold flags, are packed as ARCmail and respect routing rules. In Binkley modality *.?LO attack files are created. ■ In binkley modality orphan ARCmail packets are always sent to destination node. ■ Messages with received, orphan, lock or sent flags are always ignored by WMail. ■ In FrontDoor modality, file attacks, file requests and IMMediate messages are ignored by WMail. Pag. 24 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 -- System definitions It is possible to define a system, by putting a SEND-TO command in the global section of the routing file, but this is not always suitable. SEND-TO, POLL and the list SEND-LIST after a schedule command are the only ways to declare a system to exchange mail. Messages to nodes non present in these declaration are ignored. -- Routing commands WMail routing can be done in two different ways: * In FrontDoor compatibility, by using the same routing file and by creating a file attack message for packed mail. This is the default. Note that to preserve compatibility, user should avoid to use any verb. * In Binkley compatibility, by using extended commands in routing file, and by creating files NNNNnnnn.?LO in case of file attach, NNNNnnnn.?UT for unpacked packets and NNNNnnnn.REQ for file requests. Packets for zone other than the default one, will be put in directory outbound.zzz, where 'outbound' is outgoing packets directory, and zzz is the hex destination zone number (E.g. If you are in zone 2 and your outbound subdirectory is C:\Outbound, packets for zone 39 will be put in C:\Outbound.027). In the following commands, VERB declarations are optional and useful for the operations in Binkley modality, and include these commands: Verb Extension of created files ---- -------------------------- NORMAL FLO or OUT CRASH CLO or CUT HOLD HLO or HUT DIRECT DLO or DUT EXPRESS CUT For the meaning of these declarations, please refer to BinkleyTerm manual, as they are used by this mailer. In Binkley compatibility, it is possible to tell WMail NOT to pack outbound mail, by putting -N switch in the command line. In the following, the routing file commands are presented: SCHEDULE <TAG> [VERB] [SEND-LIST] Defines the start of a command block. All commands following a schedule declaration are considered in the same block, until another schedule declaration or the end of file. TAG is an alphanumeric character. Each character can be used in Pag. 25 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 at most a tag. Optional parameter VERB, used in Binkley modality, specifies the kind of file .?LO or .?UT which will be created for nodes specified in SEND-LIST. Optional parameter SEND-LIST contains systems concerned by schedule. SEND-TO [VERB] <SEND-LIST> Defines the systems listed in SEND-LIST which receive mail in the way specified by VERB. VERB and SEND-LIST options are similar to those in SCHEDULE declaration. HOLD <LIST> Keep mail for specified systems. It is the equivalent of the command SEND-TO HOLD <SEND-LIST>. Hold mail is not sent, unless the receiving node makes a call. UNHOLD <LIST> The opposite of HOLD. It is useful in case of global declaration in HOLD command, if one or mode nodes should be excluded by the effect of the command. ROUTE-TO [VERB] <TARGET> <LIST> Route mail (except file attach messages) for nodes specifies in LIST to node specified in TARGET. In Binkley modality, VERB sets the way in which mail must be created for TARGET node. NO-ROUTE <LIST> Sends directly mail to nodes specified. This command can be used to negate effect of ROUTE-TO to one or more nodes, in case of global declarations. ROUTE-FILES [VERB] <TARGET> <LIST> Routes file attach messages (but not the standard mail) of nodes specified in LIST to node specified in TARGET. Destination node must know of it in order for file attach to work; it is therefore necessary to ask that node's Sysop if he or she lets files be routed through his/her system. POLL [VERB] <LIST> Pag. 26 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 Forces mailer to call systems specified even if no other mail addressed to them is present. This command, used in FrontDoor modality, is equivalent to SEND-TO, as it is the mailer who calls concerned nodes, while if used in Binkley modality fake files are created, according to VERB parameter: Verb Fake POLL file ---- -------------- NORMAL NNNNnnnn.OUT CRASH NNNNnnnn.CUT HOLD NNNNnnnn.HUT DIRECT NNNNnnnn EXPRESS NNNNnnnn.CUT N.B. In Binkley modality it is necessary that files present in LIST don't contain global declarations (ALL or *). EXCEPT <LIST> Specifies exceptions to the list of nodes, in the above commands. Multiple EXCEPT lines are supported. EXCEPT statements always follow a command and can be put either after this command or in a new line. E.g."ROUTE-TO 334/100 * EXCEPT 334/101" N.B.: The following commands are useful only in Binkley modality: ----------------------------------------------------------------- CHANGE <TO-VERB> <LIST> Changes the way in which packets are sent, by modifying extensions of .?LO and .?UT files for nodes present in LIST, on the basis of TO-VERB parameter. For example, CHANGE HOLD 1/1 would have the following effect: 00010001.?LO --> 00010001.HLO 00010001.?UT --> 00010001.HUT LEAVE <LIST> LEAVE command makes unavailable for mailers the packets already created for nodes present in LIST, by changing their extension. This is useful to avoid sending of mail to a calling node during some events. This command is similar to FrontDoor's DENY, which is however useless with WMail, as it is managed by mailer. Files are renamed in this way: NNNNnnnn.?UT --> NNNNnnnn.N?T NNNNnnnn.?LO --> NNNNnnnn.N?O UNLEAVE <LIST> Pag. 27 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 UNLEAVE command renames again packets whose name was changed by LEAVE command, restoring the original extension. Files are renamed in this way: NNNNnnnn.N?T --> NNNNnnnn ?UT NNNNnnnn.N?O --> NNNNnnnn ?LO -- Specifications for node lists It is possible to use a number of different formats to specify a list of systems in routing commands: ALL All systems. 2:ALL All systems in zone 2. 2:334/ALL All systems in zone 2, net 334. 2:334/1 101 102 2:334/1 2:334/101 and 2:334/102. .1 .2 .3 .4 .5 Own points 1, 2, 3, 4 and 5. NOTE: Instead of ALL it can be used a star `*'. To preserve compatibility with FrontDoor 2.x the use of `*' is strictly necessary. -- Note about points Points from other systems are always treated as their boss. Systems can send mail only to other nodes and to its own points. -- Routing philosophy * Commands are interpreted sequentially, so that any statement can be modified by the next ones. E.g.: SEND-TO DIRECT 334/100 SEND-TO CRASH 334/100 Messages are sent to 334/100 as CRASH. In its internal reasoning WMail first flags messages for 334/100 as DIRECT, and then as CRASH. * When you use ROUTE-TO and ROUTE-FILES commands, remember to exclude all nodes which are not to be routed, as they have effect in any position of Global and Local routing. E.g.: ROUTE-TO 334/100 332/400 SEND-TO CRASH 332/400 The second statement has no effect, as after first line all Pag. 28 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 messages addressed 332/400 are considered for 334/100. ROUTE-TO 334/100 * EXCEPT 332/400 SEND-TO DIRECT 332/400 NO-ROUTE 332/400 ROUTE-TO 334/100 * In these two cases messages will not be routed to 332/400. -- Examples * Example 1: a Binkley system with points (fakenet is 22402) SCHEDULE @ NORMAL ALL ; This schedule looks at all ; nodes and sends by default ; messages as NORMAL SEND-TO HOLD 22402/* 332/305 SEND-TO CRASH 332/309 334/100 ROUTE-TO DIRECT 332/404 * EXCEPT 334/100 332/309 332/305 22402/* All message will be routed to 332/404 except for specified nodes. Messages for points and for 332/305 will be flagged as HOLD. Messages for 332/309 and 334/100 will be flagged as CRASH. * Example 2: a FrontDoor system with 4 dimensions points ROUTE-TO 2:334/0 2:* ; Send all zone 2 messages to 2:334/0 ; except for points messages ROUTE-TO 2:33/999 * ; Send all other zones messages to ; 2:33/999 HOLD * ; Holds all messages SCHEDULE A 334/101 ; Look only at messages for 334/101 NO-ROUTE 334/101 ; Do not route messages for 334/101 POLL 334/101 ; but call the system everyday. SCHEDULE B 2:* ; Look at all messages UNHOLD 2:33/999 ; Unhold messages for 2:33/999 DENY 334/100.* ; Prevent points from picking up mail * Example 3: a Binkley point system (created by WMSetup) SCHEDULE @ DIRECT * ROUTE-TO DIRECT 2:334/100 * 1st line is used to qualify system to send mail everywhere 2nd line is used to send all netmail to boss system Pag. 29 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 HOW AREAFIX WORKS The automatic management of areas file is accomplished by means of NetMail messages sent to "Areafix"; in the message subject it must be put the password assigned to the node which sent the message. The message text must contain the list of areas, one for each line and starting in column 1, to be added or deleted. The character `-' (minus) before the area tag means that areas should be deleted. Message text ends with a line containing a triple dash `---'. For ex. From : Silvan Calarco of 2:334/100.2 To : Areafix of 2:334/100.0 Subj : My_Password ________________________________________________________________ MSD_HARD.ITA -CLANG.ITA --- The previous message instruct WMail to add to Silvan Calarco's node, to which password `My_password' was assigned, area MSD_HARD.ITA, while area CLANG.ITA will be deleted. If in subject there is a `-L' after the password (separated by a blank), WMail will send to the node the list of EchoMail areas for which adding is allowed. If -Q is used instead, areas list will be sent as a message. If in subject there is a `-R' a rescan of added areas will be done, so that old messages will be forwarded too. Note that rescan will not work for QuickBBS areas, if they have already been scanned for export. Pag. 30 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 OTHER FUNCTIONS -- Return receipts WMail is able to honor return receipt requests if desired (see CONFIGURATION chapter). Receipt messages will be created during any netmail scan; WMail will check either for RRQ bit in message header and for extended flag RRQ; besides receipts will not be created in the case that messages have already been replied to. -- Security *Packets with a password different than the one specified in setup will not be imported and will be renamed as 'BAD_PKT.nnn' if switch -S is set in import. *Messages from PKTs with different destination from the addresses specified as primary or AKAs will be imported in Badecho directory. To force WMail ti import wrong addressed packets, it is necessary to specify in WMSETUP, as an AKA, the address reported in log file as 'Wrong address'. *EchoMail messages coming from nodes not linked to the interested area, will be put in Badecho area if switch -S is set in import. *To import messages from BadEcho area switch -I must be specified on command line; during this phase, only messages coming from nodes linked to the interested area will be moved. -- New areas creation WMail is able to automatically create new areas, if desired (see CONFIGURATION chapter), during import and areafix phases. Only nodes specified as 'Creating nodes' in setup are allowed to do this. New areas will be created with an areafix level of 200. Pag. 31 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 TECHNICAL NOTES * PKT with extended header WMail generates type 2+ PKTs, with extended header, according to standard proposed in FSC-0039 and FSC-0048. In the new header structure, zone provenance and destination of PKT and origin and destination point are included. Due to compatibility problems with these FSCs WMail creates packet headers according to FSC-0048, and imports packets according to FSC-0039. * Product Code The present WMail product code is 0x77 (119 dec). * Areas The largest number of areas that WMail can manage is 1000. * New Areas The largest number of new areas that can be created in one session is about 50. * Nodes The largest number of nodes managed by WMail is 8192. * Dupes The largest number of dupes managed by WMail per area is 1000. * MSGID WMail inserts MSGID in messages which lack of it. * PID and Tear-line In the tear-line WMail will add after its identificative "WMail 2.3" the number of registration key; if tear-line is not WMail's, it will put at the start of the message and hidden with a ^A a line of Product Information (PID) with the same informations. * Illegal registration keys WMail will not import messages whose tear-line or PID contains a key similar to the one specified in WMAIL.PRM. It is therefore Pag. 32 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 impossible to use key assigned to other copies. * Attack messages In attach messages for ARCmail, WMail inserts DIR and TFS extended flags, so that FrontDoor and compatible mailers can better handle them. * Directory creation WMail will automatically create any new outbound directory it will need for export and pack functions; such are zone directories (e.g. OUTBOUND.05F) and point directories (e.g. 014C0192.PNT). * Memory occupation Thanks to its capability to swap code on disk or EMS during external programs (packer and unpacker) execution, WMail can run in about 280 Kb. Overlay file is loaded in EMS, if it is present. * ARCMail processing order To process ARCmail and PKTs Dos file date is used to determine which packet is to be imported first. * Maximum message length The maximum length of a message is virtually infinite: messages longer than available memory are temporary swapped to disk. * Execution errors In case of run-time error, WMail will create a file WMAILERR.LOG in which date, time and kind of the error are reported. * Limitations in unregistered copies If WMail is used without a registration key, Areafix function, weekly/monthly statistics, nodelist use, new areas creation and Return Receipt messages will not be operative. Yearly statistics will work. * Limitations in point registered copies If WMail is used with a point registration key, only Areafix function will not be operative. Besides, a point key will not Pag. 33 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 work with a BBS address. * QuickBBS files sharing WMail will lock message base file access during Import phase. * ARCmail naming convention WMail 2.3 does no more create P*.* ARCmail files. In FrontDoor modality a CRC-32 of the two complete addresses (origin and destination) will be the name of the packets; in BinkleyTerm modality any name will be calculated by considering the first AKA of the interested zone. * Video mode WMail and WMSetup will keep any text video mode by adapting the size of their windows to the current number of video lines. * Technical support An ECHO conference on node 2:334/100.0 is activated, with tag WMAIL.334 and dedicated to W* products; to hook it, please contact SysOp of 2:334/100.0 Pag. 34 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 EXAMPLES OF BATCH FILES 1) Bbs : Opus Mailer : BinkleyTerm Rem File Batch to use WMail with Opus and BinkleyTerm Rem ------------------------------------------------- Rem :Start Bt If Errorlevel 200 Goto Export If Errorlevel 24 Goto 2400_Baud If Errorlevel 12 Goto 1200_Baud If Errorlevel 10 Goto Import If Errorlevel 3 Goto 300_Baud If Errorlevel 1 Goto End Goto Start :2400_Baud Opus Bbs -b2400 Goto Start :1200_Baud Opus Bbs -b1200 Goto Start :300_Baud Opus Bbs -b300 Goto Start :Import WMail Import WRemap Goto Start :Export Wmail Export WMail Pack Goto Start :End Echo Bbs OffLine ! 2) Bbs : QuickBBS Mailer : BinkleyTerm Rem File Batch to use WMail with QuickBBS and BinkleyTerm Rem ----------------------------------------------------- Rem :Start Bt If Errorlevel 200 Goto Export If Errorlevel 24 Goto 2400_Baud If Errorlevel 12 Goto 1200_Baud If Errorlevel 10 Goto Import Pag. 35 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 If Errorlevel 3 Goto 300_Baud If Errorlevel 1 Goto End Goto Start :2400_Baud QuickBBS -B2400 Goto Start :1200_Baud QuickBBS -B1200 Goto Start :300_Baud QuickBBS -B300 Goto Start :Import WMail Import WRemap MbUtil Import Goto Start :Export Wmail Export -S MbUtil Export WMail Pack Goto Start :End Echo Bbs OffLine ! 3) Bbs : Opus Mailer : FrontDoor Rem File Batch to use WMail con Opus and FrontDoor Rem -------------------------------------------------- Rem :Start Fd If Errorlevel 240 Goto 2400_Baud If Errorlevel 200 Goto Export If Errorlevel 120 Goto 1200_Baud If Errorlevel 100 Goto Import If Errorlevel 31 Goto 300_Baud If Errorlevel 10 Goto End Goto Start :2400_Baud Opus Bbs -b2400 Goto Start :1200_Baud Opus Bbs -b1200 Goto Start Pag. 36 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 :300_Baud Opus Bbs -b300 Goto Start :Import WMail Import WRemap Goto Start :Export Wmail Export Goto Start :End Echo Bbs OffLine ! 4) Bbs : QuickBBS Mailer : FrontDoor Rem File Batch to use WMail with QuickBBS and FrontDoor Rem --------------------------------------------------- Rem :Start Fd If Errorlevel 240 Goto 2400_Baud If Errorlevel 200 Goto Export If Errorlevel 120 Goto 1200_Baud If Errorlevel 100 Goto Import If Errorlevel 31 Goto 300_Baud If Errorlevel 10 Goto End Goto Start :2400_Baud QuickBBS -B2400 Goto Start :1200_Baud QuickBBS -B1200 Goto Start :300_Baud QuickBBS -B300 Goto Start :Import WMail Import WRemap MbUtil Import Goto Start :Export Wmail Export -S MbUtil Export Goto Start Pag. 37 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 :End Echo Bbs OffLine ! 5) Bbs : Opus and QuickBBS Mailer : FrontDoor Rem File Batch to use WMail with areas in Opus and QuickBBS Rem format with FrontDoor Rem ------------------------------------------------------- Rem :Start Fd If Errorlevel 240 Goto 2400_Baud If Errorlevel 200 Goto Export If Errorlevel 120 Goto 1200_Baud If Errorlevel 100 Goto Import If Errorlevel 31 Goto 300_Baud If Errorlevel 10 Goto End Goto Start :2400_Baud QuickBBS -B2400 Goto Start :1200_Baud QuickBBS -B1200 Goto Start :300_Baud QuickBBS -B300 Goto Start :Import WMail Import WRemap MbUtil Import Goto Start :Export Wmail Export -S MbUtil Export Goto Start :End Echo Bbs OffLine ! --------- Opus, BinkleyTerm, FrontDoor and D'Bridge are trademark of their respective authors. Pag. 38 WMail 2.3 - Copyright 1990-92 Silvan Calarco 12/28/92 ** End of Documentation ** Pag. 39