-==* JamScan 0.55 *==- By James McOrmond Octobert 4th, 1993 What is JamScan? JamScan is a complete replacement for JBundle, an Arexx script I wrote last year, to bundle up uncompressed packets of mail, and to add them to Xferq.library to be sent out during a session. JamScan does more than JBundle ever did, and it also does it much faster! (JamScan is also pure for those of you that want things as fast as possible and like to make things resident) The reason I wrote JamScan at this time, is that with the release of JamMail, I figured people would want a relatively fast and easy to use program that will fix up the files in their outbound directory. How does it work? When you run JamScan, it will check for an Env: variable named "JAMSCAN" and if it exists, it will use the contents as the filename for the config file. If no ENV: variable exists, the default is Mail:JamScan.cfg. After reading the config file, it will scan your packets directory for files that fit any of your route patterns. If the filename fits the pattern "#?.?ut", it will compress the packet into a bundle that already exists for that system, or it will create a new bundle. If it finds a bundle in the outbound directory, it will make sure that the file is being sent to that system (if your tosser already does the archiving, this is what you'll likely be using). This method is not as safe as the first option, but it is required until more tossers are Xferq.Library aware. The priority that these files are sent with is configured one of two ways. If you specify "Hold", "Crash", or "Direct", the file will have the the priority that the specific type has (Defaults are: -50 for hold, +30 for direct and +50 for crash). If this is a bundle that JamScan is just trying to add to Xferq a setting of "Norm" will result in a priority of 0. If this is a Bundle that JamScan has just added a packet to, it will check the 3rd last character in the origional filename and set the priority appropriate to that character. (C=Crash, D=Direct, H=Hold). How Do I install JamScan? JamScan is very easy to install. There are really only two relevent files. The JamScan binary itself should be put somewhere in your search path. If you have a directory where Networking software goes, this is likely a good place. The other file is your config file. I myself have the config file in my Mail: directory, but you can locate it wherever you wish. If your config file is not Mail:JamScan.cfg, you need to specify the full path name to get to your config file in the JamScan Environment variable. Configuring JamScan: There are 8 different commands that JamScan understands in its config file. They are as follows: HOST - Your Host address HOLD - The default Priority for "Hold" mail DIRECT - The default Priority for "Direct" mail CRASH - The default priority for "Crash" mail BUNDLES - The Directory Bundles will be placed PACKETS - The directory Packets will be searched for PKTS - The directory temporary compression directories will be made ROUTE - The actual Routing command. The "Packets" and the "Pkts" directories must be on the same device. I have placed the Pkts directory as a Sub-directory in the Packets directory, you may wish to do the same. The only keyword that is absolutely required is at least one ROUTE keyword. Without any ROUTE lines, JamScan won't do anything. How do I setup a Route line? A route line can have 4 arguments on the line. The first two are mandatory, but the last two are not. The first argument is the filename pattern. This is the filename as it appears in your PACKETS directory. Each name in this field should end with a #? unless you are wanting to specify the whole filename. This field uses full AmigaDos2.0 pattern matching. This can get really powerful and complicated, so you may want to read your AmigaDos manual for some hints on using strange patterns. The Second Argument, is the Xferq.Library compatible address that the file will be sent to. This can be anything from a single number, which it will assume is another node in your Net (by using the defaults in your "HOST" keyword, and the Host address you have setup with Xferq itself), to a full 5d FTN address. You can also put a Non-Fidonet address type in this field, and it will work fine. The last two fields are the Archiver type and the priority. The defaults are the "Lha" archiver, and a "Norm" priority setting. Either or both of these two settings can be left out, and they can be in either order. The outbound compressors supported are "Lha", "Lzh", "Arc", "Zoo", and "Zip". A setting of "Non" is also partially supported, but not fully working (as it isn't something people use often so wasn't a high priority). Also, if one of these two fields is found to be a number (non-0 value) then this number will be used directly as the priority that the files will be sent with. Example Config File: ; Your Host Address (2d is required, any extra is allowed) HOST 1:163/139 ; Settings for the default priorities HOLD -50 DIRECT 30 CRASH 50 ; Directory where outbound bundles will be put. BUNDLES outbound: ; Directory to search for outbound files PACKETS outbound: ; Directory root used to create temporary compression directories PKTS outbound:packets/ route 18.110.#? ZyXELNET#18:110/0.0 lzh norm route 1.167.#? ZyXELNET#18:110/0.0 lzh norm route 18.163.?11.#? FidoNet#18:163/311.0 lzh crash route 1.163.311.#? FidoNet#18:163/311.0 lzh crash route 16.#?.#? ZyXELNET#16:16/0.0 lzh norm route 2.#? ZyXELNET#16:16/0.0 lzh norm route 18.21.#? FidoNet#18:21/0.0 lzh norm route 1.2402.#? FidoNet#18:21/0.0 lzh norm route 18.700.#? ZyXELNET#18:700/3.0 lzh norm route 1.105.#? ZyXELNET#18:700/3.0 lzh norm route 1.102.#? ZyXELNET#18:700/3.0 lzh norm route 1.106.#? ZyXELNET#18:700/3.0 lzh norm route 1.3639.#? ZyXELNET#18:700/3.0 lzh norm route 18.24.#? FidoNet#18:24/0.0 lzh norm route 1.121.#? FidoNet#18:24/0.0 lzh norm route 18.26.#? FidoNet#18:26/0.0 lzh norm route 1.260.#? FidoNet#18:26/0.0 lzh norm route 18.105.100.#? ZyXELNET#18:105/100.0 lzh norm route 1.250.#? FidoNet#1:163/99.0 lzh crash route 1.163.1?9.38.#? FidoNet#1:163/109.38 lzh crash route 1.163.109.#? FidoNet#1:163/109.0 lzh crash route 1.163.13(3|4).#? FidoNet#1:163/134.0 lzh crash route 1.163.99.#? FidoNet#1:163/99.0 lzh crash route 1.163.547.#? FidoNet#1:163/547.0 lzh crash route 1.163.452.#? Fidonet#1:163/452.0 lzh crash route 1.163.139.8.#? FidoNet#1:163/139.8 lzh hold History: 0.54 - initial release, October 4 0.55 - minor tweeks, October 16 0.56 - Adding support for converting .FLO files.