ProfitPress Mega CDROM2 Shareware Freeware (MSDOS)(1992)(Eng)

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

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / BBS / OPUS / OMMM_170.ZIP / OMMM.DOC < prev next >

Wrap

Text File | 1991-06-18 | 100.7 KB | 2,767 lines

OOOOO MM MM MM MM MM MM OO OO MMM MMM MMM MMM MMM MMM OO OO MMMMMMM MMMMMMM MMMMMMM OO OO MM M MM MM M MM MM M MM OO OO MM MM MM MM MM MM OO OO MM MM MM MM MM MM OOOOO MM MM MM MM MM MM THE OPUS MATRIX MESSAGE MASHER For use with Opus CBCS Processes, compresses, routes and sends mail according to operator specifications. Version 1.70 July 14, '91 Table of Contents Introduction................................. 3 If You're New to OMMM or the Matrix New Setup from Scratch................ 4 The OMMM Configuration File........... 5 Command Line Switches................. 8 Setting up Errorlevels................ 9 OMMM Scheduling....................... 10 Working with HOLD & UNHOLD Verbs...... 11 The PreScanFile....................... 13 The Routefile......................... 14 ShortHand Commands.................... 16 News for Grizzled Veterans Day and Time in your Config........... 18 Day Stamping Extensions............... 19 Support for Points.................... 19 File Requests/File Attaches .......... 20 OMMM and OMMM286...................... 20 New Zone Commands..................... 20 Replaced Commands..................... 21 Zone Awareness Setup................................. 22 After a Zone message is entered....... 24 TechnoTalk How OMMM does what it does............ 25 Indexes Index A - Config Commands/Switches.... 28 Index B - Mail Packet Extensions...... 32 Index C - Schedule Verbs.............. 33 Index D - Dec/Hex Chart............... 39 Legal Department............................. 40 Glossary of Terms............................ 41 OMMM 1.70 Table of Contents Introduction What exactly is OMMM? It's the "Opus Matrix Message Masher", or perhaps stated even better; it's a way for your Opus system to handle it's own mail. Whether you send one Matrix message a month, or transfer echos daily between several systems, OMMM lets you set up your system to handle the mail the way YOU want it handled, without the use of any type of front end program. OMMM was originally written by Wynn Wagner III as part of the Opus CBCS package, and has always been an integral part of Opus. With the work of Jon Marshall and others, this new version has added day of week named packet extensions, day and time schedul- ing, point support, zone awareness, plus complete compression support through the "stuffer<tm>" command lines in it's con- figuration file. Because each Sysop is at a different level of experience, I've tried to create documentation that will satisfy everyone. There are those Sysops who were there at the start of this wonderful phenomenon who want to quickly learn about juicy new features. There are those who are setting up a board for the very first time, and don't care HOW the program works, but want the answer to that old question, "How do I set this thing up from scratch?" This documentation is dedicated to Wynn Wagner III with thanks, and to Mark Lymburner, with love. Tina Dougherty June '91 OMMM 1.70 Page 3 New Setup from Scratch ====================== +--------------------------------------------------------------+ | | | "It's important to set up your head for all of | | this before you set up your computer." | | | | - Wynn Wagner III | | Opus 1.0 docs | | | +--------------------------------------------------------------+ Ok, so you've set up most of your Opus board, and now want to be able to send mail to another system. OMMM, when setup cor- rectly, will bundle your mail, address it, and send it out ac- cording to specifics you've set. To setup OMMM, you're going to have to do five things: 1. Edit the OMMM.cfg to your preferences. This file comes with the OMMM program, and has many helpful comments already in it to provide extra information for you. 2. Setup your OMMM schedules. Having your schedules setup correctly is one of the keys to running OMMM correctly, and to having your board do what you want it to do WHEN you want it done. Read the sections on schedule verbs, and on the Routefile. 3. Edit your Nerf batch file to work with OMMM. The section of these docs on the use of errorlevel exiting will be helpful if this is a new concept to you. 4. Work with your Event Manager. After you've setup your schedules, you'll need to use your Event Manager to specify WHEN you want Opus to run OMMM and do it's thing to handle your outbound mail. 5. Choose either OMMM or OMMM286. (Both are included) This choice will depend on what type of processor you have. If you're running your board on a 286, 386 or 486 processor, rename OMMM286.Exe to OMMM.Exe. If you've never set up OMMM before, it's not hard, but IS going to take a bit of reading on your part. This section will lead you through setup as painlessly as possible. If you're an old hand at working with OMMM, and haven't jumped to the "Grizzled Veteran" section yet, do read through these docs to get some detailed ideas on what's new with 1.70. OMMM 1.70 Page 4 The OMMM Configuration File =========================== OMMM has one of THE most easy to understand config files because of all the helpful comments that are there for you. Your OMMM program comes with a sample OMMM.cfg that you can pull into your favorite word processor and edit to your specifications. Your word processor MUST be able to save in ASCII format. If you're new to config files for programs, you need to know that any line that starts with a word will be read by the pro- gram, and any line that starts with a symbol such as ";" is con- sidered to be "commented out". In other words, if you want to add some notes of your own, you can do that just by making sure that the ";" symbol is the first character on the line. You also use the symbol before a command or parameter if you don't want it to be read by the program. Here are the commands where you tell OMMM where to find info it needs about your system. Optional items are noted here with *: MESSAGEPATH - Path to your Matrix messages. HOLDPATH - Path to your outbound mail holding area. PRESCANPATH (*) - Path to your prescan routing file. ROUTEFILE - Fully pathed RouteFile name. ADDRESS - Your FULL address. This *MUST* show your Zone, Net, Node and Point number. If you don't have a number yet use 0:-1/-1.0 'til you get one. If you want to run in to run in Zone Aware mode, use the zone numbers. If you don't want to run in Zone Aware mode, use 0 for your primary zone number. Ex: 1:371/15.0 is Zone Aware 0:371/15.0 is NOT Zone Aware POINTNET (*) - Local pointnet if you're a Bossnode. More info on this command is available in the "Grizzled Veterans" section of these docs. SCHED (*) - Allows you to set up schedules so that OMMM does WHAT you want it to do, WHEN you want to do it. This is one of the most important parameters in your config file, and will be covered in-depth a bit later in this doc. If you're NOT a Bossnode, or don't use a PRESCANPATH, then sim- ply comment these lines out by putting the ";" in front of that word. In the sample OMMM.cfg, PRESCANPATH comes to you already commented out. Note that OMMM does have a minimum of information it needs to run. MESSAGEPATH, HOLDPATH, ROUTEFILE, ADDRESS, and at least one SCHED are all necessary fields that need to know where you're storing what. OMMM 1.70 Page 5 For each command, you must make the choice whether or not you want your board to use that particular option. You "toggle" these choices off and on by "uncommenting" the line by removing the ";" in front of the command. In addition to the lines listed above, here's a list of the com- mands available to you in OMMM config, and what each will do for you. (This info is also available with fuller explanations and examples in Index A of this doc.) FORWARD Toggles off the default of OMMM to forward mail and add to an existing bundle of a different type. (Hold, Crash, etc.) Be careful about turning off forwarding if you're a Host or Hub. MO? If you'll be communicating with an old Opus 1.0x board, or a mail system that doesn't understand the newer extensions, then use this switch. GATEROUTE Tells OMMM to route all your interzone mes- sage through the zone gates. NO_SCAN Will tell OMMM not to scan your Matrix area. OMMM will only scan your outbound area and do routing. QUIET Suppresses some of the displays, which makes for more speed, and a tidier screen. NORMAL Normalize all packets in the holding area so that those that are left with the LEAVE verb are sent. (The LEAVE verb is explained here in the section on Scheduling verbs.) MAXARC Used to specify the maximum compression size. The default is no limit. OLDBUNDLE # Will tell OMMM to delete bundles after they've been sitting around in your outbound area for too long. If you decide to let OMMM handle this, you must specify the number of days before a bundle is deleted. NO_DATE Disables the OMMM default to support the time/date stamping of Opus messages into FTSC for- mat for outbound mail. Use this ONLY if you're not using an Opus compatible message editor. NAKED Makes OMMM generate file requests understandable to mailers that treat .REQ files as normal mail rather than as a file request. If you're not running Binkley, don't use this option. REQUEST Toggles the new Opus (1.2x) file requesting options. If you're running Opus 1.2x, check out the new file extensions listed in the TechnoTalk section of this doc. OMMM 1.70 Page 6 OZONE Will let you hold off on processing Zone mail. With this option, mail in your matrix area will NOT be scanned. Use this if you don't want mail addressed to other zones scanned. At the bottom of your config file, you'll find all your "stuffer<tm>" options. These tell OMMM which compression pro- gram to use for compressing mail from your system. Choose ONE of the options as your default, and comment out the others. So, if you're going to use PKZip to compress mail from your board, it should look something like this: ;Define the "stuffer" program to use for creating compressed Define_Stuffer ZIP pkzip -a ;Define_Stuffer PAK pak a ;Define_Stuffer ZOO zoo -add The second set of stuffer<tm> lines enable you to define a spe- cific compression method for a specific system. Let's say you're a PKWare fan, and have chosen ZIP as your default. How- ever, you've got a friend who really prefers their mail to come in PAK'd. You can have OMMM PAK their mail by uncommenting the PAK line in the second stuffer<tm> set, and adding their address to that line. Example: ;Define a list of nodes to use with each stuffer<tm> Stuffer PAK 129/112 Stuffer ZOO 371/18 By using lines like these, 129/112 will receive their mail PAK'd, and 371/18's mail will be ZOO'd. Everybody else will re- ceive mail from your system ZIP'd. There's no limit to how many boards you can put in each line, other than DOS's limit of 512 characters. If you find that you need more than 512 characters on a line, feel free to use the same stuffer definition more than once. OMMM can handle it: Stuffer PAK 129/112 129/50 129/11 371/18 Stuffer PAK 129/26 Stuffer will work with ANY compression program that uses the same syntax as those found in your config file. If your favor- ite compression program can be setup like this: Name <options> compressed_file_name filename_to_be_compressed then it'll work in OMMM. Check into the config file, as just about every known compression program has already been listed for you to comment in or out. Don't Forget: Your compression method MUST be in your path! OMMM 1.70 Page 7 WARNING WILL ROBINSON, WARNING! Do NOT change the way a node has it's mail compressed while there's mail being held for that board. If you change a board's compression method while there's a packet sitting there, you'll end up creating a packet that will be garbage 'cause neither compression method will be able to open it. Command Line Switches ===================== There's another way you can have OMMM read your configuration choices. Take a REALLY close look at the QUIET toggle line in OMMM.cfg: QUIET ; -q from command line The "-q" is the command line switch this command. This means that you can either run: c:\opus\OMMM and have it read the toggles from your config file, or you can run: c:\opus\OMMM -q and have it read the toggles from your command line. This can come in handy for you if you want to run OMMM differently at different times. Basically, remember it this way...all the op- tions that you want OMMM to use ALL or MOST of the time, set them up in your config file. It's best to use command line switches only to over ride the configuration in special in- stances. REMEMBER: COMMAND LINE SWITCHES OVER RIDE THE CONFIG SETUP. So, if you ALWAYS want to run OMMM in Quiet mode, uncomment the Quiet line in your config. When we get into setting up sched- ules, you'll see how you can use the command line switches to over ride the config in special cases. You'll also see how you use the command lines to run a specified SCHEDULE at a specified time. OMMM 1.70 Page 8 Setting Up Errorlevels ====================== So, how can you use the command line switches to run OMMM to your specs when you want them run? The answer is errorlevels. You're going to need to setup errorlevels in your Nerf.bat (aka Runopus.bat) to let OMMM know what to do and when. You've already setup some exiting errorlevels in your Opus con- trol file to tell Opus what to do when a caller exits. Now, you tell Opus what to do when it gets to that errorlevel. You use errorlevels, OMMM command lines, and the OMMM SCHED command in conjunction with your Event Manager to have OMMM run certain schedules. This is done either when Opus exits at a specific errorlevel, or at specific times of day. The key to successfully using OMMM is to set up the errorlevels correctly, so they call the OMMM schedule you want, when you want it to be run. Go into your Nerf.bat, and setup an "If ERRORLEVEL ## Goto" line to be run when a caller hangs up. This MUST match the error- levels you told Opus to use when you set up your control file. Let's say that when you setup your Opus board, you told Opus to use: AFTER Call Exit 12 (somewhere near line 245 in bbs.ctl) Here's what a BARE BONES Nerf.bat would look like: @Echo Off Cls C: CD\Opus :START Opus BBS :LEVEL If errorlevel 255 goto start Errorlevel here -------> IF ERRORLEVEL 12 GOTO MAIL If errorlevel 5 goto start If errorlevel 4 goto start If errorlevel 3 goto error If errorlevel 2 goto start If errorlevel 1 goto end :ERROR Echo Echo Serious Error - Opus Halted. Goto end Sends Nerf.Bat Here --> :MAIL Runs Schedule E ------> OMMM -sE Goes back to Start ---> Goto Start :END CLS OMMM 1.70 Page 9 Using this example, the board would exit at an errorlevel of 12, as you told it to do in your bbs.ctl. This errorlevel is caught by the batch file, which makes it "goto MAIL". The MAIL part of the batch file runs OMMM for Schedule E. (The -sE switch in the command line tells OMMM to run Schedule E). The next line then returns the board to START, so it'll be ready for the next caller. Remember, command line switches over ride the config file, so if you've got QUIET mode commented out in your config file, but add a "-q" to your command line, that particular run of OMMM will run in QUIET mode. So, we've exited and told OMMM to run Schedule E. How do we set that up? Scheduling ========== We've called for Schedule E to be run in the example, so we have to tell OMMM what we want it to do for Schedule E. This is ac- complished with your SCHED lines in your config file. Putting all of your scheduling information in the OMMM.cfg is now fully supported and easy to use, although the Routefile is still supported. IMPORTANT: OMMM must have at least one Sched- ule in the config file, and it will also be looking for the RouteFile you specified. Since you MUST have at least one SCHED statement in your OMMM config, and since OMMM will be looking for the RouteFile you specified in your config, let's (for now) set up a Schedule E in both places. Schedule E will handle any mail that was entered while a caller was on-line. This would be a "normal exit after caller", or what your system would normally do when a caller hangs up. Create a very simple RouteFile with the name you specified in your OMMM config (something like ROUTE.CTL) that includes lines like these, then add edit the SCHED lines in your config file. Use a schedule similiar to this, substituting boards you're in contact with in place of 129/112 and 371/18: ;Normal Exit After Caller SCHED E ONEHOLD 129/112 371/18 ONEDIRECT All The words: SCHED, ONEHOLD and ONEDIRECT are just a few of the Scheduling Verbs, and they're what allows you to setup OMMM to handle mail to any board you want. Each Scheduling Verb can be used to specify ONE board, or to list many boards. OMMM 1.70 Page 10 This particular Schedule E causes any mail destined for 129/112 or 371/18 to be put on HOLD, and to have it's files processed individually. (You'll learn more about this in Index C, Sched- ule Verbs). The ONEDIRECT ALL statement at the end of the schedule serves as a catchall for any unrouted bundles sitting in your outbound area, so that they'll be directed to the cor- rect system. There are many Scheduling Verbs available to you, and each will cause mail to the boards you've listed to be handled as you specify. Please read Index C carefully so that you can have OMMM correctly handle mail for your board. The HOLD and UNHOLD Verbs ========================= Let's take a minute to talk about the HOLD command. Mail you've marked HOLD will take up permanent residence in your outbound area until one of four things happen: 1. It's picked up by the destination board. 2. Your board UNHOLDS it, so it can be sent. 3. It's deleted by the OLDBUNDLE (-t) command. 4. It's deleted manually by you. Option #4 doesn't mean that you'd delete the message from your board, but that you'd actually go into your outbound manager, or the outbound area itself and delete the mail packet. PLEASE resist any and all temptation to futz with the files in your outbound area until you know EXACTLY what you're doing. It used to be that HOLDing and UNHOLDing mail was pretty much determined by when the destination board could handle an incom- ing call. Nowadays, most boards can handle incoming mail at any time of day, so you want to concentrate on sending mail when it's the cheapest for you. This harkens back to the way you've setup to process your nodelist, and to setting up your OMMM. So, if you're going to send some long distance mail, rather than have it picked up, you'd want your board to know to HOLD all mail for long distance/tollcall boards until it's the right time to UNHOLD and send them. Let's say that you've setup your files like the examples above (substituting a board that you'll be contacting in place of the 129/112 and 371/18 shown). Go into your board and enter a net- mail message to the board you've specified to have their mail marked for HOLD. Say Good-bye, and watch OMMM do it's thing. What happens is that when you sign off (either remotely, or from local keyboard), Opus finds the "if errorlevel 12 goto" line, and runs the OMMM line that includes Schedule E. So, the mail to the system(s) you specified in Schedule E with the ONEHOLD command are now sitting on hold. OMMM 1.70 Page 11 What you should end up with is a mail packet that's on HOLD. You can check this by reading the packet's extension, but since we haven't gotten that far (yet), use oMAN or your outbound man- ager to check on what's in your Outbound area. You should have a set of files that are marked as HOLD in the Status column. If not, go back and check everything you've setup. (Spelling counts). So, now you've got this mail sitting in your Outbound area. Since you now know that HOLD mail won't be send, what do you do with it? That depends on whether you're responsible for sending it, or if another board is going to call yours and pick it up. If you're going to have to send it, how do you get OMMM to UNHOLD that mail? You run another errorlevel, with another Schedule. Using your Event Manager, set up a new event with an errorlevel you've not used in your Opus setup, and one that's NOT reserved for use by Opus. Opus reserves errorlevels 0-4 and 255 for it's own use. You'll also need to setup the Start and End times of the event for 11pm (23:00). Now go to your Nerf.bat, and add the errorlevel line: IF ERRORLEVEL 50 GOTO CHEAPER And it's corresponding "goto" line: :CHEAPER OMMM -sC Goto Start and then setup a Schedule C in your OMMM config file: ;Call Chuck at 11pm SCHED C UNHOLD 129/112 POLL 129/112 ONEDIRECT All When the event is run, it'll exit at the errorlevel you specified in your event setup. The command UNHOLD will change the mail packet so that it's not on HOLD anymore. When Opus sees this packet isn't on HOLD, it'll call the destination board to send the mail. The POLL command is used incase you've agreed to call this board whether or not you have mail waiting for it. The POLL command will cause your board to call the board you've specified to be polled. Not only can you have schedules run just specific tasks where you set the time by errorlevels, but you can specify days of the week, and start and end times for them. We'll be covering that aspect of the Schedule file in the section on enhancing your OMMM setup. OMMM 1.70 Page 12 The PreScan File ================ There are two things you should keep in mind about the PreScan file: 1. The PreScan file is rarely used. It's available to you in OMMM.cfg, and can be added on the command line with the switch -p (Example of command line: -pC:\OPUS\PRES.CAN) 2. If you choose to use it, you must remember that commands in this file will be run BEFORE ANY of your schedules. Be- cause it is run on ALL mail in your outbound directory, and because it is run before any of the schedules, it is either extremely helpful or downright dangerous. Make SURE you know what you're doing before deciding to run a PreScan file. Quoting Jon Sabol on what the PreScan file does: "<The PreScan File> allows you to convert the outbound area to a normal state prior to running the event. I don't use a prescan file. I let the routing statements correct themselves. Prima- rily, the PreScan file is to allow you to un-LEAVE nodes that have been marked as no-send. Other than that, you are on your own to decide what the prescan does. Here are some examples: UNCRASH ALL Will change any CLO,CUT files into FLO,OUT files. Useful if you need to UNCRASH any nodes. UNHOLD ALL Will change any HLO, HUT files into FLO,OUT files. Useful if you need to UNHOLD any nodes. UNCRASH ALL UNHOLD ALL ONECRASH ALL Will change ALL outgoing mail that has not been routed to CRASH. Useful to create archives that are marked CRASH for all the boards listed. UNCRASH ALL UNHOLD ALL ONEHOLD ALL Will change ALL outgoing mail that has been routed to HOLD archives. Useful to create archives that are marked HOLD for all the boards listed." To fully understand what Jon has said about PreScanning, check into the commands he's used. All commands are listed here in Index C. OMMM 1.70 Page 13 The RouteFile ============= The RouteFile is simply all your Schedules in one file that you can create with any ASCII text editor. To OMMM, having this file named (and fully pathed) is essential, whether you choose to define it in the OMMM config or on the command line. The RouteFile must exist, either pathed in your OMMM.cfg file, or given on the command line with the "-c" switch. OMMM config must have at least one schedule in it. This gives you the free- dom to put all used schedules in one place or the other, or di- vide them between both files. Some Sysops will want to put all the schedules in the RouteFile, and not have them listed in the OMMM config. That's fine and will work as long as you remember that OMMM config must have at least one schedule in it. This doesn't mean it has to be one that is ever run. For example, you could put a schedule Z in your OMMM config, and simply never call for that particular schedule. If you'd prefer to have all of your schedule info in the OMMM config, do the exact opposite. Put all your schedules that are run in OMMM config, and one that's never called in the RouteFile. To create a simple RouteFile which we'll call Route.ctl, add the name to your ROUTEFILE line in OMMM config. With the name of Route.ctl, it would be added to the OMMM config like this: ROUTEFILE c:\opus\Route.ctl Or, call it from the command line: OMMM -cC:\OPUS\ROUTE.CTL Then, create your file using any ASCII text editor (even Edlin if nothing else is handy.) Here's a simple, sample RouteFile: SCHED E ;The fault schedule - Normal Exit after caller OneHold 129/112 129/11 129/50 129/26 OneDirect All SCHED C ;Poll Chuck after 23:00 UnHold 129/112 Poll 129/112 OneDirect All SCHED N ;National Mail Hour 4-5 am EST 5-6 am EDT Unhold All OneHold 371/All 129/All OneDirect All OMMM 1.70 Page 14 Setup your Schedules either in your config file, or your RouteFile so that you hold mail for systems that call you for mail, and for those systems that you only want your computer to call at certain times. DON'T SKIP THIS SECTION, IT'S IMPORTANT: The important thing to remember about OMMM when working with the RouteFile, and with OMMM config, is that it's a PRODECURAL pro- cessor. It will run command 1, then 2, then 3, etc. To make it simple, what this means is that you should deal with specific boards first, then use any shorthand command(s). Since my Netnumber is 371/15, I have mine set like this: HOLD 129/112 ONEDIRECT ALL If I had it bassackwards: ONEDIRECT ALL HOLD 129/112 Then the mail for 129/112 would NOT be put on hold, because it was already a direct bundle. I'd have to go in manually via oMAN or my outbound manager and change this bundle to a HOLD. Since the idea of OMMM is to let it deal with the mail for you, that's not a very tasty solution. OMMM 1.70 Page 15 Shorthand Commands ================== There are many ways to add to your OMMM setup, and these are ac- complished mainly through Scheduling correctly. For example, if you know that you're going to be sending mail to different members of the same net, and they're all long distance calls, you can either specify each one in your RouteFile, or use a bit of OMMM shorthand. For example, you could have the line: ONEHOLD 129/112 129/11 129/50 129/26 * OR * ONEHOLD 129/All The commands: ALL WORLD NET??? are used when you want to specify groups of nets. For example: 129/ALL 129/WORLD NET129 are all valid commands that tell OMMM that you're referring to every system listed in the Nodelist as a member of Net 129. Other shorthand commands are OURNET and OTHERS. Both will refer back to your primary Net Number. My primary NetNumber is Fido 1:371/15, so if I have the line: HOLD OURNET in a Schedule, that means that I want to HOLD any mail for any board in Net 371. The OTHERS command is the exact opposite, as it means every board OTHER than those in your primary net. So, if I have the line: HOLD OTHERS in a Schedule, it would set all mail to every board that's NOT in Net 371 to HOLD. In addition to shorthand commands, there are other ways in which to customize your OMMM setup so that it'll tap dance if you like. (well, not really, but darn close.) These ways are your OMMM config file, and your schedules setups. OMMM 1.70 Page 16 Once you've got a basic setup running on your board, take a close look at Indexes A and C of this doc. Index A is a concise guide to the commands available to you through OMMM config and/or the the command line. Index C is a list of all the schedule commands, and what each will do for you, along with some tips on how to use them. You may also want to check through the "Grizzled Veteran" section, to learn about day and time commands that are a new feature of OMMM version 1.70. Please keep in mind though, the immortal words of Wynn Wagner when he was talking about schedule commands: "In most cases, you can lead a fruitful/meaningful life with nothing more complicated than those <three or four commands>. All of the other words are for advanced usage or for special circum- stances. (K.I.S.S!)" So, though OMMM has the power to handle all mail chores for a board that NEEDS an extremely complicated setup, that doesn't mean you need to MAKE your setup extremely complicated. OMMM 1.70 Page 17 News for Grizzled Veterans - Juicy New Features of 1.70 ======================================================= +--------------------------------------------------------------+ | Oh well a touch of grey, | | kinda suits you anyway. | | - Touch of Grey | | The Greatful Dead | +--------------------------------------------------------------+ Date and Time ============= The ability to add day and time parameters to your Schedules is now available. This can be particularly helpful to set up OMMM for something like National Mail Hour. SYNTAX: SCHED <tag> <day> [<start_time> <end_time>] EXAMPLE: SCHED N All 04:00 05:00 ; National Mail Hour Valid days are: All Every Day Tue Tuesday Only Week Week Days Only Wed Wednesday Only WkEnd WeekEnds Only Thu Thursday Only Sun Sunday Only Fri Friday Only Mon Monday Only Sat Saturday Only If you'd want to run a schedule on Wednesdays and Fridays, you can do that with the "|" symbol to join days in the same Sched- ule. For something like this, you'd enter the days as Wed|Fri, and that Schedule would only be valid on those days. Starting and ending times use military time: 00:00 Midnight 08:00 8am 16:00 4pm 01:00 1am 09:00 9am 17:00 5pm 02:00 2am 10:00 10am 18:00 6pm 03:00 3am 11:00 11am 19:00 7pm 04:00 4am 12:00 Noon 20:00 8pm 05:00 5am 13:00 1pm 21:00 9pm 06:00 6am 14:00 2pm 22:00 10pm 07:00 7am 15:00 3pm 23:00 11pm So a Schedule set for 20:00 23:30 would run from 8pm to 11:30pm. Also new in the category of "Time" is that OMMM now automagically stamps FTSC format time/date on outgoing mail packets. Only disable this if you're not using an Opus compat- ible message editor. (Use NO_DATE or -d to disable). OMMM 1.70 Page 18 Day Stamping ============ OMMM now supports the proper day stamping of compressed mail: MO?, TU?, WE?, TH?, FR?, SA?, and SU?. The "?" equals a number from 0 to 9, depending on how many packets you've put together for that system that day. This type of extensioning is only done if you've commented out the MO? command in the config, or haven't overridden it with the -o parameter. There's ONE exception to this rule though: if you're using MO?/-o, AND have set a size limit, then OMMM could possibly get to MO9, and have it exceed your set size limit. If this happens, then OMMM will automagically override your deci- sion to use the older standard, and name the next bundle TU0. POINTS ====== More and more Sysops are starting out as "Points" to established systems (Called a "Bossnode" when they have a Point or Points running under their supervision). Some nets are encouraging new Sysops to serve as Points before joining the net as a full fledged system. Until recently, Opus and OMMM didn't have full support for this type of operation, but you can now set up your OMMM to reroute mail to Points. To enable this, use the POINTNET line in OMMM config: POINTNET ### where ### is the network address the message is to be rerouted to. So if my address is 109/315, and a message is found ad- dressed to me as 109/315.2, and I have POINTNET 0 in my config file, the message would be automagically rerouted to 0/2. Message to: Zone:Net/Node.Point Re-Route to: Zone:Net/Point Quoting Jon Marshall in the OMMM History file: "It is rumored that Opus will support points using WaZoo/Yahoo protocol with a rerouted message going to a network address of 0. In the above example, if another Opus calls me with an address of 109/315.2, any outbound mail for 0/2 will be sent. In testing, the point network address needs to be -1 for Opus 1.1x to work this way." OMMM 1.70 Page 19 File Requests ============= OMMM will now support Opus 1.2x's new file request features. This'll allow you to control WHEN you want to send file requests as well as receive them. It'll also help to prevent file re- quests during National Mail Hour. Use the REQUEST line in OMMM config, or the "-y" on the command line to toggle it on. See Index B for a list of mail packet extensions used with this feature. File Attaches ============= You can file attach messages with file names beginning with ^ or #. The beginning character determines how OMMM will handle the file after it's been sent: ^ will be deleted after being sent. # will be 0'd out (to 0 bytes in length) after being sent. OMMM will also allow you to do wildcard file attaches and mul- tiple file attaches where each file is separated by semicolon, a comma or a space. Your message editor might hiss at you about this, but OMMM will expand the information out so your mailer will pick it up. OMMM and OMMM286 ================ As of 1.70, OMMM will include two versions of the program. OMMM is for those who aren't running with an 80?86 processor, while OMMM286 is for those who are. If you're running on a 286 or 386, a good suggestion would be to either delete or rename OMMM.Exe, then rename OMMM286.Exe to OMMM.Exe. No_Scan ======= OMMM now gives you the ability to choose NOT to scan your Matrix area. Using the new No_Scan or -j switch will cause OMMM to only scan your outbound areas and do routing. OZone Scanning ============== The new OZone or -z command will let you hold off on processing Zone mail. With this option, mail in your matrix area will NOT be scanned, so use this if you won't want mail addressed to other zones scanned. Command Line Switch Over Ride ============================= ALL command line switches now over ride the config file. OMMM 1.70 Page 20 Replaced Commands ================= ARC Routing Verbs ================= They be gone! The ARC and ZOO routing commands have been re- placed with the STUFFER verbs. Here're the conversion equals: ARCCM is now STUFFCM ARCDIRECT is now STUFFDIR ARCHOLD is now STUFFHOLD ZOOCM is now STUFFCM ZOODIRECT is now STUFFDIR ZOOHOLD is now STUFFHOLD VERB COMMAND ==== ======= INFO_PATH -i Gone completely. DOCM Gone completely. ZONE -z Formerly used to specify Zone Aware mode, the -z is NOW used for OZONE, or holding zone mail that you don't want scanned right away. Use 0 for your zone ADDRESS to disable zone. Use # for your zone ADDRESS to enable zone. NO_ADD -u Formerly used to determine whether OMMM would add to existing bundles, this command is gone. OMMM 1.70 Page 21 Setting up for Multiple Zones ============================= +---------------------------------------------------------------+ | Her name was McGill, | | And she called herself Lil, | | But everyone knew her as Nancy. | | - Rocky Raccoon | | The Beatles | +---------------------------------------------------------------+ With the release of Opus-CBCS 1.20, Opus is now fully Zone aware! To setup for Zone awareness you have to do each of the following items: 1. Tell Opus all of your addresses. This is done in the BBS.Ctl, and all addresses must be fully listed including zone, net, node and point. Remember that the FIRST address listed will be your Primary address. Your Primary address MUST be the same in Opus, OMMM, and in the nodelist compiler of your choice. The order of your other addresses (if any) can be in any order you like, but your Primary address must always be listed first: ADDRESS 1:371/15.0 ADDRESS 69:2304/1.0 ADDRESS 45:570/103.0 ADDRESS 30:30101/15.0 2. Edit any of your echo areas which will be exchanging mail with other Zones. In the message area, it's only your ADDRESS line which reflects the Zone. Don't try to put the Zone number in your SCAN line. If you do, Opus will burp and spit and say bad things about you. Here's an example of an echo setup that I use to exchange mail within Zone 69: AREA 0102 REVIEW SECTION O PUBLIC MESSAGES ONLY ANONYMOUS OKAY ECHOMAIL A_REVIEW ACCESS PRIV Privil PEEK PRIV Sysop PATH G:\MSG\AREVIEW\ TITLE Over18 Movie Reviews MAXLINES 60 ADDRESS 69:2304/1.0 ORIGIN The Emerald City - Ft. Myers, FL SCAN 2304/18 END AREA Opus will automagically include my Adult Links (Zone 69) ad- dress in the origin line, and will know that this echo is Zone 69 bound. Which leads to the point that you can't share echos inter-zone. Putting the Zone in your message area ADDRESS line will give Opus the Zone to send to, so whatever boards you list in the SCAN line must be in the same Zone as your message area OMMM 1.70 Page 22 ADDRESS. Omitting the Zone will cause Opus to default to the Primary Zone. (You knew you'd see that term again, didn't ya?) Once you've got all the echo areas setup, re-Salt your control file, and move on to telling OMMM what's going on. 3. Tell OMMM all of your addresses. This is done in the OMMM.CFG, or with the "-a" switch on the command line. Same as with the Opus control file, all addresses must be fully listed: ADDRESS 1:371/15.0 ADDRESS 69:2304/1.0 ADDRESS 45:570/103.0 ADDRESS 30:30101/15.0 While you're in OMMM.Cfg, you can decide which (if any) of the Zone commands you want to use. The NO_SCAN (-j) and OZONE (-z) switches are available if you decide to only handle specific Zone processing at specific times. If you're just setting up for Zones for the first time, a suggestion would be to not use either of these switches until you've decided how you'll want them to work for you. 4. Let your Route.Ctl file know what you're doing. Unlike the Opus SCAN line, you DO include the Zone number here if it's different from your Primary Zone. You don't need to include the Zone number for your Primary...that's your automagic de- fault: SCHED E ;Normal Exit after caller OneHold 129/112 30:30101/18 OneCM 69:2304/18 OneDirect All 5. Compile your nodelist using the compiler of your choice in Zone Aware mode. Check the documentation of your compiler to setup it's config correctly so that your nodelist.idx and nodelist.dat files include the Zone specifics. If you don't compile your nodelist to include the Zones, none of the other adjustments you've made will do you any good, and will only confuse everybody involved. 6. Create separate outbound directories for each Zone. Your pri- mary address will be handled by your main outbound directory (usually C:\OPUS\OUTBOUND), but each other zone must have it's own. This is done by using extensions made from the hexidecimal value of the Zone. Use the conversion table avail- able here (Index D) to find the correct Hex values for your zones. Example: C:\OPUS\OUTBOUND\ For Primary Zone 1 C:\OPUS\OUTBOUND.045\ For Zone 69 C:\OPUS\OUTBOUND.02D\ For Zone 45 C:\OPUS\OUTBOUND.01E\ For Zone 30 OMMM 1.70 Page 23 6. Check what you've setup by going into your board and entering a message to a board in another Zone. In your Netmail area, en- ter the message to the correct board INCLUDING the Zone number. If Opus tells you that it can't find the address, go back and check everything you've done. (Spelling still counts). What Happens Next ================= Once you've entered your message and Opus has found the address, hang up and watch OMMM go to work on it. You'll see something like this, which I see when I enter a message to 69:2304/18: Reading OMMM.cfg file OMMM processing schedule 'E' Quiet Mode Scanning mail area... 102 ... To: 69:2304/18 (CM) Go into your Matrix section, ("M" if your board is sitting READY), and ask for I)nfo, you should see that the mail is sitting in the correct directory, and has it's Zone number noted: CRASH/SPEW ATTACHES: C$ 69:2304/18 #C:\Opus\Outbound.045\09000012.CUT Opus will call the board, and will present YOUR address that matches the Zone of the intended board. Note line #4: 1. OPUS Calling 69:2304/18 Mental Floss (2755410) 2. OPUS Connect 9600/Arq 3. OPUS Responding to: 69:2304/18.0 4. OPUS Responding as: 69:2304/1.0 5. OPUS /\/\ENTAL FLOSS (69:2304/69.0) 6. OPUS Password-protected session 7. OPUS Throughput = 280 bps (3) 8. OPUS DL-Z C:\Opus\Outbound.045\09000012.CUT 252 9. OPUS Connect: 0:23 10. OPUS End (1) Basically, Zone awareness is simply making sure that your board knows the different names for the same thing. I send mail to 1:371/18, 69:2304/18, 69:2304/69 and 30:30101/18. They're all different names for the same board. Another example would be if you were to play these docs backwards, you'd find out that Wynn Wagner III, Zaphod Beeblebrox and Jon Marshall are all the same person. This isn't recommended though...it might cause unwanted demons to appear. :) OMMM 1.70 Page 24 TechnoTalk ========== How OMMM Does What It Does ========================== So, what exactly happens after a message is entered, and OMMM processes the mail according to your setup? Well, after the caller exits, and the computer is done burping and spitting, look into the directory you specified in your OMMM config as HOLDPATH. If you're not zone aware, this is where all outbound mail goes no matter how it's going to be handled. You're gonna some weirdly named files there, and though you won't understand them (but read on) OMMM understands them, because it's the one that named them. AGAIN, please don't muck with these files unless you know exactly what you're doing. If you MUST delete or rename a file, it's much easier and safer to do with an out- bound manager program. To understand what the scheduling verbs do for you, it's impor- tant to understand how OMMM uses the names and extensions of the files: The name of the file is used to tell WHERE the mail is going. The name of the extension is used to tell HOW it's going there. Let's peer into my outbound directory for a second and take a look at the files that OMMM created when it scanned the mail: 00810070.HLO 00F2FF9F.MO1 Both of these files were created when I entered the Matrix mes- sage to 129/112, and both are critical to making sure that the mail is sent correctly. The name of the first file is the address of it's destination in hexidecimal (base 16). In this case, it's 0081/0070 in hex, or 129/112 in decimal. This file is commonly called a File Attach file or a FLO file. The File Attach name comes from the fact that this is a small ASCII file that simply notes which mail packet(s) to send to the destination. The FLO moniker comes from the extension name FLO, which is a Normal attach file. HLO is the extension for an attach file that's on HOLD. (See Index B for a complete list, suitable for framing.) This file acts as the "marker"...it tells your board WHERE to send the mail. If you were to type this file to the screen, you'd see that it's a simple ASCII file that shows the com- pletely pathed names of all packets to send to the address, in- cluding the names of any files you want to send along with messages.. The lines listed inside this file are usually pre- ceded by the "#" symbol, which tells OMMM to truncate the mail packet itself to 0 bytes after it's sent. This helps to keep your outbound area from eating up all your disk space. OMMM 1.70 Page 25 The "stuffed" mail itself is in the second file shown, and OMMM uses a different method for the name and extension. These bundles are named for the difference between the board's num- bers, so 00F2FF9F.MO1 is the actual message bundle that's on HOLD TO 129/112 FROM 371/15. That's how your board knows WHICH board has sent you a bundle. (Your system does the math, you don't have to worry about adding and subtracting in hexidecimal). In the case of the mail itself, the extension is used to tell what day of the week it was put together (new style extensions) and number of packets inside. (Both old and new style). When you run your schedules to change the way the mail is handled, you're dealing with the extension on the "marker" file. It's these extensions that tell OMMM exactly how you want the mail to be handled. So, when you tell OMMM to UNHOLD mail, the program changes the extension on this "marker" file from .HLO to .FLO. Sure, you can do this manually, but setting your alarm clock to wake you up at 4am to change file extensions isn't gonna do your home life any good. Let's say you've agreed to call a specific board every Monday night to exchange mail. You want to call this board, whether or not you have mail for them. Let's see how OMMM would handle this. For starters, since you've agreed to call this board once a week, we'll say you HOLD mail for them until you call. So, if mail to this board has been entered, you have a packet that's been marked as HOLD. The marker file is sitting there with the extension of HLO. Now, you run a schedule who's first line says to UNHOLD mail to this board. OMMM changes the extension to FLO. Because this mail packet is now marked with a FLO exten- sion, Opus will call the board. Opus recognizes the FLO, CLO, DLO and HLO extensions, and will call the board who's address makes up the name of the file with any of those extensions. So, when UNHOLD changes the extension, your board will call out, de- liver this mail, and pick up anything for your board that the Sysop there has on HOLD for your board. But, what happens if you DON'T have any mail waiting for this board? There's nothing there for you to UNHOLD to create a FLO file. This is where the POLL command in a schedule comes in. POLL will create a "dummy" file with the extension of FLO, which will cause your board to call out. So, a good schedule for something like this would look like: SCHED C UnHold 129/112 Poll 129/112 OneDirect ALL Since you're reading this rather dry section of the docs to find out HOW OMMM does what it does, let's take a look at how OMMM manipulates the extensions in this schedule. OMMM 1.70 Page 26 UNHOLD 129/112 Will change any mail for 129/112 that has a HLO extension to a FLO extension. FLO is the extension for a normal file, which causes Opus to try to send it. If there IS a file there for 129/112, you now have a file with the FLO extension, and your board will call 129/112 to send this mail (and pick up any HOLD mail waiting for you). POLL 129/112 This will cover you incase you DON'T have any mail waiting to be sent to 129/112. The POLL command will create a dummy FLO file if it can't find a file with the extension of FLO, DLO or CLO. (Normal, Direct or Crash). This will make your board call 129/112, even if you don't have any mail for him...but just want to get any mail waiting for you to pick up. ONEDIRECT ALL This command is used for systems that you know CAN'T accept mail at all times of day (a board that CAN accept mail all day is know as supporting "Continuous Mail") and for boards that you're not sure as to their mail receiving capabilities. This is actually a holdover from old BBS systems that couldn't (or weren't set up by the Sysop) to accept mail at any time of day. Though most boards now can and do accept incoming mail all day, there are some boards that don't. So, this command is an excellent "catch-all" to handle mail for systems you haven't specified indi- vidually. Though YOU don't need to know all the extensions and what they do, OMMM uses this info to make sure your mail goes out to the correct board, at the correct time. Remember, you're completely in charge of this, and control it by the way you setup your schedules. OMMM 1.70 Page 27 Index A - Config Commands & Line Switches ========================================= --------+------------+----------+------------------------------------------- Switch | Name | Required | Examples --------+------------+----------+------------------------------------------- -m |MESSAGEPATH | Y | In OMMM.cfg: MESSAGEPATH C:\MSG\NET | | | On command line: -mC:\MSG\NET This tells OMMM where your Matrix (Netmail) area is. It's the same directory you specified when you set up your board. --------+------------+----------+------------------------------------------- -h | HOLDPATH | Y | In OMMM.cfg: HOLDPATH C:\OPUS\OUTBOUND | | | On command line: OMMM -hC:\OPUS\OUTBOUND This is the path to your outbound message hold area. You only specify your primary outbound path, even if you're running multiple Zones. You can use this switch from the command line to spec the directory where all of your mail will be placed after processing. You must specify a holding area either from the command line, or in the OMMM config. --------+------------+----------+------------------------------------------- -p |PRESCANFILE | N | In OMMM.cfg: PRESCANPATH C:\OPUS\PRES.CAN | | | On command line: -pC:\OPUS\PRES.CAN This is a non-mandatory file that enables you to have OMMM scan BEFORE the schedule you'd specified for that exit is run. Read the section on this file CAREFULLY if you decide to use it. --------+------------+----------+------------------------------------------- -c | ROUTEFILE | Y | In OMMM.cfg: ROUTEFILE C:\OPUS\ROUTE.CTL | | | On command line: OMMM -cC:\OPUS\ROUTE.CTL The complete path to your RouteFile may be added via the command line. The example shown is for the file Route.ctl which is in the C:\OPUS directory. --------+------------+----------+------------------------------------------- -a | ADDRESS | Y | In OMMM.cfg: ADDRESS 0:371/15.0 | | | On command line: OMMM -a0:371/15.0 This is your board's address. You list your primary address first, using 0 for zone if you're not operating in zone aware mode. To operate in zone aware mode, use the zone number. You list your aka(s) under your primary. If you're not in zone aware mode, OMMM will default to the primary number. OMMM 1.70 - Index A Page 28 --------+------------+----------+------------------------------------------- Switch | Name | Required | Examples --------+------------+----------+------------------------------------------- -f | FORWARD | N | | | | This switch is used to toggle off the default of OMMM to forward mail, and to add to an existing bundle of a different type. Be careful about telling your board not to forward mail if you're a Host or Hub. --------+------------+----------+------------------------------------------- -o | MO? | N | In OMMM.cfg: MO? | | | On command line: OMMM -o Older versions of OMMM used file extension names of MO#, where the "#" was the number of packets packed for that destination system that day. In the older format, MO does not stand for "Monday", but for Mail Out. You can force OMMM to use the newer version extensions, which are named according to days of the week. New style extensions: MO? TU? WE? TH? FR? SA? and SU?. If you communicate with an older Opus 1.0x board, or a mail system that doesn't understand the newer extensions, then use this switch by uncommenting it in the OMMM.cfg, or adding it to your command line. --------+------------+----------+------------------------------------------- -g | GATEROUTE | N | | | | Tells OMMM to route all of your interzone messages through the zone gates. If you're not operating in zone aware mode by specifying an address with a zone, then OMMM automagically operates in gate mode. --------+------------+----------+------------------------------------------- -j | NO_SCAN | N | In OMMM.cfg: NO_SCAN | | | On command line: -j This tells OMMM not to scan your Matrix area for messages. It will only scan your outbound areas and do routing. --------+------------+----------+------------------------------------------- -q | QUIET | N | | | | Operating in quiet mode suppresses the display of some screens, which makes for a bit more speed, and a tidier screen. OMMM 1.70 - Index A Page 29 --------+------------+----------+------------------------------------------- Switch | Name | Required | Examples --------+------------+----------+------------------------------------------- none |POINTNET -1 | N | In OMMM.cfg: POINTNET -1 | | | This if for use if you're a Bossnode. Set the network address the message is to be re-routed to. So, if you have Pointnet set to -1, and your address is 109/315, and a message is found addressed to 109/315.2, the message would be automagically re-routed to -1/2. Opus seems to do points just great with the YAHOO/Wazoo protocol when the Network address is -1! --------+------------+----------+------------------------------------------- -n | NORMAL | N | | | | Normalize all packets in the holding area, so that those that are left with the LEAVE verb are sent. --------+------------+----------+------------------------------------------- -x | MAXARC | N | In OMMM.cfg: MAXARC 512K | | | On command line: -x512 This command lets you specify how big the bundles may be before a new bundle is started. The default is no limit. --------+------------+----------+------------------------------------------- -t | OLDBUNDLE | N | In OMMM.cfg: OLDBUNDLE 7 | | | On command line: -t9 This enables you to let OMMM take care of deleting mail that's been sitting in your hold area for a specified number of days. Use the command with a specific number of days immediately following the -t with no spaces between. In first example, OMMM would delete mail after 7 days, and the second example would delete after 9 days. --------+------------+----------+------------------------------------------- -d | NO_DATE | N | | | | OMMM supports the time/date stamp converting of Opus messages into FTSC format for outbound mail. This option is used to DISable this, which you should only use if you're not using an Opus compatible message editor. OMMM 1.70 - Index A Page 30 --------+------------+----------+------------------------------------------- Switch | Name | Required | Examples --------+------------+----------+------------------------------------------- -r | NAKED | N | | | | Used to generate file requests with mailers that treat .REQ files as normal mail. (See Index B for file extensions). Using this option will create "naked" file requests, which are understandable by Binkley. If you're NOT running Binkley, don't use this option. --------+------------+----------+------------------------------------------- -y | REQUEST | N | | | | With Opus 1.2x, this command will let you specify the new Opus file requesting options. --------+------------+----------+------------------------------------------- -z | OZONE | N | | | | This toggle will let you hold off on processing Zone mail. With this option, mail in your matrix area will NOT be scanned. Use this only if you don't want mail addressed to other zones scanned. 3 THINGS TO FILE IN YOUR BRAIN (Somewhere under C:\OPUS\OMMM\MISC): 1. If you choose to use any of the command line switches that require a name input (like MESSAGEPATH or HOLDPATH), make sure you fully path the name on the control line. See the examples here. 2. DOS requires that the full command line be ONE line. So, if you choose to do your command line input from a batch file, remember that all commands must be on the same line. 3. Once again, remember that all command line switches override whatever you've set in the OMMM.cfg. OMMM 1.70 - Index A Page 31 Index B - File Extensions ========================= Below is a chart that shows all the mail packet extensions, and what type of mail packet they're used for. You DON'T need to know how to work with these, as OMMM will handle that for you. This is just for your reference. When NOT using the LEAVE verb: +------------+------------+------------+------------+ | Flow | Flow | NonStuffed | NonStuffed | | | with | | with | | File | Request | Mail | Request | +---------+------------+------------+------------+------------| | | | | | | | Normal | FLO | FRO | OUT | ORT | |---------+------------+------------+------------+------------| | | | | | | | Crash | CLO | CRO | CUT | CRT | |---------+------------+------------+------------+------------| | | | | | | | Direct | DLO | DRO | DUT | DRT | |---------+------------+------------+------------+------------| | | | | | | | Hold | HLO | HRO | HUT | HRT | +-------------------------------------------------------------+ When USING the LEAVE verb: +---------------------------------------------------+ | Flow | Flow | NonStuffed | NonStuffed | | | with | | with | | File | Request | Mail | Request | +---------+------------+------------+------------+------------| | Normal | | | | | | Crash | NLO | NRO | NUT | NRT | | Direct | | | | | | Hold | | | | | +-------------------------------------------------------------+ Additional extensions are: REQ - Opus style file request. NRQ - Binkley style file requests using NAKED (-r) option. $$? - File created by your mailer to keep track of how many bad connects have been made to a system. These are calls where you would be charged because the phones DID connect, but were unable to exchange mail. Opus will mark this board "undialable" and stop calling it it after 5 attempts. You can "clear undialables" via an outbound manager or the Opus Matrix Menu. MO? - Compressed mail packet for either old style (using MO? or -o option). Or a Monday packet, using the new style. TU?, WE?, etc are packet names using new style format. OMMM 1.70 - Index B Page 32 Index C - Schedule Verbs ======================== SCHED MEANING: This is the most important schedule command, because it tells OMMM that it's the beginning of all the commands for that schedule. For Example: EXAMPLE: SCHED <letter> (In OMMM.cfg or RouteFile) -s<letter> (On command line) SCHED C -sC tells OMMM that this is the start of schedule <letter>, and for it to run all of the following commands, IN OR- DER, until it reaches another SCHED line. You use this verb in your OMMM, or in your RouteFile to mark the beginning of list of verbs to be run when that schedule is called. POLL MEANING: This tells your board to call the board you've specified. EXAMPLE: POLL <Net/Node> POLL 129/112 will cause your board to call the board you've specified when that schedule is run. Remember, your board will call any board you specify if it finds the number from your nodelist files. However, if you've got mail on hold for that board, OMMM won't send that mail unless you UNHOLD it first. If you're holding mail to send to another system at a cheaper phone rate, make sure you UNHOLD it before you poll that board. HOW IT WORKS: The POLL command creates a dummy ????????.FLO file, if no .FLO, .CLO, or .DLO extensioned file exists. Opus recognizes these extensions as a file to be sent, so calls the board specified, and picks up any mail there for you (unless that Sysop used the LEAVE command). OMMM 1.70 - Index C Page 33 PASSWORD MEANING: Using this command will encrypt a password into the compressed mail packet. This means that the board receiving this packet must be able to uncompress the mail, AND must also have the password set up at that end. EXAMPLE: PASSWORD <Net/Node> <password> PASSWORD 129/112 PARANOID HOW IT WORKS: Encrypts a password into the *.MO? (.TU?, WE?, etc if using new extension names), so that the receiving board must also have the correct password setup at their end to un-compress and toss the mail. HOSTROUTE MEANING: Using this command will automagically have OMMM address a mail bundle FROM the board to whom it's addressed TO the board that serves as the "host" for that net. The NetWork CoOrdinators of each net serve as the "host" of the net, and presumably would have their boards setup to send the mail to the final ad- dressee at the correct time of day. So, what you're doing when using this command is sending a message to someone via their NC. If you choose to use this command, please keep in mind the fact that while most NCs can call all boards in their net as a local call, some boards may be a toll call for them. EXAMPLE: HOSTROUTE <Net/Node> HOSTROUTE 129/112 In the above example, all mail slated for 129/112 would be routed through 129/0. This command is from the days when many boards didn't support continuous mail, and so mail was routed through the host of the net. It was assumed that Hosts would be setup to send the mail at a time when the final destination board could accept it. OMMM 1.70 - Index C Page 34 HOW IT WORKS: Using HOSTROUTE causes OMMM to rename the file with the Host's board number, rather than the final des- tination boards' number. If you were to use the above example and HostRoute a message to 129/112, OMMM would change the name of the file from: 00810070.HLO (129/112 in Hexidecimal) to: 00810000.HLO (129/0 in Hexidecimal) All Hosts are <Net/0>. NOTE: If you're a Network CoOrdinator/Host, make sure you've setup your schedules to include a time to forward mail for your net. LEAVE MEANING: This verb is very similar to the HOLD verb, with one major exception: Mail that has been marked LEAVE can NOT be picked up if the destination board should call yours. The LEAVE verb renames the exten- sion of the file to one that Opus won't recognize The bundle won't be sent by your board, nor can it be picked up by the destination board. To Opus, a LEAVE packet doesn't exist. EXAMPLE: LEAVE <Net/Node> LEAVE 129/ALL 371/18 HOW IT WORKS: Renames: ????????.FLO ????????.CLO } to ????????.NLO ????????.DLO ????????.HLO } ????????.FRO ????????.CRO } to ????????.NRO ????????.DRO ????????.HRO } ????????.OUT ????????.CUT } to ????????.NUT ????????.DUT ????????.HUT } ????????.ORT ????????.CRT } to ????????.NRT ????????.DRT ????????.HRT } The NLO, NRO, NUT and NRT extensions don't mean any- thing to Opus, so the renamed file is not sent, and cannot be picked up. OMMM 1.70 - Index C Page 35 SEND MEANING: Used as an "Un-Leave", this verb causes a packet that's been marked as LEAVE to now be sendable, and pickup-able (is that a word?). The SEND verb will change the LEAVE packet to a normal packet, so if you want to remove a packet from it's LEAVE state, and have it then be on HOLD, you must SEND it, then HOLD it. EXAMPLE: SEND <Net/Node> SEND 129/ALL 371/18 HOW IT WORKS: Renames: ????????.NLO to ????????.FLO ????????.NRO to ????????.FRO ????????.NUT to ????????.OUT ????????.NRT to ????????.ORT OMMM 1.70 - Index C Page 36 There are also twelve other verbs available to you, and though listed after those above, they're actually the most common used. These twelve are HOLD, CRASH, and DIRECT, along with the pre- fixes UN-, ONE- and NORM-. HOLD will mark a packet (by changing it's extension), so that the mail is NOT sent, but can be picked up by the desti- nation board. CRASH will tell your board that this mail should go out immediately, and your board will begin calling the des- tination as soon as the caller hangs up. DIRECT will tell your board that this mail is slated for a sys- tem that doesn't support continuous mail. UN- Will reverse the verb it's used as a prefix for. ONE- Compresses the mail, and creates separate packets for each board in the line. So ONEHOLD 129/ALL will com press mail being sent to any board in Net 129, create a separate marker file for each, and put all of the pack- ets on HOLD. NORM- Will NOT compress the mail, but will create a marker file for the destination board, and then follow the in- structions of the verb it's a prefix for. The next page of these docs gives you a chart of these verbs, and their prefixes, for your viewing pleasure. Each verb has the same syntax: COMMAND <Net/Node> [Net/Node] [Net/Node] So: HOLD 129/112 ONEHOLD 371/18 129/112 129/50 are both valid lines in a schedule. OMMM 1.70 - Index C Page 37 +-----------------+-----------------+-----------------+ | UN- | ONE- | NORM- | +--------------------+-----------------+-----------------+-----------------+ | HOLD | UNHOLD | ONEHOLD | NORMHOLD | | | | | | | Mail is compressed | Change a HOLD | Compresses the | Mail is NOT | | and addressed, but | packet to a | mail, and makes | compressed, but | | after that, your | normal packet | a marker file | IS addressed, | | board will ignore | by changing the | telling the | then marked as | | it. The mail will | "marker" file | board that the | HOLD. | | sit until: | extention. | mail is to be | | | 1. You UNHOLD it. | | put on HOLD. | | | 2. The destination | | | | | board calls and | | | | | picks it up. | | | | | 3. It's deleted as | | | | | as an OLDBUNDLE.| | | | | 4. You delete it | | | | | manually. | | | | +--------------------+-----------------+-----------------+-----------------+ | CRASH | UNCM | ONECM | NORMCM | | | | | | | Opus will try | Change a CRASH | Compresses the | Mail is NOT | | to send this | packet to a | mail, and makes | compressed, but | | mail immediately. | normal packet | a marker file | IS addressed, | | Opus 1.1x & 1.2x | by changing the | telling the | then marked as | | will allow callers | "marker" file | board that the | CRASHED. | | to log onto the | extention. | mail is to be | | | board between | | CRASHED. | | | tries, while Opus | | | | | 1.03 will do it's | | | | | best to keep | | | | | calling out. All | | | | | Opus versions will | | | | | keep calling to | | | | | send until they | | | | | get the packet | | | | | through, or get | | | | | 5 unsuccessful | | | | | connects. | | | | +--------------------+-----------------+-----------------+-----------------+ | DIRECT | UNDIRECT | ONEDIRECT | NORMDIRECT | | | | | | | This command is | Change a DIRECT | Compresses the | Mail is NOT | | used for systems | packet to a | mail, and makes | compressed, but | | that you know | normal packet | a marker file | IS addressed, | | can't receive | by changing the | telling the | then marked as | | continuous mail, | "marker" file | board that the | DIRECT. | | and those you're | extention. | mail is to be | | | not sure about. | | a DIRECT packet.| | | It serves as an | | | | | excellant "catch | | | | | all" at the end | | | | | of a schedule. | | | | +--------------------+-----------------+-----------------+-----------------+ OMMM 1.70 - Index C Page 38 Index D - Decimal/Hexidecimal Conversion Chart ============================================== DEC HEX DEC HEX DEC HEX DEC HEX 1 - 1 26 - 1A 51 - 33 76 - 4C 2 - 2 27 - 1B 52 - 34 77 - 4D 3 - 3 28 - 1C 53 - 35 78 - 4E 4 - 4 29 - 1D 54 - 36 79 - 4F 5 - 5 30 - 1E 55 - 37 80 - 50 6 - 6 31 - 1F 56 - 38 81 - 51 7 - 7 32 - 20 57 - 39 82 - 52 8 - 8 33 - 21 58 - 3A 83 - 53 9 - 9 34 - 22 59 - 3B 84 - 54 10 - A 35 - 23 60 - 3C 85 - 55 11 - B 36 - 24 61 - 3D 86 - 56 12 - C 37 - 25 62 - 3E 87 - 57 13 - D 38 - 26 63 - 3F 88 - 58 14 - E 39 - 27 64 - 40 89 - 59 15 - F 40 - 28 65 - 41 90 - 5A 16 - 10 41 - 29 66 - 42 91 - 5B 17 - 11 42 - 2A 67 - 43 92 - 5C 18 - 12 43 - 2B 68 - 44 93 - 5D 19 - 13 44 - 2C 69 - 45 94 - 5E 20 - 14 45 - 2D 70 - 46 95 - 5F 21 - 15 46 - 2E 71 - 47 96 - 60 22 - 16 47 - 2F 72 - 48 97 - 61 23 - 17 48 - 30 73 - 49 98 - 62 24 - 18 49 - 31 74 - 4A 99 - 63 25 - 19 50 - 32 75 - 4B 100 - 64 Since running in multiple Zones requires multiple outbound di- rectories, and these directories must have the HEXIDECIMAL rep- resentation of the Zone, use this chart to find the correct number. You don't need to add any extension to your primary zone outbound, as your primary will work out of C:\OPUS\OUTBOUND. However, if you're running with additional Zones, you must create a separate subdirectory for each, with the decimal Zone number represented in Hex format as the directory extention. For example, if your primary address is in zone 1, mail for that Zone would be handled by C:\OPUS\OUTBOUND. If you also have a Zone 69 address, you would need to create an Outbound subdirectory with the 69 represented in hex form. So, you would need to create C:\OPUS\OUTBOUND.045 to handle your Zone 69 mail. Conversely, if your primary Zone is Zone 69, and your aka is Zone 1, then C:\OPUS\OUTBOUND would handle your Zone 69 mail (since it's your primary Zone), but you'd need to create C:\OPUS\OUTBOUND.001 to handle your Zone 1 mail. OMMM 1.70 - Index D Page 39 Legal Department ================ This documentation includes the names of many different program- mers, and their programs. Listed below are the names of the programs/programmers/organizations/persons who have had their efforts mentioned, or quoted. Arc, Arca, Arce.........Vernon Buerg, Wayne Chin, System Enhancement Associates, Inc. Binkley/BinkleyTerm.....Bit Bucket Software Fido....................Tom Jennings, Fido Software Lharc...................Haruyasu Yoshizaki oMAN....................Tom Kashuba Opus CBCS...............Wynn Wagner III Pak.....................NoGate Consulting PkWare/PkZip/PkUnzip....Phil Katz, PKWare, Inc. Zoo.....................Rahul Dhesi Very special thanks to Wynn Wagner III, Jon Sabol and Jon Mar- shall for their kind permission in allowing me to quote them in these docs. Special thanks to Chuck Ammon, Joe Fossati, Paul Kelly, Gary Rickman, and Stu Turk for allowing me to use their NetNumbers in the examples given here. It just so happens that it was Chuck, Joe and Stu who helped me setup my own board a long time ago in a galaxy far, far away. OMMM - Software Version 1.70 by Jon Marshall, Based on the original OMMM, a portion of the Opus CBCS, copyright 1986 by Wynn Wagner III. Portions Copyright BS Software 1988, 1989 Portions Copyright John Valentyn, 1990 Portions Copyright Jon Marshall, 1990, 1991 OMMM - Documentation Version 1.70 documentation by Tina Dougherty, Copyright 1991. All rights reserved. All quotes used with permission. Portions Copyright Wynn Wagner III Portions Copyright Jon Sabol Portions Copyright Jon Marshall Stuffer<tm>, Stuffer Bundles<tm>, and Stuffed Mail<tm> are trademarks of the OMMM product. They may be used freely in a friendly and legal manner to describe compressed mail and file compression utilities. OMMM 1.70 - Legal Department Page 40 Glossary of Terms If you're unable to find the term you're looking for here, try the Indexes, then your DOS manual. 1.0x ................. Version of Opus. 1.1x ................. Version of Opus - 1.10 released 3/12/90. 1.2x ................. Version of Opus - 1.20 released 7/14/91. AKA ................. Also Known As - Used by boards that belong to more than one Net, so usually more than one zone. ARCA ................. Compression Method. ARCE ................. Un-Compression Method. ARCMAIL .............. Term for mail packet that's been compressed. ASCII ................ Straight readable text. BBS.CTL .............. Text control file for Opus. BBS.PRM .............. Machine readable control file for Opus. BOSSNODE ............. A board that is running Points. CONFIG ............... A file of parameter commands read by the executable program. COMPRESSED............ File made smaller in size by a program written for that purpose. DOC .................. Documentation, instructions. EDLIN ................ DOS's text editor. FTSC ................. FidoNet Technical Standards Committee. GOTO ................. Command used in batch files to direct execution of the lines. (See "Setting Up Errorlevels" and your DOS manual). HEXIDECIMAL .......... Base 16 mathematics. INTERZONE ............ Between Zones. INTRAZONE ............ Within the same Zone. LHARC ................ Compression Program. MAXLINES.............. Maximum number of lines for a message in any message area. Configurable in BBS.Ctl. MATRIX MAIL (NETMAIL). Mail sent between 2 boards. NCs .................. NetWork CoOrdinators. NECs.................. NetWork Echo CoOrdinators. NERF.BAT ............. A present to WWIII from the boss to prevent damage to the equipment. Also the common name of the batch file that's used to run Opus. NET/NODE NUMBER....... Your Net Number and Node number: Basic Example: 371/15 With zone and point specifications: 1:371/15.0 (Zone:Net/Node.Point) NODEDIFF ............. Weekly update to Nodelist. NODELIST ............. List of all boards currently having NetNode numbers in that particular group of Nets. Fido uses Nodelist, EggNet uses EggList, etc. NON-STUFFED .......... Mail that's not been compressed. OMMM ................. Opus Matrix Message Masher. OMMM.cfg ............. Configuration File for OMMM. PAK .................. Compression/Un-Compression program. PKZIP/PKUNZIP ........ Compression/Un-Compression program. OMMM 1.70 - Glossary Page 41 POINT..................A board which is running under the direc- tion of a "BossNode". A Point board does not have it's own net number, but gets all echo mail through their boss. PRESCAN .............. Scanning all mail prior to running OMMM. PRESCAN FILE ......... File that gives commands for PreScanning. PROCEDURAL ........... To run in order. Step 1 then 2 then 3, etc. ROUTEFILE ........... OMMM file that can hold all scheduling info. ROUTE.CTL ............ A sample RouteFile name. RUNOPUS.BAT .......... Optional name for a batch file that runs your Opus board. See: NERF.BAT STUFFER <tm>.......... OMMM command to work with any compression program. SYSOP ................ System Operator, runs the board. UN-COMMENTING ........ To delete the symbol in front of a command in a config file. This enables the program to read it. UNDIALABLES .......... A board that Opus has connected to 5 times, but has been unable to exchange mail all 5 times. Opus will not attempt to call this board again, unless you "Clear Undialables" either from Opus's Matrix Menu, or with an Outbound Area Manager. UNROUTED ............. Mail that hasn't been directed to it's destination. UN-COMPRESSING ....... Opening up a compressed file. UN-LEAVE ............. Use of the SEND verb to change a LEAVE packet to a normal packet. YAHOO/Wazoo .......... Opus protocol. ZONE.................. First number in a full NetNumber. In FidoNet, this specifies geographic area. For example, North America is Zone 1, Europe is Zone 2 and Australia is Zone 3. In groups other than FidoNet, it specifies the group itself. For example EggNet is Zone 99. OMMM 1.70 - Glossary Page 42