Crawly Crypt Collection 1

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

/ Crawly Crypt Collection 1 / crawlyvol1.bin / bbs / marsmail / marsmail.txt < prev next >

Wrap

Text File | 1992-05-12 | 41KB | 785 lines

========================================================================== = = = MARS Productions presents... = = = = **** * *** *** * * * * *** * * * = = * * * * * * * * ** ** * * * * * = = **** * ***** * ** * * * ***** * * * = = * * * * * * * * * * * * * * = = **** ***** * * *** * * * * * * * ***** * = = = = - MARSmail Install v1.3 Release date: may 12,1992 = = - MARSmail Exporter v1.10/4D (C) 1992 MARS Productions = = - MARSmail Importer v1.10/4D = = = = Written by: Mario van den Heuvel = = Newtonstraat 257 = = 2562 KH Den Haag = = The Netherlands = = FidoNet point: 2:281/522.3 = = THANet node: 70:3170/9.0 = = ()lympic node: 17:775/211.0 = = = ========================================================================== Blackmail Page: 1 Some notes: ----------- This software is Public Domain. PD-Libraries are NOT allowed to spread this program without _WRITTEN_ permission by the author. This program has been tested with LED. I suggest you use this program. It's the BEST message-editor available for the Atari and you will have no problems (I hope...). Use of the program is AT OWN RISK. I'm giving a special TTD Warranty! ('Till the door) :-) Please register yourself as user by sending me a card, lettre or even a humble netmail-message will do. No payment is required but i would be in the highest sky if you decide tp pay a few giulders for my trouble. Thanks for the attention. Automatic Greetz, Mario van den Heuvel, Founder of MARS Productions. Blackmail Page: 2 The "thanks" bit: ----------------- Thank you for your convidence in my programming. This little manual will explain all the options of MARSmail installer, the only program that needs explaination. The other programs don't need really a description. Just start them and they will do their work. Thanks to Vincent Partington (yes, the "Jekyll" man, the BEST protocol available on the Atari) for some suggestions. The "what happened lately" bit: ------------------------------- Here are some update notes about Blackmail. Please read the entire manual at least ones, so that you know what to do. This manual has been complete- ly re-written. As Blackmail developed more then expected, the coniguration files of the betaversions are NOT readable anymore by the Installer, as well as the Importer and Exporter. If you're in doubt about which version config file you use, dubble-click on "MARSMAIL.CFG" and look at the first number. If this number is higher then 2, the config is an from the beta-version. If the number is lower, you can read the config into the installer and adjust it. True followers of Blackmail will notice the difference as soon as they start the installer... Yes guys, I've finally programmed the installer like it should look like... ALL GEM! An explaination about how it works follows later on. The previous versions of MARSmail Exporter always included the ^aINTL lines in Netmails. It's safer, but it is NOT standard. This option is now (default) off. To turn it on, include "-I" in your parameter field. The old Blackmail only supported FTS-0001 packets (stoneage). Now, blackmail also supports the new FSC-0039 and FSC-0048 packettypes. These types are widely in use today and are completely 4D, so there is no need for fakenet anymore. Blackmail will also RECOGNIZE (NOT PROCESS) type 3 and 4 packet- and message headers. As soon as there are good proposals available, they MIGHT be included in the next version. Also the logfile and temporary folder(s) are no longer fixed. You can specify there place (and the logfile's name too) yourself. The packing (removing deleted messages) can be skipped on user-defined days per area. Again, read on... The STATUS.LOG (an overview of incomming messages) now adds percentage per area (number of messages against the total number of messages). Blackmail Page: 3 The serious stuff: ------------------ OK, it's time to install Blackmail. Please place the files in the right folder (where you want to keep them) and start the installer. You will a dialog box with seven buttons: - Enter AKA, - Settings, - Moves/Arcs, - Copyrights, - Save Setup, - MARS Interface, - Exit. With these options you will install Blackmail. How? That's simple! Just read on... Enter AKA: ---------- Select this and a dialog box wil pop up looking like this: +-------------------------------------------+ | Page: 01 | | Boss: ___:_____/_____ | | AKA.: ___:_____/_____._____ | | Fake: _____ | | Password: ________ | | Domain..: _______________________________ | | | | +-------------------+ +---+------+---+ | | | Packet type: 3D__ | | < | PAGE | > | | | +-------------------+ +---+------+---+ | | | | +===================+ +--------------+ | | | OK | | CANCEL | | | +===================+ +--------------+ | +-------------------------------------------+ Now, behind the Boss you type in the Boss' address. First type in the zone, press ":", then type in the netnumber, press "/" and type in the nodenumber. Move to the next row with cursor down, type in YOUR zone, press ":", netnumber, press "/", nodenumber, press "." and pointnumber (if needed). Move to the next row (again with cursor down) and enter the fakenet (if used/desired). Again, to the next row and type in your password. The password will be converted to uppercase automaticly later on. Again, to the next row and type in the domain for the network. You can ask the domain names from your boss. Now, you see that little window containing "Packet type: 3D"? This means that the mail for that address will be send with stoneage packettypes (FTS-0001/15). It's OK, but for point addresses, you need fakenet then. However, if your boss supports 4D packet-types, you can troggle the field and select 4D packets as well. Click on it and you will see "4D-1". This means "4D packets according to the FSC-0039 fidonet document". This one is used by most mailtossers. Click on it again and you will see "4D-2". This means "4D according to the FSC-0048 fidonet document". This type is supported by DBridge for example (but Blackmail Page: 4 DBridge also accepts "4D-1"). It's not so widely spread as the FSC- 0039. If you don't know which packet to choose, take "3D". ALL systems recognize that one. After filling out the page, you can chose "OK" to accept the AKA, "CANCEL" to abort or select the left arrow/right arrow to enter the next AKA (if you have more than one). So, to enter a next AKA, click on the arrow right and in the lefthand corner you will see "Page: 01" changing to "Page: 02" and fill out the form like you just did. There is a maximum of 10 AKA's for you to enter. After you have entered ALL your AKA's, click on "OK" to accept ALL your AKA's or "CANCEL" to abort ALL your AKA's. Settings: --------- Select this and a dialog box wil pop up looking like this: +-----------------------------------------------+ | SysOp...: ___________________________________ | | Outbound: ___________________________________ | | Inbound.: ___________________________________ | | Netmail.: ___________________________________ | | AREA.BBS: ___________________________________ | | Bad area: ___________________________________ | | Temp.Dir: ___________________________________ | | Log file: ___________________________________ | | Archiver: Extract: ________.___ __ ___ KBytes | | Packing: ________.___ __ ___ KBytes | | | | +===========================================+ | | | OK | | | +===========================================+ | +-----------------------------------------------+ The cursor will be on the SysOp line. Enter your name EXACTLY as in your BINKLEY.CFG, TB.CFG etc. Now, CLICK in the outbound line. An itemselector will pop up. Move to your outbound folder, DO NOT select ANY file in that folder and click on the "OK" button of the itemselector. If you've done everything right, the path will be entered on the line. Repeat the same for the Inbound folder. CLICK on the netmail line. An itemselector will pop up. Move to your mail folder and select your netmail area (or type it in). Normally, these areanames consist of a four-digit number ("0000"-"9999") and click on the itemselector's "OK". You can find the name in the BINKLEY.CFG etc. CLICK on the "AREA.BBS" line and select your "AREAS.BBS" file. Again, click on the itemselector's "OK". CLICK on the Bad area line and locate your BADAREA (also called TRASHAREA or something simular) just like the netmail line. Again, the areaname usually consist of 4-digit number. You should find the areaname in your AREAS.BBS. If not, you should add the Trasharea to your AREAS.BBS file. (<drive>:<path>:<areaname in 4-digit format> <areaname> <def. address> Example: E:\BINKLEY\MAIL\9998 TRASHAREA 2:281/522) See The AREAS.BBS for detailed explaination about the Trasharea. Blackmail Page: 5 CLICK on the Temp.Dir line and select the ROOT-folder where Blackmail may place his temporary folders (MARSTEMP folder, containing the ROUTE and CRASH folder. For example: If you would select a folder called "TEMPS" on drive E, the line will read "E:\TEMPS" and the folders created by Blackmail will be: E:\TEMPS\MARSTEMP\ E:\TEMPS\MARSTEMP\CRASH E:\TEMPS\MARSTEMP\ROUTE KEEP THESE FOLDERS EMPTY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! If you would leave the line empty, Blackmail will create his temporary folders in the same folder as where MARSmail Exporter is located. CLICK on the logfile line and select the logfile Blackmail may use. This could be a own logfile, or the logfile used by your mailer. If you would keep this line empty the logfile will be named "MARSMAIL.LOG" which can be found in the same folder as where Blackmail is. CLICK on the Extract line and locate the archiver to be used by MARSmail Importer (the archiver you need to extract your mail with). Although only the name of the archiver will be displayed, the full path will be stated in your configuration. CLICK on the Packing line and locate the archiver to be used by MARSmail Exporter (the archiver you want to use to pack your mail). Again, only the name will be displayed but the full path will be included in your configuration. Move your cursor to the "__" directly behind the name of the Extract archiver and type in the extract command of the archiver (refer to it's manual). I suggest you move to the field by clicking on it, but you can use the cursor up/down as well. Do the same with the Packing archiver, entering the _add_ command. NOTE: Please make sure you use the correct command. Blackmail will look at the return code of the packer and when it's 0, it assumes that everything went well and delete the packet. Now, behind the Extract archive you will see an amount of KBytes. This is the memory the Importer may use. Note that it is NOT for the archiver itself... I suggest a minimum of 250 KBytes here (1 Megabyte computers). It you can afford more USE IT! Fill in this field like you've just filled in the extract- and add- commands for your archiver. Behind the Packing archive you will also see an amount of KBytes. This is the memory the Exporter may use. Again, it is NOT for the archiver itself... As the Exporter reads the entire HDR file of your areas, I suggest a minimum of 250 KBytes here (1 Mesgabyte computers). Again, use more if you can use it. The memory you will have to enter is strongly influenced by the archiver you use. Archivers like STZIP and Yoshi's LZH require a lot of memory. The MORE memory the archivers use, the LESS memory you can reserve for the Importer/Exporter. Archivers like Jonn Webb's LHARC 0.60B take up far less of your important memory so that you can reserve a higher amount. After entering all the necessary fields, click on "OK". Blackmail Page: 6 Moves/Arcs: ----------- Select this and a dialog box wil pop up looking like this: +------------------------------------------------+ | Move-To: Arc-For: | | Zone ___ to: ___:_____/_____ ___:_____/_____ | | Zone ___ to: ___:_____/_____ ___:_____/_____ | | Zone ___ to: ___:_____/_____ ___:_____/_____ | | Zone ___ to: ___:_____/_____ ___:_____/_____ | | Zone ___ to: ___:_____/_____ ___:_____/_____ | | Zone ___ to: ___:_____/_____ ___:_____/_____ | | Zone ___ to: ___:_____/_____ ___:_____/_____ | | Zone ___ to: ___:_____/_____ ___:_____/_____ | | Zone ___ to: ___:_____/_____ ___:_____/_____ | | Zone ___ to: ___:_____/_____ ___:_____/_____ | | | | +--------------------------------------------+ | | | OK | | | +--------------------------------------------+ | +------------------------------------------------+ Now, Blackmail can put packets for other networks together in one archive (different packets, of coarse) or redirect mail to an address if the zonenumber is unknown. It's very simple, but I will give you some examples... Let's suppose that you have an fidonet address 2:281/522.3 (your boss would be 2:281/522.0) and a THANet address 70:3170/9 (your boss would be 70:3170/0). If you would export your mail, packets for both addresses are created. These packets will be archived seperately and placed in two different outbound folders (that's why you can't put an extension behind your outbound folder). So, <outbound> will contain your packet for fidonet and <outbound>.046 will contain your mail for THANet. Now, you WILL need an mailer that can handle EMSI or you will have to call two times OR your THANet mail will never leave your modem. If you would enter a Move-To looking like "Zone 70 to: 2:281/522", your packet will be added to the archive containing your fidonet packet. And see... No more problems. This way, your mailer doesn't even have to be multi- address-capable, as long as you are collecting all the networks on one system (sysopm, boss, take a selection! :-) ) The second function is this: Let's use the above address for fidonet. Fidonet is divided into 6 zones. For example, zone 1 is the U.S.A. If you would like to send a message to the states, Blackmail will look for zone 1 in your AKA list (the reason why it does that is because Blackmail is multi-zone/point). It will not find it, so it will look thru your Move-To list. If there would be a line containing "Zone 1 to: 2:281/522" it will redirect that message to your boss on 2:281/522. If the line would be "Zone 1 to: 70:3170/0" it will send the message to the one you are getting THANet mail from. He will not like that, nor will the one that will recieve the message... Why put it in then? Well, Blackmail takes your FIRST AKA of the zone is not in the Move-To list or when the Move-To option is switched off. And NOBODY knows if your first AKA is fidonet or an other network... This way, you will be sure that everything goes like it should. To fill a Move-To line, type in the zone to be moved, press "T", type in the zone of the boss, press ":", type in the netnumber of the boss, press "/" and type in the nodenumber of the boss. Needless to say that the address MUST be in your AKA list. Make sure of that because there is NO checking at this stage. Blackmail Page: 7 In the ARC-For list you can enter the addresses the Exporter MUST pack for, regardless of what's in the Move-To list. For example: If I would have a Move-To for zone 70, but I want that messages for address 70:3170/100 are NOT moved to the boss behind the Move-To because he's my second THANet boss, enter 70:3170/100 in the ARC-For list and a seperate archive will be created for that address containing your messages for that system. Crashmail is NEVER moved! After entering all fields needed, click on "OK". Copyrights: ----------- The copyright message of the Blackmail programs and docs. Read it and stick to it. Save Setup: ----------- If you are all done, select this to save your configuration and you are almost ready to go (read the command line switches chapter!!!). MARS Interface: --------------- Select this and a dialog box wil pop up looking like this: +------------------------------------------+ | For MARS-Shell v1.5 users. | | | | |X| ^aINTL always | | Wait | | | | | | Move To | | Arc-For | | | | | | Random origins | | Domained random | | | | | | Pack, NO export | | No Packing | | | | |X| Write LED.NEW |X| Status Log | | | | Loglevel: | | 1 |*| 2 | | 3 | | | | +-----------+ +=======================+ | | | Export | | Exit | | | +-----------+ +=======================+ | +------------------------------------------+ For detailed explaination about the switches, read the command line switches chapter. As you can see, this option is for MARS-Shell v1.5 users only. The new version, which is NOT available yet (I haven't even started working on it), will be able to import the commands needed to start the Importer and Exporter with the parameters you need. By selecting the needed options (the X is on) and setting the loglevel, and clicking on "Export", the installer will create 2 files, EXPORT.SCR and IMPORT.SCR, containing the necessary data to import into the scripts editor of MARS-Shell. This way you can install everything with the GREATEST ease. Again, no use for it currently and only for MARS-Shell users. I plan to use this "Interface" in future programs as well so I suggest you to get hold on MARS-Shell (ALWAYS THE NEWEST requestable at Haasnet, 2:281/522, THE support BBS for MARS Productions) and register for it (15 dutch guilders, approx. £4.00, US$6,00) Blackmail Page: 8 Exit: ----- All done? Well, just exit then and let's go! :-) The command line switches: -------------------------- There are certain switches that can be used to affect the way Blackmail handles mail and to make your live easier/more fun. The Exporter: -1 Loglevel 1 (least). -2 Loglevel 2 (average). -3 Loglevel 3 (most, default). -I Always include INTL lines in netmail messages. If you have no reports of bad mail (VERY unlikely), USE IT! -W Wait for a key press at the end of the Export. -M Activate Move-To list. If you don't include this switch, data in the Move-To list will be ignored. -A Activate Arc-For list. If you don't include this switch, data in the Arc-For list will be ignored. -R Use random origins (See: The MARSMAIL.RAN). -D Use domained random (See: The MARSMAIL.RAN). -P Pack (remove deleted messages) only, NO Export. -N Do NOT pack (remove deleted messages). -H Help text (looking like this). The Importer: -1 Loglevel 1 (least) -2 Loglevel 2 (average) -3 Loglevel 3 (most, default) -W Wait for key press at the end of the Import. -L Write LED.NEW (You use LED? Use this switch so you can recognize which areas contain new messages). -S Status Log (an overview of incomming messages). The MARSMAIL.RAN: ----------------- MARSmail Exporter can add random origins to each message. This is fun, faith helping you or put silly things underneath silly messages. There are two kinds of random origins files, both are called MARSMAIL.RAN! So, you can only use ONE of the two types. The global type: With this type, ALL the lines in the MARSMAIL.RAN file (create one with a simple editor, WP mode OFF!) is a domain and will be placed underneath the messages of ALL areas, so you can't select a group of orgins to be used for area <x>, an other group to be used for area <y> etc. The commandline must contain "-R", the "-D" must be left out. Blackmail Page: 9 The domained type: With this type you CAN select a group of origins to be used on a specific area. Areas not found in the MARSMAIL.RAN will have the origin specified in the AREAS.BBS file. Again, create the MARSMAIL.RAN file with a simple editor (WP mode off). But it gets tricky now... You must specify the areas... Well, it's simple actually. Look: %ATARI.028 This is an ATARI.028 This is an other ATARI.028 origin %MUSIC This is an MUSIC origin This is also an other MUSIC origin etc. You see, FIRST you enter the areaname with a "%" in front of it, followed by the origins to be used in that area. You can do this for one, some or ALL areas you have (exept the Trasharea of coarse). You can enter almost a much origins you'd like. Keep in mind: the larger, the slower. The AREAS.BBS: -------------- The AREAS.BBS is a file containing your areanames, paths and origins. The structure is simple. Follow these guidelines and everything will be Okay. The first line is your default origin. You can specify your origin per area, but you don't have to. Besides, some programs EXPECT to find your global origin here. The format is simple: This is a default origin. NOTHING in front of it, nor behind it. It MUST be on the FIRST line. Following the global origin are your areas. With the exeption of the netmail area, ALL your areas MUST be entered here. The format is: <drive>:<path>\<area> <areaname> <address> for example: E:\BINKLEY\MAIL\0001 ATARI.028 2:281/522 NOTE: this is what every line must look like, the drive, path, name, and above all, the address. There is one special area... the Trasharea. All messages for which you have NO arealine are placed here. The format of the line is the same, so you MUST enter one of your Boss' addresses here. No worries as the Importer will make sure that the addresses are correct (as far possible). There is NO export from the Trasharea, so there is NO use of entering or replying message there... they will NEVER be exported. Blackmail Page: 10 As told, there are some other lines that can be used in the AREAS.BBS. One of them is the origin line. You can specify an origin per area. The origin must be placed before the area you want to use it in and AFTER the previous area. Example: E:\BINKLEY\MAIL\0002 MUSIC 2:281/522 -ORIGIN This is an ATARI.028 origin E:\BINKLEY\MAIL\0001 ATARI.028 2:281/522 E:\BINKLEY\MAIL\0003 MSDOS.028 2:281/522 The origin "This is an ATARI.028 origin" will ONLY be used in the ATARI.028! The area MSDOS.028 will (according to this) have no specified origin. The word "-ORIGIN" may be shortened to "-O". And introducing a new AREAS.BBS command... PACK! The format of this line is: -PACK <patterned value> The patterned value is a number range 0 to 127. With this command you can specify the day that MARSmail Exporter may pack (remove deleted messages) the areas. The value is build according to this system: Every value is build up from bits. The first 7 bits (start counting from the right) represent each day of the week. You don't have to be a wizz-kid. Look at the table, add up the values and put this behind the -PACK: Monday 1 Tuesday 2 Wednesday 4 Thursday 8 Friday 16 Saturday 32 Sunday 64 If you want the area(s) to be packed on Monday, Thursday, Saturday and Sunday, calculate the sum of: 1 (Mo) + 8 (Th) + 32 (Sa) + 64 (Su). This is 105. Add the line "-PACK 105" and all areas following this line will only be packed on Monday, Thursday, Saterday and Sunday. Note: ALL AREAS FOLLOWING THE LINE "-PACK" ARE AFFECTED! You may use as much -PACK lines as you want. Until the first -PACK line is found, the default will be all days (so that would be value 127). The switch "-P" overrides the -PACK lines. Blackmail Appendix Page: 1 These (error) messages are produced by MARSmail: ================================================ The exporter: ------------- - "MARSMAIL.CFG file not found!" The exporter was unable to find it's configuration file. To create one, run the installer supplied with the package. - "Internal error! Unable te request DTA-Buffer!" This is somewhat technical. All you need to know is that when this pops up, things are WRONG! Reset the computer and try again. - "Internal error! Unable te create MARSTEMP folder!" The Exporter uses a folder called "MARSTEMP". However, when this message pops up, the program was unable to create one. Export is halted... - "No Move-To's in config. Option switched off." You've used the Move-To switch, but there were NO Move-To's defined. Exporting will continue however. Next time, switch the option off or install MARSmail correctly. - "No Arc-For's found! Option switched off." You've used the ARC-For switch, but there were NO ARC-For's defined. Exporting will continue however. Next time, switch the option off or install MARSmail correctly. - "No AKA's found in config! Please alter setup!" The intention is that you have AT LEAST one AKA in your configuration. Please state ALL your addresses in the configuration program. - "AREAS.BBS file not found! Exitting..." The Exporter could not find the AREAS.BBS file. This file is needed for exporting your messages. Please create one. - "Scanning random file for origins..." The "MARSMAIL.RAN" file is scanned for the random origins. - "MARSMAIL.RAN textfile empty." The "MARSMAIL.RAN" textfile does NOT contain origins.... Please put some in the file so that you can enjoy this feature. The option has been turned off automaticly during the export session. - "Scanning random file for origins with domains..." The "MARSMAIL.RAN" file is scanned for the random origins. - "MARSMAIL.RAN file incorrect. No domains defined!" There are two types of ramdom origin files. One with origins ONLY or with random origins divided per area. You choose to have origins per area, but you've forgotten to state the domains.... Please do so or don't use the "-D" switch. - "MARSMAIL.RAN textfile not found." You used the random origins switch but there is NO MARSMAIL.RAN file. Please create one with a simple texteditor (WP mode OFF!!!!) - "<areaname>: Incorrect header! Skipping compression!" The messageheader "*.HDR" is incorrect. The compression will be skipped for that area. This is a "save what you can save" errormessage. It's quite serious. Fortunately there are some programs that allows you to rescue your messages. - "<areaname>: Nothing to delete" Quite simple. Not ONE message was deleted so nothing has to be done. - "<areaname>: <number1> messages found, <number2> remaining." Just an overview. - "<areaname>: Incorrect messagelength. Message #<n> not saved! According to the header the message was LONGER then the message base. This can't be right so the message will be skipped. Note that the message is gone forever! - "Compression aborted by user." Why would you do that? :-) Blackmail Appendix Page: 2 - "<areaname>: Incorrect messagelength. Message #<n> shrunk to 32767 Bytes." The maximum length of a message during compression may not be more then 32 KBytes. This message was longer and has been truncated. - "Error during compression. Area <areaname> left in it's old state." Well, something went wrong here... So I won't touch it and bring back the situation as it was. - "<areaname>: Area not found." The area in the AREAS.BBS list was not found on the disc. - "<areaname>: Area empty." Nice and easy.... - "<areaname>: Incorrect header! Skipping area!" The same as the errormessage during compression... (see above!) - "Export aborted by user" Now this is not the intention.... :-) - "<areaname>: Incorrect messagelength. Skipping message #<n>" This message is longer then the message base.... How did you do that? - "<areaname>: Message too long! Message #<n> not send!" The maximum length of a message during the export is 32000 Bytes. This message is longer. It has NOT been truncated and NOT send so you can alter it... - "<areaname>: Unexpected end of message! Message #<n> truncated!" There was a CHR$(0) in your message. This value (0x0) marks an "end of message". The rest of the message will NOT be send! - "Message for <zone>:<net>/<node> routed to: <dzone>:<dnet%>/<dnode>" This is for your information. It means that a message will be routed via the stated address. But it does NOT mean that the message will have the network altered. You can move an mailpacket to an other address, even when you HAVE an AKA for that address. In that case the only thing is that the packet will be included in the mailbag for that address. (See somewhere in the manual!!) - "Incorrect Move-To line. Address: <zone>:<net>/<node> not in AKA list! Message routed via primary address." This means that you had entered a Move-To, but the destination address (the address you want to move your packet to) was not found in your AKA list. - "No AKA and MOVE found for address <zone>:<net>/<node> Message routed via primary address." You wrote a message to an unknown zone-number. The zone was not found in your AKA, nor in your Move-To list. It will be send via your primary (first) address. - "No AKA found for address <zone>:<net>/<node> Message routed via primary address." You wrote a messahe to an unknown zone-number. The zone was not found in your AKA list. It will be send via your primary address. - "Netmail -> CRASHING message to: <name> (<zone>:<net>/<node>.<point>" For your information. This message had his CRASH bit on, so the message will be send DIRECTLY to the destination by your mailer. - "Netmail -> Exporting message to: <name> (<zone>:<net>/<node>.<point>" Just for your information. As you well know, Netmail is private mail, so only the destination address can read it. - "<areaname> -> Exporting message to: <name>" Just for your information. This (echo) mail is exported from the area. - "<areaname>: <number 1> messages found, <number 2> exported." Just for your information. It tells how many messages were found and exported from one area. - "No filename in subject field for attach!" A Netmail had a file attached, but the file was not found. - "Attaching file: <filename>" Just for your information. It confirms that the file is attached to a netmail message. Blackmail Appendix Page: 3 - "Filename already in the FLO-file." Indicates that a filename, either generated by the exporter or a file- name from fileattaches was already found in the FLO file. BEWARE: If the file was a PKT file (mailpacket), the file will be deleted. Every precaution has been taken to prevent this, but there is NO garanty it will NEVER happen... But normally it will not happen... (Some strange things must be done before this could happen...) The importer: ------------- - "MARSMAIL.CFG not found!" The importer was unable to find it's configuration file. To create one, run the installer supplied with the package. - "Internal error! Unable te request DTA-Buffer!" This is somewhat technical. All you need to know is that when this pops up, things are WRONG! Reset the computer and try again. - "Import from unknown system." This message will appear when you have recieved a ECHOMAIL from a system not listed in your AKA. The messages will, however, still be imported. - "<areaname>: <from name> -> <to name>" For your information. Just to show you from whom the message came and to whom it is addressed. - "Writing new LED.NEW file." MARSmail Importer can created a new LED.NEW file for you. This little file holds the last-read message number per area and some flags. The importer will put you into the FIRST new message and will set those flags so you can easely recognize in which area new messages have been added. - "Writing Status Log." MARSmail Importer can write a status log, containing the number of messages per area in total, the number of messages (total) addressed to you and the percent of the total number of messages. This tabel will be updated every import session, so you can see which area is the biggest. - "AREAS.BBS file not found!" The importer could not find the AREAS.BBS file. This file is needed for importing your messages. Please create one. - "No AKA's found in config!" The intention is that you have AT LEAST one AKA in your configuration. Please state ALL your addresses in the configuration program. - "No areas found in AREAS.BBS!" The importer could not find a single areaname in the AREAS.BBS file. It should contain AT LEAST a line for the Trasharea. Please alter your AREAS.BBS file and run the importer again. - "Extracting mailbag: <filename>" For your information. After this line the extracting archiver will be called to unpack your mailbag. - "Error during extraction! Renaming packet to <filename>" During the extraction, an error has occured. For safety reasons, the packet will be renamed. To identify the error, refer to the manual of the used packer. - "Packet found: <zone>:<net>/<node>.<point> -> <zone>:<net>/<node> .<point>" "Created on: <day> <month> <year> at: <hour>:<min>:<sec>" For your information. Please note that the point values are NOT always correct. - "Import aborted by user." He, the ^C also works... :-) Blackmail Appendix Page: 4 - "Unexpected end of packet! Message saved but may be incomplete!" If an message is longer than 32000 Bytes and there was NO packet- and message-terminator found, this line will pop-up. Nothing serious (most of the times), but bad enough to let you know. - "Message larger then 32000 bytes found! Message truncated!" If an message is longer than 32000 Bytes it will be cut at that length. The rest of the message will disappear. - "Unexpected end of packet. Last message non-existing." An messageheader was found and was suddenly cut off. The "message" was not appended, probably at the boss, and therefor not tossed. - "Type <n> message-header encountered (NOT supported!). Message skipped. PKT will be renamed to: <packetname>.UNK" Blackmail only supports type 2 packet- and messageheaders. The found messageheader was a type <n>, so it can't be handled. - "Expected message not found. PKT will be renamed to: <packetname>.UNK Scanning for next message..." To be on the safe side... There were some extra bytes in the packet and it's best to have a look at it. The search begins to find the next message. - "No more messages found." After the previous error, if the Importer can't find any more messages it will inform you. - "Unexpected end of packet." And suddenly (again?) the packet stopped. Don't HAVE to be serious. - "Empty packet encountered. Removed from inbound." You can't import something that is not there... - "Unknown packet header! Renaming packet to <packet name>.UNK" As told before, Blackmail can only handle type 2 message- and packet- headers.