Differences

This shows you the differences between two versions of the page.

--- whats_new_110 [2016/05/22 04:09] – avon
+++ whats_new_110 [2016/05/22 04:29] – avon
@@ Line 3169: / Line 3169: @@
 ===== 1.10 Alpha 31 =====
+<code>
++ Lots of changes to the MUTIL echomail import functions:
+. MUTIL will now process all PKT files with no regard of message type
+        (ie echo or netmail).  It should now also process PKT files that
+        have a mix of each without crashing.
+. MUTIL will now ignore the base filename of PKT files meaning it will
+        attempt to process ALL incoming PKT files.  MUTIL will check the PKT
+        header against the configured AKAs and if there is a match it will
+        import.  If a PKT is found that is not addressed to a configured AKA
+        address, MUTIL will delete it.
+. For incoming echomail bundles, MUTIL will continue to first attempt
+        to match the bundle filename to a configured echomail node, but if a
+        configured node cannot be linked, it will attempt to find an archive
+        signature and use that to extract the bundle.  Currently supported
+        signatures are ZIP, RAR, LZH, and ARJ.
+        If either a signature is found OR a link to an echomail node is found
+        it will attempt to import.  Should both fail, MUTIL will no longer
+        delete the bundle instead it will only log the issue.  This allows
+        the issue to be resolved without loss of echomail.
+        If it DOES succeed, MUTIL will process all PKT files using the same
+        logic that is described in #2 above.
+. MUTIL now reports status and percentage bars for each individual PKT
+        file when tossing a bundle, rather than just the bundle itself.  In
+        addition, the logging will contain both the bundle and the PKT files
+        contained within it.
+ ! Fixed a bug with the windows local console bleeding colors on a clear EOL
+   that was introduced in A30.
+ + Added the footprint for the new reply functions (reply by current base,
+   email, netmail, or a selectable msg base).  These are not functional yet,
+   but the internal changes have been made to allow for it.  If you notice
+   wierdness during message replies let me know.
+   <ALPHA 31 RELEASED>
+</code>
+===== 1.10 Alpha 32 =====
+<code>
++ New option in System Config -> Message Base settings called "Forced NL
+   Match".  If this is set to TRUE, Mystic will force a user who is sending
+   netmail to match an address found in the nodelist.  If it is set to false
+   Mystic will still allow a user to search the nodelist, but if it does
+   not find a match they will still have the option to send the netmail.
+ + When replying to a message, Mystic now gives the option to reply in the
+   current message base, BBS email base, or by selecting a new message base.
+   Four new prompts have been added for this:
+      ; Message reply options (standard)
+      ; &1=base name  &2=reply to name   &3=msg subject
+|16|CL|09|17 ° |15Message Reply |$X79 |16|CR|CR|03    Area: |11|&1|CR      |03To: |11|&2|CR|03 Subject: |11|$R65|&3|CR|CR|09Reply area (|11ENTER|09) Current, |09(|11B|09)ase, |09(|11E|09)mail, |09(|11Q|09)uit? |14
+      ; Message reply options (lightbar)
+      ; &1=base name  &2=reply to name   &3=msg subject
+|16|CL|09|17 ° |15Message Reply |$X79 |16|CR|CR|03    Area: |11|&1|CR      |03To: |11|&2|CR|03 Subject: |11|$R65|&3|CR|CR|09Reply area (|11ENTER|09) Current, |09(|11B|09)ase, |09(|11E|09)mail, |09(|11Q|09)uit? |14
+      ; Message reply select base prompt
+|CR|09Select message base for reply [|10?|09/|10List|09]: |11
+      ; Message "replying to X base" prompt   &1=base name
+|CR|03Posting reply message to base |11|&1|03.
+ + The message jump command in both lightbar and standard message readers
+   now use intelligent input for the message number.
+ + MUTIL can now optionally remap incoming netmail messages by defining up to
+sets of mappings under [EchoImport] address.  For example:
+      [EchoImport]
+        forward = sysop;g00r00
+        forward = system operator;g00r00
+ + Netmail exporting has been rewritten and now requires routing information
+   configured for each Echomail node.  The first requirement is that any
+   netmail base must first be linked for export if you want it to be checked
+   for routing of netmail posted in that base.
+   Once linked, it must match the "Routing Info" defined for that node.  In
+   general if you only have one uplink for that zone/network, you can use the
+   first example below.  But if you have many uplinks for a single network it
+   will of course become more complicated.
+   Routing info is defined in the format of addresses separated by spaces and
+   uses an asterisk (*) as a wildcard.  In addition to an address, a "NOT" can
+   be applied to each address by appending a ! and another address mask to it
+   which will then be excluded.
+   For example if you have are a FidoNet node in zone 1 and you want to route
+   all netmail posted to zones 1 through 5 to a specific downlink, you'd
+   configure the following Routing Info for that echomail node:
+      Routing Info | 1:* 2:* 3:* 4:* 5:*
+   For most cases that will do.  For networks that only have one zone you'd
+   simply route just that zone.  IE RandomNet zone 66 would just have 66:*
+   and you are done.  But...
+   If for example, you had two FidoNet uplinks one at (1:123/1) and you
+   wanted to route all Netmail to your first uplink EXCEPT for Netmail
+   specifically addressed to your second uplink's NET you'd do this for your
+   primary uplink:
+      Routing Info | 1:*!1:123/* 2:* 3:* 4:* 5:*
+   This will cause ALL zone 1-5 netmail to be routed to that uplink EXCEPT
+   for netmail with a destination to 1:123/*.  And then you'd configure your
+   second uplink to route ONLY net 123:
+      Routing Info | 1:123/*
+   Remember, only exported echomail nodes are eligible for routing, so in the
+   above example you'd link both FidoNet bases to your export and Mystic.
+   As usual with routing it can be confusing when you have very specific
+   routing needs but if you have only single uplinks then it can be pretty
+   straight forward.  EXISTING echomail users need to go in and add their
+   routing information if they are using the internal tosser.
+ + Message bases can now be tagged and deleted in bulk, along with their
+   message base data files.
+ + Message base global editor can now add and/or remove an echomail link to
+   a selected list of bases.
+ + New MPL filebase variable: "fbasefn" returns the file base's filename.
+ + Added new utility program: ansi2pipe.  This program converts ANSI files
+   to pipe color files and should compile for all operating systems that
+   Mystic compiles for.  This program is not distributed with Mystic directly
+   but is on SourceForge.
+ + New MPL function "GetMBaseTotal (Compress: Boolean) : LongInt".  This
+   function returns the total message bases on the system.  If Compressed
+   is true, then it will return the total number of message bases the user
+   has access to (slower to calculate).  If it is false, it returns the raw
+   total number of bases on the system.
+ + MPL variables can now be initialized by calling a function.  This has
+   actually been in a for a while but I think I forgot to document it.  For
+   example:
+     Var
+       TotalBases : LongInt = GetMBaseTotal(False);
+     Begin
+       WriteLn ('Total message bases: ' + Int2Str(TotalBases));
+     End.
+ + New MPL procedure "GetMailStats" returns the number of e-mail messages
+   and the number of unread email messages:
+     Var
+       Total, UnRead: LongInt;
+     Begin
+       GetMailStats(Total, UnRead);
+       WriteLn ('You have ' + Int2Str(Total) + ' emails, ' + Int2Str(UnRead) + ' unread');
+     End;
+ + The MC (check email) menu command now has the optional data /NOLIST.  If
+   this is supplied Mystic will go straight to reading mail instead of
+   listing the messages and asking the user if they want to read e-mail.
+ + New MPL vars: CfgNetDesc (array 1..30 of string[25] contains network
+   descriptions) and MBaseNetAddr (contains the network address target of
+   the message base).  Ex:
+      Uses CFG, MBASE;
+      Begin
+        If GetMBase(1) Then
+          WriteLn ('Base #1 is in network: ' + CfgNetDesc[MBaseNetAddr]);
+      End.
+   <ALPHA 32 RELEASED>
+</code>
+===== 1.10 Alpha 33 =====
+<code>
+ ! Fixed a small pipe code display bug in the new FS editor.
+ + MUTIL echo import now ignores case of echotag when trying to match.
+ ! MUTIL no longer adds netmail messages to a Binkley FLO file when exporting
+   echomail.
+ ! FIDOPOLL no longer expects netmail packets to be in a FLO file.
+ + Message base editor now has a Move command.  You must first Copy a message
+   base, and then move to where you want to move it to and then /M to move it.
+ + FTP server now has the option to allow passive data transfers or not, and
+   this has replaced the "Allow Anonymous" which does not exist at this time.
+   PLEASE REVIEW YOUR CONFIGURATION.  If you or users have issues with passive
+   turn it off or review the network interface setting (see below).
+   The default should set it to off now.
+ + When editing a posted message, Mystic now allows the option to set the
+   echomail "sent" flag.  Prompt #296 has been updated for this new option. A
+   new default follows:
+      ; editing message display
+|16|CL|09|17 ° |15Message Editing |$X79 |16|CR|CR|09(|11A|09)      |03To: |11|&1|CR|09(|11B|09) |03Subject: |11|&2|CR|09(|11C|09)    |03Sent: |11|&3|CR|CR|09Edit option (|11!|09) Edit text, (|11Q|09)uit? |11
+ + When Mystic gives an input prompt with a default text value, pressing a
+   backspace will now automatically erase the default.  Likewise, typing any
+   key will erase the default.
+ + Added a new flag into message bases called Pvt Reply.  If this is set to
+   true then Mystic will allow private replies/posts to a message based
+   marked as public.  This basically creates a "public/private" type base.
+   Two new prompts are added for this:
+      ; Message post: "post msg as private" in pub/priv type base
+|CR|12Post this as a private message? |11
+      ; Message reply: "post msg as private" in pub/priv type base
+|CR|12Post this as a private message? |11
+ ! When using extended hotkeys in a standard menu (ie UP,DOWN,PGUP,DOWN,etc)
+   Mystic was bleeding input during some events, and also allowing input
+   and redrawing the menu when invalid input was entered.  This is now fixed.
+ + Further optimized the on-the-fly ANSI optimization generated by Mystic. I
+   think its probably not possible to make it more efficient now.
+ + MUTIL now properly exports echomail and netmail for BSO-style point nodes.
+ + FIDOPOLL now supports sending/receiving echomail for point systems.
+ ! Fixed a bug in the QWK download system that could cause some networked
+   message bases to get corrupted.
+ + Mystic now allows the network interface to be defined for its MIS servers.
+   If you want it to work the same as before, you MUST set the "Interface"
+   value in "System Configuration -> Internet Options" to "0.0.0.0" without
+   the quotes.  ALPHA TESTERS: DO NOT SKIP THIS STEP!  USE CTRL-Y WHEN
+   EDITING THIS FIELD AND VALIDATE THAT IT IS BLANK BEFORE SETTING THE
+   VALUE TO 0.0.0.0 (ie no spaces before or after etc).
+   If you specify 0.0.0.0 Mystic will try to accept ANY connection on a
+   specified port for all adapters.  If you specify one in particular Mystic
+   will only bind, accept, and use connections from that network interface.
+ + Added some new file buffer functions to replace the old stuff.  In areas
+   where this is used (very few for now) there should be some speed up.  Be
+   on the lookout for broken things.
+ + When selecting message base during a reply, Mystic will now list all bases
+   the user has access to, instead of just the current group.
+ ! Fixed a rare bug that could ocassionally cause some strange behavior
+   during global new scans IF a message was moved.
+ ! The new FS editor wasn't correctly handling the parameters passed to it
+   via MPL and some other areas (like editing file descriptions).  This has
+   been fixed.  It can do SO much more than it does now, but its going to
+   require a revamp to the editor template files.  More on that later.
+ + The "Crosspost ACS" value in the configuration has been renamed as the
+   "Extended Reply ACS".  If this value is met for a user, Mystic will allow
+   the user to select the message base which the reply will go to.  ALPHAS:
+   YOU MUST REVIEW THIS SETTING BECAUSE IT WILL BE S255 BY DEFAULT NOW.
+   Crossposting is already allowed because once you post a message you can
+   forward it to other message bases if you are the "owner" of that message,
+   which is basically the same outcome.  This ACS was unused and useless so
+   its now changed to a more appropriate "Extended Reply ACS".
+ + Mystic has been ported to ARM Linux (aka Raspberry Pi).  There is still
+   one issue with MIS and FIDOPOLL so I am not releasing a complete install
+   for A33, but once that is sorted out I will do an installable release.
+   In the meantime, you can certainly compile the code now and run it.  It
+   runs suprisingly well once you get the console setup correctly.  However,
+   until the issue with MIS is solved you will have to use inetxd or similar
+   for your telnet server.
+   <ALPHA 33 RELEASED>
+</code>
+===== 1.10 Alpha 34 =====
+<code>
+! Mystic was not properly closing some files when resetting the message
+   base new scan pointer date.
+ ! The FTP server will now gracefully handle data session timeouts (after
+seconds) which should prevent FTP ghost users when there is a firewall
+   or network adapter configuration issue.
+ - Removed MPL support for GOTO labels.
+ - MPL/IPL syntax for not equal has been changed from "<>" to "!="
+ - Removed MakeTheme.  Prompts are not longer required to be compiled.  You
+   can delete *.thm from your DATA directory it is no longer used.  You MUST
+   move your default.txt, etc, from your root Mystic BBS directory into your
+   DATA directory.
+ + The N and P keys now go to next and previous pages in the full screen
+   ANSI viewer.
+ + The MATRIX login will now use the matrix login prompts for ALL logins
+   from matrix login.  This means that the standard login will now be
+   bypassed for menu command XL.  Make sure your matrix login looks the
+   way you want after upgrading, if you use matrix.
+ ! Fixed some quirkiness introduced in A33 around netmail.
+ ! Lots of minor bug fixes that were mostly not reported.
+ + The prompt to set the message base pointers by date now defaults to the
+   current date.
+ + The FS editor quote window template has changed (ANSIQUOT).  It now allows
+   the quote window size to be defined and all attributes.  3 screen info
+   codes are used:
+      !1 = Defines the text attribute and Y location where normal text ends
+      !2 = Defines the top Y location of quote window text and attribute
+      !3 = Defines the bot Y location of quote window and lightbar attribute
+ + Added 3 new optional Screen Info codes to the FS editor (ANSIEDIT)
+   template which allow different types of text to be colored "on the fly".
+   If you do not want to use these features, just do not set them in your
+   template.
+      !4 = Defines the color of capital letters
+      !5 = Defines the color of punctuation
+      !6 = Defines the color of numbers
+ ! Fixed issues with the ALT-GR key detection for international keyboards in
+   the Windows version.
+   <ALPHA 34 RELEASED>
+</code>
+===== 1.10 Alpha 35 =====
+<code>
+ + MBBSUTIL -FSORT will now ignore file casing on case sensitive operating
+   systems.
+ + When changing theme options involving single character input (field input
+   percentage bars, etc) Mystic will now prompt for the ASCII character
+   number.
+ + When doing a message QuickScan (MQ) with the /LIST option, Mystic will now
+   pause when the users terminal screen is full (and allow them to abort the
+   scan as well).
+ ! Mystic would get stuck in an endless loop if the MATRIX menu was turned
+   on but the menu didn't physically exist.  It will not error and log that
+   the menu is missing.
+ + When "Ask Theme at Connect" is ON, Mystic will now set the theme selected
+   as the users default theme.  Previously it would reload their last used
+   theme regardless of what was selected on startup.
+ + If the download directory doesn't exist when NodeSpy attempts a Zmodem
+   download, it will now tell you instead of crashing.
+ + NodeSpy Terminal now allows the current connected phone book entry to be
+   edited while connected.  This allows the password to be set, statusbar to
+   be turned on/off, etc.
+ + NodeSpy Terminal now only updates the last call date and times called if
+   the connection was successful.
+ + NodeSpy terminal now fully disconnects the session before displaying the
+   "connection terminated" box.
+ + MPLC will now continue to attempt to compile subsequent MPL programs even
+   if one compilation fails.
+ + Message Base QWK scan and regular scan settings now have the ability to
+   toggle ALL bases on or off at one time.  An updated prompt goes along with
+   this:
+      ; Message base new and qwk scan toggle prompt:
+Toggle: |09[|11#-#,#|09], Select [|11A|09]dd ll, [|11R|09]emove All, [|11?|09/|11List|09]: |XX
+ ! Fixed a bug in the matrix login after creating a new user.
+ ! Fixed a bug when searching or doing new scans on a single file base which
+   could sometimes cause a crash.
+ ! Broke BADIP.TXT recently.  Fixed now.
+ ! Fixed a bug with NodeSpy Zmodem download which would cause it to crash,
+   hopefully it will work better now?  At least it shouldn't crash now either
+   way.
+ ! Fixed a few other bugs and did some minor enhancements that no one will
+   notice. ;)
+   <ALPHA 35 RELEASED>
+</code>
+===== 1.10 Alpha 36 =====
+<code>
+ ! Fixed a memory leak in the new theme prompt system.  Mystic was leaking
+   about 30kb per login.
+ ! Mystic should now will properly display the file base "display file"
+   before listing files.
+ ! Date corruption with MUTIL echomail export has hopefully been fixed.
+ + MPL now has the ability to interface directly with internal Mystic BBS
+   classes.  This opens up a whole world of new possibilities in the future
+   (for example) sockets, full remote ANSI screen library (boxes, listboxes)
+   data sorting, and more.
+   Classes must first be created and then freed after using.  Mystic will
+   create the class instance and return a handle to that specific class to
+   use with the functions.  Finally, the class is freed.  Two new functions
+   go with this:
+      ClassCreate (ClassHandle, ClassType)
+      ClassFree (ClassHandle)
+ + MPL now supports the ANSI box class.  There are three functions which
+   go along with this: BoxOpen, BoxClose, and BoxOptions.  The Box class
+   will automatically save and and subsequently restore the text under the
+   box when it is closed.
+   See TESTBOX.MPS for an example.
+ + MPL now supports the ANSI input class.  There are several functions which
+   go along with this: InputString, InputNumber, InputEnter, InputOptions.
+   This class allows you more freedom over input functions than the standard
+   MPL input functions do.
+   See TESTINPUT.MPS for an example.
+ + MIS FTP server now will display 'ftpbanner.txt' from the DATA directory
+   if it exists when a user connects via FTP.
+ ! Once a default protocol was selected, the GE command (option 22) to change
+   the default was not working.
+ + MPL now supports ANSI screen class.  This allows the ability to save and
+   restore portions of the user's screen.  The example below saves the screen
+   coordinates defined as: X1:20, Y1:5, X2:60, Y2:10.  It then clears the
+   screen and then restores the saved portion of the screen.
+      Var SavedScreen : LongInt;
+      ClassCreate (SavedScreen, 'image');
+      ImageGet    (SavedScreen, 20, 5, 60, 10);
+      ClrScr;
+      WriteLn ('Press a key to restore');
+      Pause;
+      ImagePut (SavedScreen);
+      ClassFree (SavedScreen);
+      Pause;
+   <ALPHA 36 RELEASED>
+</code>
+===== 1.10 Alpha 37 =====
+<code>
+! Fixed an issue with useropts variable in MPL which could cause memory
+   corruption.
+ ! Fixed two leaked file handles during QWK packet generation.
+ + New MCI code: FT returns the total number of files in the current file
+   area.
+ + MIS BINKP server is now active.  Configuration is in the system
+   configuration with the rest of the servers.
+ + All MIS servers now maintain their own independant log files in the LOGS
+   directory, assuming "Server Logging" is turned on in Internet Server
+   Options.
+ + In order to maintain consistancy and for easier file association, telnet
+   node logs have changed from "sysop.nodenumber" to "node<nodenumber>.log"
+   in the logs directory.
+ + Users can now be flaged as "QWK Network Account" in the User editor.
+   Account names should be the same as their QWK Network BBSID.  These users
+   will bypass a majority of the login procedures and can have their own
+   distinct start menu (found in General Settings).  A new default menu called
+   "qwknetwork.mnu" has been included as an example of how one should likely
+   be setup.
+ + Message bases can now be flagged as "Allow QWK Networking" which means that
+   the message base will be allowed to be selected for scanning by QWK network
+   scans.
+ + The OS menu command (Set QWK scan settings) now has the /QWKNET option
+   available in command data.  This limits the message bases listed to ONLY
+   show bases flagged for QWK networking.
+ + The OE menu command has been removed.  Instead, a setting now saves the
+   users preference of QWK or QWKE packets.  You will need to update your
+   QWK menu to remove this command and to add the toggle of the QWKE packet,
+   or you can optionally use the new qwk.mnu included as a guide/replacement.
+ + New Menu command GE (edit user preferences) optional data: 33.  This
+   toggles the user's preference for QWKE style packets on or off.
+ + New MCI code QE returns Yes/No based on the users QWK Extended setting.
+ + The MD menu command (set message lastread pointers) now has the optional
+   data option of /ALL.  If this is used, Mystic will NOT has if the user
+   wants to update their current base, and will instead force the update for
+   all message bases.
+ ! Mystic was changing the user's message base to the last base processed
+   when globally resetting the new message scan date.
+ ! Fixed a bug that could cause a lockup in the FS editor when using the TAB
+   key.
+ + The FTP server now accurately reports the file date during file listings.
+ + The FTP server now accurately reports directories (filebases) based on the
+   actual time the file base was created in Mystic.
+ + When editing the FTP directory name for a file base, / and \ characters
+   are now automatically converted to _ so it does not conflict with FTP.  If
+   you have existing FTP names set for your file bases, you must open them in
+   the file base editor for their names to be automatically changed.
+ + Users can now download QWK packets using the FTP server.  A QWK packet
+   filename will be shown in all FTP listings.  If the user is flagged as a
+   FTP network account, their handle will be used as the BBSID for the QWK
+   packet (handle.qwk).
+ + Users can now upload QWK reply packets using the FTP server.  If the user
+   is flagged as a FTP network account, their reply packet will need to be
+   "handle.rep".
+ + The file base configuration editor now allows bulk file base deletion
+   if a list of bases are tagged when delete is requested.
+ + Mystic's FTP server now supports uploading directly to Mystic's file bases
+   using FTP.  It will also attempt to use the archive configuration to import
+   FILE_ID.DIZ files.
+ + MIS server status updates and logging now use a MMM DD format date instead
+   of MM/DD which was confusing/annoying for people outside of North America.
+ + Mystic's node logging now uses MMM DD format date instead of MM/DD/YY.
+ + The FTP server now allows resumed uploads via the APPE function.
+ + System configuration now has a QWK Networks configuration editor, where
+   one or more QWK networks can be defined.
+ + Message base editor now allows each message base to be linked to a
+   configured QWK network.  In addition, each message base also now has a QWK
+   network conference ID number.
+ + Users can now be linked to a configured QWK network using the User editor.
+   This defines the QWK network message bases that they have access to if
+   they are flagged as a QWK network account.
+ + Mystic's QWK system no longer forces all upper case user names and
+   subjects.
+ + A new temporary QWK mailer has been included called QWKPOLL.  This will
+   allow you to function as a node of a QWK network.  It will connect via FTP
+   to your network hub, send them a REP packet of new messages, download a
+   QWK packet of new messages, and toss them into the BBS message bases all
+   automatically.
+ + QWK and QWKE Networking (as a HUB and a NODE) has been implemented.  This
+   implementation also allows you to be a part of multiple QWK networks and
+   even HUB them in addition to being members of several - all with separate
+   access management.
+      NOTE: All setups require you to have defined your QWK packet ID in
+      the Local QWK settings.  This is the filename of the QWK packets
+      generated from your BBS or uploaded to your BBS.
+      SETTING UP AS A NODE OF A QWK NETWORK
+      =====================================
+. Create a new QWK network profile in the System Configuration ->
+         QWK Networks and set the member type to Node.  When you join a QWK
+         network you should get all of the details required to fill in the
+         rest of the settings.
+. For each message base in the QWK networking:
+            A. Create message base in the message base editor.
+            B. Set message base type to echomail
+            C. Set QWK Network to point to your newly created QWK network.
+            D. Set the QWK Conference ID for the base.  This is specific to
+               the network and should be provided to you along with the list
+               of bases when joining the network.
+. Thats it.  When you run QWKPOLL it will attempt to connect to your
+         QWK networking hub and exchange/import messages for you for each
+         base (via FTP).
+      SETTING UP YOUR OWN QWK NETWORK
+      ===============================
+. Create a new QWK network profile in the System Configuration, and
+         set the member type to HUB.
+. Create your message bases in the same way that you would as a node
+         (see above), except you need to make up a unique QWK conference number
+         for each message base.  This number should be unique across all QWK
+         networks and needs to be provided to your nodes.  Mystic itself does NOT
+         require that each base is unique across all networks, but it appears
+         that other software does require this.
+         These two steps are all that is needed to create your own network!
+      Now for each node that is a part of your network, you need to give them
+      a list of the conference IDs you created for each base you've created
+      for your network.
+      Next you need to login and create a new user, or instruct the Sysop of
+      your node to create an account using a unique BBS ID.  For example, my
+      BBS is Sector 7 so I would create a user named "sector7".  Once the
+      user is created, set the user's "Qwk Networking Acount" flag in the
+      user editor to TRUE and then associate them to the network you've
+      created (also in the user editor).
+      From now on when the user calls and logs in as their BBS ID (sector7 in
+      this example), they will be given a menu which allows them to select
+      which networked bases to subscribe to, in addition to resetting scan
+      pointers, etc.
+      Once that is done and the person has their client side setup, then can
+      connect to the MIS FTP server and login with the BBSID and password. From
+      this point they can download bbsid.qwk and upload bbsid.rep to the FTP
+      server to exchange mail.  If they are also using Mystic, QWKPOLL will do
+      all of that for them!
+ ! MUTIL should now generate a MSGID when posting text files to an echomail
+   base.
+ + MUTIL logs now use MMM DD YYYY date stamps, instead of MM/DD/YY.
+ + MUTIL now has a MergeNodeLists function which will scan for nodelist
+   files to find the most recent nodelists, then combine them and copy them
+   into the Mystic DATA folder so they can be used for node lookups.  It also
+   supports merging archived nodelists.  See MUTIL.INI for more information.
+ + Mystic's terminal library in Linux will now attempt to detect terminal
+   screen size before switching to 80x25, and will also attempt to restore
+   screen size upon exit.
+   <ALPHA 37 RELEASED>
+</code>
+===== 1.10 Alpha 38 =====
+<code>
+ + Mystic now creates "echomail.in" whenever it receives a new file from an
+   authenticated connection via the BINKP server.
+ + The semaphore files named echomail.now, newsmail.now, and netmail.now
+   have all been changed to .out, ie echomail.out, newsmail.out, netmail.out
+   You will need to update any scripts that key off of those files.
+ + Mystic now creates "qwkmail.out" whenever new messages have been posted
+   in a base assigned to a QWK network.
+ + MUTIL EchoImport function now deletes echomail.in semaphore file after
+   it is done tossing messages.
+ + MUTIL EchoExport function now deletes echomail.out semaphore file after it
+   is done exporting messages.
+ ! Fixed a problem with the BINKP server and CRAM MD5 authentication.
+ ! Fixed a problem with FIDOPOLL and BINKP where a file transfer would appear
+   to get stuck in certain situations when a file was skipped.
+ ! Fixed a compatibility issue with the BINKP server when used against a BINKD
+   client.
+ ! Fixed a bug when posting messages via NNTP.  Since there is no "To" in
+   NNTP, Mystic now sets all posts to "To: All".  This fixed a problem where
+   some messages posted via NNTP were not showing up inside of Mystic.
+ ! Fixed: Posts to networked bases via NNTP were not adding origin lines.
+ ! BINKP server should now properly escape filenames with spaces in them.
+ + When tossing ECHOMAIL PKT files and bundles, Mystic will now sort the
+   entire incoming directory by filedate and then filename as a secondary and
+   process each PKT or bundle in order.
+ + When tossing an ECHOMAIL bundle, Mystic will now extract the bundle and
+   then sort the contents of the bundle by filedate and secondly by filename,
+   then process each PKT in the sorted order.
+ + The message base editor now has a new function /R (Reset messages).  This
+   will take a single base or a selection of tagged bases and remove ALL
+   messages in them without effecting your user's new scan/qwk scan settings
+   OR the echomail linkage.  IF bases are tagged before /R Mystic will also
+   offer to reset the echomail duplicate tracking pointers as well.
+ + QWKPOLL should now provide more detail during the polling process,
+   including possible data port issues and when the HUB does not have a QWK
+   packet with new messages for you.
+ ! Fixed a bug where Mystic would incorrectly address routed Netmail in both
+   the header and INTL kludge.  This could cause tossers to not correctly
+   reroute netmail to the correct destination.
+ ! Fixed a bug in BINKP protocol on the client side where the client was not
+   sending the proper SKIP filesize back to the server.  With BINKD this
+   could cause the BINKD server to just wait until the session times out
+   instead of sending EOB.
+ + FIDOPOLL can now poll a single node by the address.  IE:
+      fidopoll 46:1/100
+ + FIDOPOLL now logs to "fidopoll.log" in the logs directory.
+ ! SEEN-BY and PATH kludge lines are no longer added to exported netmail
+   messages.
+ + Mystic will now flush the buffer after displaying the Inactivity timeout
+   prompt so that your remote users will actually see it!
+ + When sending NETMAIL, Mystic's nodelist browser will now filter out any
+   nodes which are part of net "0" in the address searches.  Using the browser
+   menu command will still show them.  Assuming you have Forced NL compliance
+   turned on, this will prevent users from ever being able to select a net 0
+   address.
+ + Mystic's netmail fowarding will now strip leading and trailing spaces in
+   case of typos in the .INI.
+ ! Netmail messages will no longer export from MUTIL if their destination
+   address is one of your configured AKA addresses.
+ + Mystic echomail nodes can now be configured as a "Directory" session type,
+   which means that Mystic (FIDOPOLL) will send bundles to/from locally
+   configured inbound and outbound directories instead of using BINKP or FTP.
+ ! Mystic's FTP server was not sending the QWK packet name in directory
+   listings when the NLST command was used (instead of LIST).
+ + When importing a FIDONET.NA format file, or when creating message bases
+   during echomail import OR when using the ImportMsgBase function, MUTIL
+   will now change any filenames (calculated from ECHOTAG) to replace both
+   \ and / with a _ character.
+ + Mystic echomail nodes can now be configured as a "FTP" session type, which
+   means Mystic (FIDOPOLL) will send/receive bundles with their uplink using
+   the FTP protocol (as opposed to BINKP or Directory).
+ + Added the ability to turn off showing the user's QWK packet in FTP
+   directory listings (Internet Servers > FTP)
+ + The autocreating message base while Importing Echomail can now have a
+   lowercase_filename = 1 value to convert all msg base filenames to lower
+   cased.  This was previously only available in FIDOBONE/FIDONET.NA
+   importing but it works under [ImportEchoMail] now too
+ ! When hubbing FTN point systems, if you had multiple point systems their
+   PKTs were all getting stuffed into one bundle.  Fixed.
+ + FIDOPOLL's FTP send client will now list echomail packets on the remote
+   server and automatically increment packet names (ie we1->we2) until it
+   finds an unused packet name on the remote server.
+ ! Fixed a bug when using spaces in menu filenames which caused the menu
+   editor to fail to edit, copy, and delete menus.
+ ! When posting a text file to a netmail base using the MX menu command, the
+   origin address was not being AKA matched with the destination address.
+ ! MIS telnet in Linux should no longer create zombie processes.
+ + Inactivity timeout is now disabled when running Mystic with the -CFG
+   option from the command line.
+ ! MUTIL import of FIDONET.NA will now not blow up if you used tabs instead
+   of spaces to separate echotag with description.
+ ! MUTIL import of FIDOBONE.NA will now not blow up if you used tabs instead
+   of spaces to separate tag with description.
+ ! MUTIL import of FIDOBONE will now replace / and \ characters when
+   calculating the datafile name, if they exist in the echotag.
+ + Changed the filename format used when Mystic generates PKT filenames in
+   bundles and when sending ?UT files:
+     Old way: Day of month + Hour + Minutes + Seconds
+     New way: Hex(Day + Seconds past midnight + Hundredth of seconds)
+   This allows truely unique names down to the hundred of a second for a one
+   month period.  It solves all collision issues caused by the old way!
+ + The FS editor quote window will now only insert a blank line when exiting
+   if new text was quoted.
+ + When editing message text, Mystic will now try to find the originating
+   message and re-create the quote data, so that you can access the quote
+   text just as you did when you originally posted the message.
+ + If an echonode's archive type is set to a blank value, Mystic will create
+   non-bundled PKT files in the outbound directory for that node.
+ + If an archive type is blank for an echomail node, Mystic will try to
+   detect the archive type of the inbound bundles and extract them
+   accordingly.  ZIP, RAR, LZH, LHA, and ARJ detection is supported.
+ ! Fixed a bug where the wrong Internet address could be shown during
+   nodelist searches.
+ + The callers count in the BBS history now will only increase if an actual
+   user has logged into the BBS.  In the past, it counted any connection which
+   means it would count port scanners, etc.
+ ! Fixed a bug where NodeSpy could crash on startup, if there is no BBS history
+   data.
+ + Prompt #473 now has the option to supply &1 in the Title section of the
+   prompt.  &1 returns the filename, however, it is truncated to 34 characters
+   which is the field size for SAUCE titles.
+ + New option in Message Settings: "Message Upload ACS".  The user must meet
+   this ACS string in order to be allowed to upload message text in the message
+   editors.  A new prompt has been added, make sure you add this to your
+   default.txt (or any prompts files you are using):
+      ; Msg Editor: No permission to upload message text
+|CR|12You do not have access to upload message text.|CR|CR|PA
+ ! Not really a Mystic bug, but mTelnet does not honor the Zmodem standard
+   properly when handling file dates.  Mystic now sends the file date along
+   with the file in a way that mTelnet will correctly handle it.
+ ! Mystic now appropriately stores and retrieves MSGID and REPLY in JAM
+   header subtext instead of the message body.  In addition, other kludge
+   lines will also be stored correctly during echomail import.
+ ! Fixed a small bug in MUTIL's message base packer that could cause a crash
+   during a status update under rare circumstances.
+ + When auto-creating Message Bases during echomail import, Mystic will now
+   attempt to automatically configure the message base for export back to the
+   uplink.
+ ! When posting an echomail message via NNTP, Mystic was not generating a
+   MSGID.  Fixed.
+ + Pressing V from within the message reader will now toggle showing of
+   kludge lines in messages.  If kludge lines are toggled on, they will also
+   appear in message quote data.  The state of kludge viewing is constant per
+   session.
+ + Mystic export should now generate proper Type2+ echomail PKT files.
+ ! Fixed a bug in the ANSI message reader where on occasion a blank line
+   would not be displayed when redrawing a message.
+ ! Fixed a small bug that could cause a loss of a character when uploading
+   a message that had a message line that ended with a pipe code.
+ + New Message Box system has been added.  Each theme now has a "Message Box"
+   section where style elements can be defined for Message Boxes.  The style
+   element allows colors and frame type to be defined, as well as box shadow
+   options.  Message boxes when used with Mystic will pop up and save then
+   restore the screen content underneith it.
+   Mystic boxes are triggered through a new MCI code: #B
+   The new MCI code format is as follows:
+      |#B<Header text>#<Message text>#
+   Here is an example of how you might want to use it:
+      ; Ansi msg reader scan toggle  &1 = message base name
+|#BInfo#|&1 will NOT be scanned in new message scan#
+|#BInfo#|&1 will be scanned in new message scan!#
+   In the examples above, when a person toggles a message base scan setting
+   while reading in the ANSI reader, Mystic will pop up a message box with
+   the configured message, and then it will restore only the part of the user
+   screen where the box was after they press ENTER.  Example:
+      .-------------------- Info --------------------.
+      |                                              |
+      |  MYSTIC will be scanned in new message scan  |
+      |                                              |
+      |                      OK                      |
+      `----------------------------------------------'
+   Existing Sysops should go into the Message Box settings at least once and
+   select the "Reset Defaults" options, so that defaults will be loaded.
+ + When posting a message, Mystic will now force all messages to be Private
+   in Netmail message bases, regardless of if the base is set to Public or
+   Private.
+ ! All JAM kludge lines are now handled and stored 100% in compliance with
+   the JAM message base proposal.
+ + MUTIL's Echomail import (mutil.ini) has a new option to strip SEEN-BY
+   lines from messages during import.  This is disabled by default, so
+   add it in under your EchoMail Import stanza if you want to strip them.
+        ; Strip SEEN-BY lines from messages when importing?
+        strip_seenby = false
+ + Mystic will no longer prompt the user to Post a message while reading
+   if they do not meet the Post ACS level.
+ ! FIDOPOLL now properly counts the number of systems polled for mail.
+ + RIGHT ARROW on the last message in a base now moves to the next message
+   base in the full screen ANSI message reader.
+ + Mystic should now play nicely with GoldEd+ and last read pointers.  Keep
+   in mind that the first "UserName" defined in GoldEd must match your
+   "real name" in your Mystic user record in order for them to link together.
+   This also works when packing and renumbering message bases without
+   screwing up any lastread pointers.
+   EXISTING SYSOPS should run MUTIL to pack their message bases, so that
+   Mystic will rebuild the last read files.  This WILL reset your pointers
+   in GoldEd+, but from this point on they will be managed hand in hand.
+ + New Menu command: MI.  This is the Area Index reader.  This command cycles
+   through all message bases and calculates total, new, and personal messages
+   and then presents them in a scrollable and customizable window to the user.
+   The list is sorted so that the bases with new messages are first, then
+   by the base name.  Typing text while in the list will automatically search
+   the message base list.  CTRL-A will search again, CTRL-Y or using any of
+   the movement keys will reset the reset.  Pressing ENTER will read new
+   messages if it is a base with new messages, otherwise it will start reading
+   at the first message if there are no new messages.  ESCAPE quits.
+   A new template ANSIMIDX goes along with this feature.  Please also note
+   ANSIMIDX.INI as well which is now part of the template, and read the next
+   section!  This template .INI has tons of configuration options for the
+   Area index so be sure to take a look!
+ + A new template format has been implemented.  Placing the screen info codes
+   in the existing format's ANSI file is annoying, so this format is designed
+   to simplify templates so that you never have to modify the ANSI to inject
+   codes again.
+   The new format uses a .INI file which goes in the same directory as the
+   template.  The INI file now holds the screen location codes and various
+   other configuration options related to the function of the BBS that uses
+   the ANSI template.  In addition to that, I am experimenting with also
+   including all prompts related to the function inside of the INI file, but
+   this might change in the future depending on feedback.
+   The negative here is we lose nice things like being able to setup the
+   percentage bars inside the theme editor.  We also lose the ability to
+   edit the prompts for template-related functions from within the theme's
+   prompt editor, because they will be stored in the INI file now.
+   The positive here is we no longer have to "inject" the |!X codes into
+   ANSI files, and we have all configuration and prompts related to a
+   template found in a single location.  This means you can easily release
+   template mods with just a .INI and .ANS and it will work just as you want
+   it to by simply copying those two files into another Mystic BBS setup.
+   Please give me feedback as to whether or not you like this new system,
+   or if we should revert back to the old or make changes.  Eventually all
+   templates will be converted to this new system and additional
+   configuration options will likely be added for each template.  I am most
+   excited about redoing the ANSI gallery! :)
+   As an alternative, we could keep the percentage bars in the theme editor
+   and keep the prompts in the prompt editor, and only put configuaration
+   options and screen locations inside of the .INI files?
+ - Mystic no longer exists with a certain errorlevel when new echomail is
+   entered.  Instead, Semaphore files should be used (echomail.out, etc).
+ + Mystic now has a new option in System Configuration -> Message Base
+   Settings: Create Semaphore (Logoff or MsgPost).  This determines whether
+   or not Mystic will create semaphore files immediately when saving a
+   message, or if it will wait for the user to logoff.  Logoff is the default
+   and recommended setting because it allows users time to edit their message
+   before it gets sent off.
+ + New MIS event system is active.  This event system has four event types
+   which can be used to fully automate your BBS including echomail and QWK
+   networking transmission, among other things.
+   ** IF YOU ARE UPGRADING YOU MUST DELETE "EVENT.DAT" IN YOUR DATA FOLDER
+   ** DO NOT SKIP THIS STEP OR YOU WILL HAVE ISSUES THE EVENT FILE FORMAT HAS
+   ** CHANGED NOW THAT WE HAVE ACTUAL EVENTS!
+   Here is a description of each Event type:
+   TYPE1: Semaphore
+   ================
+   This event type listens for one or more "semaphore" files, and will execute
+   a command line if one or more of the semaphore files are found.  Prior to
+   executing the command line, MIS will also delete the detected semaphores.
+   The following options are used for Semaphore type events.  Any other options
+   not mentioned here can be ignored for this type:
+     Active      - If yes this event will be active.  Set to No to disable.
+     Description - This can be any description you want.
+     Exec Type   - This is one of BBS, Shell, or Semaphore
+     Semaphore   - This defines the semaphore filename to "look" for.  If
+                   there is no path included, Mystic will automatically look
+                   in the configured semaphore directory.  In addition, more
+                   than one semaphore file can be monitored by using a pipe
+                   symbol to separate them (|).  For example:
+                      Semaphore: echomail.out|netmail.out
+                   The above example will look for the existance of EITHER
+                   echomail.out or netmail.out in the configured semaphore
+                   directory.  If either file is found, the event will remove
+                   the semaphore files and then execute the event.
+                      Semaphore: c:\mybbs\somefile.txt
+                   The above will list for the c:\mybbs\somefile.txt and
+                   trigger the event if it is found.
+     Shell       - This is the command line which will be executed when the
+                   event is triggered.  Similar to the Semaphore detection,
+                   this can have one *or more* executions per event each
+                   separated by a pipe.  If no path is supplied, MIS will
+                   default to the root Mystic BBS directory.  For example:
+                      Shell: domail.bat
+                   The above example will execute domail.bat in the root
+                   Mystic BBS directory.
+                      Shell: mutil export.ini|fidopoll send|mutil import.ini
+                   The above will execute 3 command lines in a row:
+                      mutil export.ini
+                      fidopoll send
+                      mutil import.ini
+                   If we put it all together we can get something like this:
+                          Active: Yes
+                     Description: Send outgoing echomail
+                       Exec Type: Semaphore
+                       Semaphore: echomail.out|netmail.out
+                           Shell: mutil export.ini|fidopoll send|mutil import.ini
+                   The above example wait for echomail or netmail.out, and
+                   execute mutil to export, then fidopoll to send, then
+                   mutil to import any new packets.  Completely automated!
+   TYPE2: Shell
+   ============
+   This event type executes on a defined time, defined on a weekly schedule.
+   When the event executes, it will execute the Shell command line.  Like the
+   Semaphore event type, this Shell command can also execute multiple command
+   lines by separating them with a pipe character (|).
+   The different between this type and Semaphore is that instead of waiting
+   for a file, the event is defined by a specific execution time.  This is
+   defined by picking which days of the week the event should execute, and
+   what time per day it should be ran (in 24-hour format).  For example:
+          Active: Yes
+     Description: Pack message bases
+       Exec Type: Shell
+           Shell: mutil msgpack.ini
+       Exec Hour: 01
+        Exec Min: 30
+        Sun: No  Mon: Yes  Tue: No  Wed: No  Thu:  No  Fri: No  Sat: No
+   The above event would execute once per week, at 1:30am on Monday morning
+   and execute the command line "mutil msgpack.ini" from the root Mystic BBS
+   directory.
+   TYPE3: Interval
+   ===============
+   This event type is similar to the shell event type, except that the hour
+   and minute define a time interval.  For example, if you want to execute
+   the event every 15 minutes you would set:
+      Exec Hour: 00
+      Exec Mins: 15
+   If you wanted to run the event every 3 hours and 30 minutes, you set:
+      Exec Hour: 3
+      Exec Mins: 30
+   When the time interval expires, the shell command line is executed with
+   the same possiblities as the other events (using the pipe character, etc).
+   This event is commonly used to polling for mail.
+   TYPE4: BBS
+   ==========
+   This event type is not actually executed by MIS itself, and is similar to
+   what you might have found in old DOS-based BBS software.  The purpose for
+   this event is to provide an option to force users to log off the BBS if
+   you want them to.
+   Like the scheduled Shell event, a BBS type event can be scheduled at a
+   certain hour/min and one or more days of the week.  In addition to the
+   time/day scheduling there are some other options:
+         Node: This defines the node number for which the event will execute.
+               If you keep the node number at 0, it will be applied to all
+               users on all nodes.
+      Warning: This determins the time before the event to notify the user
+               of the upcoming event.  This can be set to 0 to never warn them,
+               or (for example) 10 to give them a message that they will be
+               required to logoff in 10 minutes.
+   When this event time hits, the user will be logged off of the BBS if they
+   have not already logged off on their own.
+ + When using the DF mci code make sure that the proper format is used which
+   means the DF ends with a pipe code.  IE: |DF<filename>|  Mystic will be
+   more selective in what it allows for this.  Prompts that had a space in
+   them used to work, but may not now.
+   If you notice issues, you can go into the Themes->Prompt and do a search
+   for |DF and use the Search Again to fix each one.
+ + New optional data option for the MR (read messages) menu command: /NOIDX
+   If this is supplied, Mystic will bypass the user's setting for the message
+   list index and go straight to the reader.
+   <ALPHA 38 RELEASED>
+</code>
+===== 1.10 Alpha 39 =====
+<code>
+   <ALPHA 39 SKIPPED>
+ + Alpha 39 was skipped so that I could better track who is using the new
+   tosser vs who is using the old (a rewritten tosser was introduced in A40).
+</code>
+===== 1.10 Alpha 40 =====
+<code>
+ + MUTIL's Import_MessageBase now has the option to search subdirectories and
+   create message bases based on data files found in directories off of the
+   main message base directory.  A new option has been added into the MUTIL
+   .INI file format in the import stanza:
+   [Import_MessageBase]
+     search_subdir = true
+ + All servers can now use a DNS blacklist lookup.  There are two new options
+   in the System Configuration > Servers > Internet Server Options section:
+      Use DNSBL  - If set to Yes, MIS will preform a DNSBL lookup on all
+                   connections.
+      DNSBL Host - Hostname of the DNSBL server.  The default will be
+                   configured to use "xbl.spamhaus.org" for now, so if you
+                   are upgrading that is one option for this setting.
+   For those who may not be familiar with a DNS blacklist service: A DNS
+   blacklist service is basically a giant public database filled with IP
+   addresses of known spammers, scanners, etc...
+   MIS will now optionally perform a lookup of all incoming connections and
+   if they are found to be in this database, they will be blocked as if they
+   were in the BADIP.TXT file.  In addition, MIS will log the result of the
+   DNSBL service so that further information about the particular IP address
+   can be retrieved if needed.
+ + All servers can now use a DNS country lookup and connections can now be
+   both identified by country and optionally blocked by country.  Two new
+   options in System Configuration > Servers > Internet Server Options:
+      Use DNSCC  - If set to Yes, MIS will preform a DNSCC lookup on all
+                   connections.
+      DNSCC Host - Hostname of the DNSCC server.  The default will be
+                   configured to use "zz.countries.nerd.dk", so if you
+                   are upgrading that is the setting to use.
+   In addition to the DNSCC configuration, a badcountry.txt file must exist
+   in the DATA directory.  This file contains a master list of all countries
+   in the world, sorted by the ISO country number.  MIS uses this along with
+   the DNSCC host to determine the origin country of the connection.  Inside
+   this file, each country can optionally be blocked as well so you can use
+   this to identify all connections AND/OR block by country too!  MIS will
+   now show status/logs like this:
+     Connection from United States  <-- DNSCC is enabled
+     Connect: 123.123.123.123 (myhostname.myinternet.com)
+     or
+     Connection from China
+     BLOCKED 123.123.123.121 (somehostname.china.whatever)
+   See the contents of the badcountry.txt file for information on how to
+   block by country.
+ + MUTIL now has optional logfile management via a log roller.
+   Two new log options have been added to the GENERAL section of MUTIL.INI
+   files:
+     [General]
+        ; number of old log files to keep (0 to disable)
+        maxlogfiles = 10
+        ; size of each log file in kilobytes
+        maxlogsize = 500
+ + MUTIL logging performance has been significantly improved.  Running with
+   debug logging on should no longer slow down some processes to a crawl.
+ + Lightbar area index now has a CTRL-N key.  This highlights the next base
+   that has new messages, if one exists.
+ + Lightbar area index now starts reading at the last message in a message
+   base if ENTER is pressed on a base when there are no new messages.
+ + Lightbar area index now has a CTRL-Z key which displays "ansimidxhelp"
+   and then redraws the screen.
+ + Lightbar area index now has a CTRL-R key which will recalculate all
+   message statistics and redraw the entire screen.
+ + When auto-creating message bases during echomail import, Mystic now allows
+   some options to be configured based on the network address used within the
+   new message base.  These will override the default if a base is being
+   created with that network address.  For example (in [ImportEchoMail]):
+     ; If you want auto created bases that are linked to your AgoraNet
+     ; address of 46:999/999 then you can by prefixing with the address:
+     ;46:999/999_acs_list     =
+     ;46:999/999_acs_read     =
+     ;46:999/999_acs_post     =
+     ;46:999/999_acs_news     =
+     ;46:999/999_acs_sysop    = s255
+     ;46:999/999_use_realname = 0
+   This is very useful if you want to place auto-created bases in certain
+   groups, or if some networks have a real name vs alias requirement, etc.
+ + New MCI code #I works just like the #B mci code, but does not wait
+   for a key and restore the screen afterward.  IE:
+      |#IHello#This is a box!#
+ + MUTIL now has a new option to configure the time stamp of log files.  In
+   the [General] header you can now set "logstamp=" using the following
+   codes:
+     YYYY  4 digit year
+       YY  2 digit year
+       MM  2 digit month
+      DDD  3 letter day of week
+       DD  2 digit day
+       HH  2 digit hour
+       II  2 digit minutes
+       SS  2 digit seconds
+      NNN  3 letter month
+   ; logfile time stamp.  defaults to NNN DD HH:II:SS if not set here
+   ;logstamp = YYYYHHMMHHIISS
+ + MUTIL echomail tossing has been revamped so that messages are tossed to
+   your downlinks during message import.  This is more in-line with
+   traditional tossers.
+ + Some MUTIL functions used during import/export operations have been
+   revamped for a performance increase.  Still more to come though.
+ + Duplicate message detection has been improved so that it does not factor
+   in SEEN-BY/CTRL-A kludge lines into the message text.  Unfortunately this
+   makes existing duplicate databases useless, so you can delete echodupes.dat
+   from the DATA folder to reset your duplicate database.
+ + Echomail Nodes can now have a maximum PKT size and maximum ARCmail/bundle
+   size defined in their setup (in kilobytes). Defaults will be 512kb for PKT
+   and 2048kb for bundles.
+   Keep in mind these are approximate values, and that the PKT size should be
+   significantly less than the ARCmail size if you want accurate results
+   (because bundles are just zipped PKTs).  Both can be set to 0 to disable.
+ ! Fixed a compatibility issue with Mystic's BINKP against MBCICO
+ + Mystic now properly allows pass-through (re-routed) netmail messages.
+ + NetMail message bases no longer need to be linked to any Echomail nodes
+   in order for Mystic to attempt exporting.
+ + Mystic, when routing Netmail, will now first compare the destination
+   address against all configured echomail nodes.  If there is a direct match
+   Mystic will route the Netmail automatically to that node without reviewing
+   the Route Info.
+   If there is no direct match, Mystic will then look at the Route Info
+   for each Echomail node (starting at the first entry) until it finds a
+   match and redirect netmail through that system.
+ + Mystic now has a built in AreaFix.  The following commands are currently
+   supported:
+     %COMPRESS <type>
+     This sets the compress type where <type> is either left blank for raw
+     PKT or an archive extension configured for that OS (ZIP, RAR, etc)
+     %HELP
+     This appends the contents of "areafixhelp.txt" from the DATA folder
+     into the response message.  The help text is included at the end, so
+     that if additional commands were administered, those results will be
+     displayed before the help.
+     %PWD <new password>
+     Changes the password for the node to <new password>
+     %LIST
+     Returns a list of all available echomail areas.  This is done by
+     comparing the network domain of the address assigned to the message base
+     with the echomail node's configured domain.
+     %LINKED
+     Returns a list of all linked echomail areas
+     %UNLINKED
+     Returns a list of all unlinked echomail areas
+     %RESCAN [R=# or D=#]
+     This rescans all linked echomail areas and exports the last 250
+     messages in each area, unless the optiona R and D commands are also
+     specified.  Ex:
+       %RESCAN        <--- Returns last 250 messages in all linked areas
+       %RESCAN R=1000 <--- Returns last 1000 messages in all linked areas
+       %RESCAN D=365  <--- Returns messages posted in the last 365 days
+     -ECHOTAG
+     This removes ECHOTAG from the list of exported echos for this node.
+     +ECHOTAG [R=# or D=#]
+     This adds ECHOTAG to the list of exported echos for this node.  The
+     plus symbol can also be omitted to add an echo, for example:
+        +MYSTIC        <--- Adds the MYSTIC echo area
+        FIDONEWS       <--- Adds the FIDONEWS echo area
+     In addtion, a rescan value can be OPTIONALLY supplied where R specifies
+     the # of most recent messages to return.  D returns messages less than
+     # days old.  For example:
+        +MYSTIC,R=50   <--- Add MYSTIC echo and export the latest 50 messages
+        MYSTIC D=365   <--- Add MYSTIC echo and export last year of messages
+     A comma or space can be used to separate the echo tag and the rescan
+     information, if it is supplied.
+     =ECHOTAG <R=# or D=#>
+     This rescans an existing linked message base, where R is the number of
+     newest messages to export, or D is the number of days of messages to
+     export.  For example:
+       =MYSTIC R=100        <--- Exports the most recent 100 messages
+       =MYSTIC D=90         <--- Exports all messages posted within 90 days
+     The echotag can be separated by a space as shown above, or a comma for
+     example: =MYSTIC, D=365 will return the last year of messages in MYSTIC.
+ + When performing a nodelist search when sending Netmail, Mystic will now
+   pop up uplink of a point address, if a point address is entered.  This
+   allows the user to see where the message is being sent, and it allows the
+   "Force NL" option to be enabled without preventing people to netmail point
+   systems.
+   <ALPHA 40 RELEASED>
+</code>
+===== 1.10 Alpha 41 =====
+<code>
+ ! Areafix RESCAN will now only rescan areas that a downlink is subscribed
+   to!  Whoops! :)
+ + When exporting message quote data, Mystic will now replace CTRL-A
+   characters (in kludge lines) with the "@" character.
+ + Mystic should now properly add and use FMPT and TOPT kludges for echomail
+   point systems.  This may fix incompatibilities with HPT (fingers crossed!)
+ ! AreaFix will no longer try to automatically rescan a base when it is
+   linked.
+ + PKT passwords can now be configured for each echonode system and will be
+   both added to created PKTs and enforced for incoming packets if a password
+   is defined.
+ + Mystic should now gracefully handle changing event configuration while
+   MIS is running, including changing of event types.
+ ! MIS event thread could get stuck if events were edited in the
+   configuration at the same time.  Should be fixed.
+ + Pressing ESCAPE while picking an echomail address now preserves the
+   original setting, instead of setting the address to the first one.
+ + File Base editor now allows a FileEcho Tag and a Network address to be
+   defined for each file area.
+ + The File Base editor now allows for echomail nodes to be linked to
+   file bases.  This works just like message bases, but for file echoes!
+ + Mystic MUTIL tosser now supports FileFix.  FileFix works just like
+   AreaFix, except the message is addressed to FileFix and is used to
+   link to configured file echos.  The following commands are supported:
+      %HELP     - Append contents of DATA folder: filefixhelp.txt
+      %PWD      - Change session password for BINKP/FTP/etc
+      %LIST     - List all available file echos
+      %LINKED   - List all linked file echoes
+      %UNLINKED - List all unlinked file echoes
+      +ECHOTAG  - Link to a file echo (+ can be omitted)
+      -ECHOTAG  - Remove a linked file echo
+ + MUTIL now counts the number of rescanned messages and includes them into
+   the toss statistic on the status screen/logs.
+ ! Other hard to explain or minor internal changes AKA I'm forgetting stuff :)
+   <ALPHA 41 RELEASED>
+</code>
+===== 1.10 Alpha 42 =====
+<code>
++ When receiving incoming BINKP connections from ARGUS, the CRAM-MD5 string
+   is sent from ARGUS with a null terminated character at the end which
+   changes the value of a CRAM string.  Mystic will now gracefully handle this
+ + FIDOPOLL now creates the echomail.in semaphore file when it receives files
+   during a client transfer.  This is true for BINKP, FTP, and Directory
+   tossing.
+ ! Fixed a problem with |DF MCI code when used inside another display file.
+ ! QWKPOLL could possibly save a corrupted networked QWK message to a random
+   message base in a rare situation.  This should be fixed now.
+ + Mystic BINKP server will now attempt to strip ".org" and ".net" from domain
+   names during authentication.  Domain names should have a maximum of 8
+   characters to comply with the "domain.zonehex" BSO directory structure under
+   DOS (and it should never include a period) but some people seem to append
+   .net or .org for some reason (which can causes auth failures)
+   <ALPHA 42 RELEASED>
+</code>
+===== 1.10 Alpha 43 =====
+<code>
+ ! Fixed event editor crashing introduced in last alpha.
+ + Mystic's tosser now has a Twit filter.  Anyone added to the twit filter will
+   have every message To or From that person automatically ignored while tossing
+   messages.  In addition, an echomail address can be specified which will cause
+   all messages labeled as originating from that node to be deleted.
+   Twit messages will not be imported, and will not be tossed down to any
+   downlinks; they will basically disappear from your network.  There can be up
+   to 100 twits in the [ImportEchoMail] one per line, for example:
+      [ImportEchoMail]
+          ; twit names or addresses, up to 100
+          twit=John Guillory
+	  twit=1:396/60
+ ! Hide AKA BINKP option now uses the domain to generate a list AKAs instead of
+   zone.
+   <ALPHA 43 RELEASE>
+</code>
+===== 1.10 Alpha 44 =====
+<code>
+! Twit filtering now actually does something other than log.
+ ! The TID kludge line should now only be added to local messages, instead it
+   was also added to messages being tossed to downlinks during import.
+ ! Added some additional logging details into MUTIL packet importing
+ ! Fixed PATH/SEENBY corruption when exporting multiple echomail messages at
+   once (thanks to Mark for finding a producable problem)
+ ! BINKP should now send the correct file dates when sending files.  It was
+   sending every file with a March 2013 date (oops!)
+ + Mystic Echomail nodes now support outbound FileBoxes.  If FileBox is
+   enabled for that echomail node, then any existing files found in FileBox
+   directory will be sent along with echomail packets.  There are two new
+   settings for each node in the Echomail Node configuration:
+      Use FileBox | No, Any, Hold
+          FileBox | Defines the directory name for this node's filebox
+   If FileBox is set to No, no files will ever be sent from the filebox.
+   If set to Any: Files will be transmitted during any connection.
+   If set to Hold: Files will only be transmitted when the system connects
+   to you.
+   All files are deleted after they are successfully sent.
+   Note: This also works for FTP and Directory tossing as well, not just
+         BINKP.
+ ! Fixed a bug in the Area Index reader which could cause the Network
+   category to show up incorrectly when sorting by network type.
+   <ALPHA 44 RELEASE>
+</code>
+===== 1.10 Alpha 45 =====
+<code>
+ + FIDOPOLL now has a LIST command which lists all active echomail nodes,
+   by description, address, and session type.
+ + FIDOPOLL now has a ROUTE command which lists the top-down netmail route
+   priority.
+ + MIS and MYSTIC now correctly set the "effective" user ID and group ID
+   instead of just the current process group and user ID.
+ ! When running MIS as root, files received by BINKP, etc, will no longer
+   have root ownership, but instead, have the ownership equal to the ownership
+   of MIS.
+ ! When running Mystic, the virtual PTY spawned by DOSEMU should no longer
+   create itself as root causing an access error.
+ + Mystic now attempts to detect whether or not it is being executed on the local
+   console or not, and will properly setup the DELETE and BACKSPACE functionality
+   based on this detection.  If you recently changed your backspace fuction in
+   your terminal for A44, change it back.
+ + During echomail bundle extraction, Mystic will now attempt to extract *.pkt
+   instead of *
+   <ALPHA 45 RELEASED>
+</code>
+===== 1.10 Alpha 46 =====
+<code>
+! In Linux, Mystic now has additional precautions to make sure the effective
+   user is not root after binding the ports.  This should fix issues with BINKP
+   root PKTs and DOSEMU when running in Daemon mode.
+ + MUTIL can now process incoming TIC/FDN files and import them to the BBS.  It
+   can also auto-create areas, perform CRC/size checks, process or refuse
+   unsecured files, import .DIZ, support TIC Replace/LDESC keywords, toss files
+   out to any downlinks connected to the file base.  In addition, failed files
+   can be archived globally or specifically per echomail node.  FileFix is also
+   provided to allow nodes to self-service their connected file bases.
+   A new stanza [FileToss] should be added to MUTIL.INI (see the new default
+   MUTIL.INI for this stanza).  In addition the filetoss option should be
+   added under the [General] stanza.
+   There are many options within this stanza all which are documented within
+   the default MUTIL.INI.  Keep in mind, in order for an echomail node to use
+   FDN, they must have FileBoxes enabled for their node.
+   <ALPHA 46 RELEASED>
+</code>
+===== 1.10 Alpha 47 =====
+<code>
+ ! Fixed a minor backspace bug in the FS editor.
+ ! Mystic was always saving the seconds as 0 when saving JAM message timestamps
+ ! TIC processor in Linux was only processing files with the all-lowercase .tic
+   file extension.  It should now ignore casing and process .TIC, .Tic, etc.
+ + Mystic Windows version now traps additional Linux terminal keys are
+   configured by default in some clients such as Putty.  This is only specific
+   to the Windows version as the Linux/OSX versions have always done this.
+ + Mystic's BINKP client and server now logs specifically when a connection
+   times out or the connection is lost.
+ + TIC process now uses the AKA listed in the "To" field of the TIC file as the
+   address when auto-creating file bases, instead of zone matching.
+ + Echomail tossing now uses the AKA listed in the PKT destination of the mail
+   bundle as the address when auto-creating message bases, instead of zone
+   matching.
+ + Mystic's MIS will now log when it cannot bind to a port on startup and will
+   shut down the server thread.
+ ! The FTP client code (FidoPoll FTP and QwkPoll) have had some compatibility
+   and performance improvements.
+ ! Fixed the / key on the keypad and é in Windows.
+ + Added more debug logging to BINKP sessions for further IREX compatibility
+   diagnoses.
+   <ALPHA 47 RELEASED>
+</code>
+===== 1.10 Alpha 48 =====
+<code>
+ + Enhanced the FILES.BBS import to hopefully work with some more odd ways of
+   using it.
+ ! Fixed random timeout issues from BINKP server
+ ! Fixed an issue with the file handshake when a file already exists using
+   BINKP.
+   <ALPHA 48 RELEASED>
+</code>
+===== 1.10 Alpha 49 =====
+<code>
+ + FTP server now has more options for how QWK packets are shown in FTP listing
+   Hide=Do not show ever, Root=Show only in root directory, All=Show in all dir
+ + Changed the Linux access settings yet again.  I think I nailed it this time,
+   all tests on all of my platforms have been successful!
+ + Releasing this version early because I forgot to increment the A48 version.
+   <ALPHA 49 RELEASED>
+</code>
+===== 1.10 Alpha 50 =====
+<code>
++ The FIDOPOLL FORCED command now has an optional [type] to specify a session
+   type For example:
+      fidopoll forced dir      < only poll dir nodes
+      fidopoll forced ftp      < only poll ftp nodes
+      fidopoll forced binkp    < only poll binkp nodes
+   This is mostly useful for the directory tossing mailer.  Including no type
+   will poll all types as it always has.
+ + Mystic now supports display of ICE colors, which allows for 8 new
+   background colors within ANSI.  Note that your terminal needs to support
+   this too, and it may show up as nothing or blinking text on some terminals.
+   The latest version of NetRunner 2.x will also support proper ICE colors.
+   There are also 8 new pipe colors to go along with this:
+      |24 Grey background
+      |25 Bright blue background
+      |26 Bright green background
+      |27 Bright cyan background
+      |28 Bright red background
+      |29 Bright magenta background
+      |30 Bright yellow background
+      |31 Bright white background
+ + Pressing ESCAPE in MIS will now pop up a confirmation yes/no box before
+   exiting.
+   <ALPHA 50 RELEASED>
+</code>
+===== 1.10 Alpha 51 =====
+<code>
+! Fixed a bug with ICE colors where the |16 wasn't turning off the resetting
+   ICE colors.
+ + MIS now has the option to automatically BAN an IP if they connect to a
+   server more than X times in X seconds.  The default recommendation is
+connections in 120 seconds.  This setting can be found in System
+   Configuration -> Internet Servers.  Setting either of the values to a zero
+   will disable this feature.
+ + Windows version now has better support for terminals that use alternative
+   extended keymappings, for better handling of keys like F1-F10, INSERT, etc
+   between different telnet clients.
+ + When in the Message Area list reader, CTRL+U now updates the lastread
+   pointer of the currently selected message base to the last message.
+ + Added some trickery in the socket shutdown code to ensure data is completely
+   sent prior to terminating the connection (for logoff screens, etc).
+ ! Fixed a bug in MIS which could cause it to crash randomly in Linux.  I just
+   did a full load test of a 25 node BBS which consisted of allowed, blocked
+   accounts (and an activity level that refused 25 nodes with BUSY).  No ghost
+   nodes and thousands of connections handled!  Seems pretty stable now.
+   <ALPHA 51 RELEASED>
+</code>
+===== 1.10 Alpha 52 =====
+<code>
++ CTRL-P now posts a message of the currently select message base in the area
+   index reader.  A new [Prompts] has been added to ansimidx.ini template file:
+	; Shown before posting a message  &1 = message base name
+	str9 = |16||11|CLPosting a message to area |15|&1|11.|CR
+ + The FS editor now automatically reformats the paragraph when using the
+   delete key.
+ + Slightly streamlined the ANSI efficiency of the paragraph reformat command
+   in the FS editor.  Keep an eye out for display issues.
+ + New MCI code: SS.  This MCI code saves the remote user's screen in its
+   current state.
+ + New MCI code: RS.  This MCI code restores the remote user's screen in its
+   current state.  IE:
+        |SS|CLPress a key to restore screen|PN|RS
+ ! Fixed a small ICE color bleed when resetting a grey background
+ ! Fixed issues with PKT processing in MUTIL, where MUTIL could sometimes pull
+   the wrong point or zone information, causing the PKT not to get tossed due
+   to an invalid AKA.
+ ! JAM: Mystic should now properly store any REPLY variation that is not
+   specificly "REPLY:" as an UNKNOWN JAM kludge (replyto, replyaddr, etc)
+ + Mystic BINKP now allows unsecured BINKP echomail transfers.  A new path for
+   unsecure inbound files has been added to System Configuration > Paths
+   as well as a toggle to enable this feature in Servers > BinkP.
+   If this feature is on, then Mystic BINKP will accept connections and files
+   from nodes that are not configured in the Echomail nodes, and these files
+   will be placed in the unsecured directory.
+ + MUTIL echomail import now allows the option to also toss packets from the
+   unsecure directory.  This option can be set by adding the unsecure option
+   to your "[ImportEchoMail]" stanza:
+      [ImportEchoMail]
+         ; Toss packets from unsecure directory in addition to inbound?
+         unsecure_dir = false
+ + MUTIL filetoss now allows the option to also process TIC/files from the
+   unsecure directory.  This option can be set by adding the unsecure option
+   to your [FileToss] stanza:
+      [FileToss]
+         ; Toss TIC from unsecure directory in addition to inbound?
+         unsecure_dir = false
+ ! Fixed a bug in the FTP server that caused FireFox to not pop up a login box
+   if no credentials were provided on the URL.
+ + Exporting a message with the V (show kludge) lines option turned on will now
+   include kludge lines in the exported file.
+ + MUTIL nodelist merger now logs the archive command line when debug logging
+   is turned on.
+ ! Mystic should now (hopefully) properly handle the seconds in PKT files and
+   in both JAM and Squish format bases, and these changes should reflect
+   accurately in PKT files as well.
+ ! Added back the ridiculous BINKP debug logging so we can hopefully figure out
+   any remaining issues with IREX compatibility (malformed command)
+   <ALPHA 52 RELEASED>
+</code>
+===== 1.10 Alpha 53 =====
+<code>
++ In the Index reader, Mystic will now "snap" to the next new area with
+   messages in relation to your currently selected base (if the option is on)
+   instead of always finding the first base with new messages in the list.
+ ! Pipe codes are now striped from user name and alias inputs during new user
+   applications.  This also happens when using a MPL program to replace the new
+   user application process.
+ + The /ME command will no longer broadcast to all chat rooms.  It will only
+   show to people in the same chat room as the person doing /me.
+ ! Mystic will now strip PIPE codes out of message subjects before displaying
+   them in the message reader lightbar message list.  This was causing some
+   formatting errors.
+ ! Fixed a bug where backspace could always delete the input string when editing
+   a default string using the stanard line input.
+ ! Fixed a display bug where Mystic wasn't recalculating the "&X" MCI codes after
+   editing a message.
+ ! Fixed some pathing issues with UnSecure inbound files using BINKP
+ ! Fixed BINKP resume problems (malformed command).
+ + New option Internet Servers -> BINKP -> File Conflict specifies the action to
+   take when there is a file name conflict with an incoming file and an existing
+   file, and these files are determined to be different files.
+      - Rename  : Automatically rename the file using the filename.#.ext where #
+                  is the first available number.  So myfile.zip would be renamed
+                  to myfile.1.zip
+      - Skip    : Skip the incoming file send from remote system.  This will cause
+                  the remote mailer to attempt to resend the file in a later
+                  session
+   Note: Existing files with the same timestamp will be resumed, unless they have
+   a matching time stamp and file size, in which case Mystic will report the file
+   as successfully received.
+ ! Fixed a small bug where the output buffer was not being flushed when using the
+   theme box MCI code #I
+ ! Fixed a small MCI parsing bug which could cause some oddities in display files
+   in very rare occasions
+ + New option in message index reader to create the area list by categorizing
+   bases using group information.  Two new options have been added to the [Options]
+   section of ANSIMIDX.INI in the TEXT directory:
+      [Options]
+         group_list = true
+         exclude_groups = 1,5
+   If group_list is TRUE Mystic will generate the area list using group information
+   as categories.  If group_list is false, Mystic will generate the area list by
+   using the network address and network descriptions.
+   The exclude_groups option specifies the group number to exclude from the list
+   when group_list=true.  This is useful to exclude a "global" group from the list
+ + Linux version of Mystic now supports mouse with a supported terminal (NetRunner)
+   in some areas.  Some configuration boxes, the Area index message reader, and a few
+   other places will have preliminary mouse support.
+   <ALPHA 53 RELEASED>
+</code>
+===== 1.10 Alpha 54 =====
+<code>
+ ! Fixed a bug with group membership while using the index reader
+   <ALPHA 54 RELEASED>
+</code>
+===== 1.10 Alpha 55 =====
+<code>
+ ! Fixed a possible record locking issue when listing files.
+ ! Fixed an issue where the X hotkey when editing a menu would change both the X
+   position and the Timer type.
+ ! Fixed an issue with group ordering in the message index reader
+ + Added the dreadful BINKP debug logging again to diagnose a unsecure session issue
+   <ALPHA 55 RELEASED>
+</code>
+===== 1.10 Alpha 56 =====
+<code>
+! Fixed a problem with BINKP non-secure authentication from the Argus class of
+   mailers
+ ! Incoming BINKP authentication could sometimes fail if the address list was more
+   than 255 characters.  Fixed.
+ + When displaying kludge lines with the V command in the message reader, Mystic
+   will now change the #1 ascii character to a @ for a cleaner display
+ ! Fixed a very rare QWK message import bug in the QWK networking engine which
+   could cause some minor corruption of text
+ + Mystic now supports BINKP 1.0 with the Non-realiable extension
+ + Mystic now supports BINKP 1.1 with fallback to 1.0/NR or 1.0
+ + BINKP now responds to the remote side with "secure" or "non-secure" when
+   accepting a new connection.  This is not required by BINKP but "recommended"
+ + Importing packets from unsecure directory should now only process NETMAIL
+ + MUTIL now logs the log level when starting up
+ ! Fixed a bug with date converstions past the year 2070.
+ ! Extended msg/nodechat buffer length per line, which in turn means about 50k
+   more memory is used per active telnet node.  This is temporary until I recode
+   it but this will fix the weird wrapping issue in node chat.
+ + Node chat messages now word wrap, instead of just chopping the line off but
+   as a result, MCI codes are stripped from the messages.  This probably should
+   have always worked this way.
+ + In addition to /MSG in node chat, /T or /TELL will also now send a private
+   message to a user.
+ + In addition to /Q, /QUIT will now quit node chat.
+ + In addition to /ME, /EMOTE will now perform an action in node chat.
+ + New node chat option: /R or /REPLY <text> will send a private message to the
+   last person who sent you a private message.
+ + Updated telehelp.asc in the default installtion to contain the new chat
+   commands.
+   <ALPHA 56 RELEASED>
+</code>
+===== 1.10 Alpha 57 =====
+<code>
+ ! Fixed a bug which could cause crashing in MPL programs.  I accidentally added
+   the wrong files for A56 so I am release a57 just an hour or so later to fix it
+   <ALPHA 57 RELEASED>
+</code>
+===== 1.10 Alpha 58 =====
+<code>
++ Rejoice! BINKP debug logging spam has been removed.
+ + Added new prompt info codes to node chat message prompts, as follows:
+      &2 = Returns the node number
+      &3 = Returns low node-specific color (node zero = blue (color 1), node
+           one = cyan (color 2) and so on.
+      &4 = Returns high (bright) node specific color (node one = bright cyan)
+   Changed the default prompt #181 for node chat to use all of these things to
+   create node specific colors as an example:
+|&3<|&4|&1|&3:|&4|&2|&3> |07
+   The above prompt will produce something like this for g00r00 on node 1:
+      <g00r00:1> This is a test message
+      |02<|10g00r00|02:|101|02> |07This is a test message
+   The brackets and the : will be color 2 (green) and g00r00 and 1 (the node
+   number) will be color 10 (bright green).  The users text will be in grey
+   color 7, but could easily be changed to use the node specific color, too.
+   Now on node 2, the same thing would be true except cyan would be used.  Node
+would use red, 4 magenta, 5 yellow, 6 white, 7 blue, 8 green, and so on.
+ - Disabled BINKP 1.1 and now identifies as 1.0 with NR for compatibility reasons
+ ! Pressing enter on a private or netmail base should now properly allow you to
+   read your messages in the Area Index reader
+   <ALPHA 58 RELEASED>
+</code>
+===== 1.10 Alpha 59 =====
+<code>
+ ! Fixed a bug which was causing kludge lines to get completely stripped when
+   tossing to downlinks.  The lack of kludges was also likely the cause of
+   some weird addressing recently when replying to netmail.
+ - Added back a check on the Sent flag in QWK networking.  This breaks FidoNet
+   gating between QWK which was hidding from all of you anyway, but it may also
+   stop the recently flood of duplicates as well.
+ + The &6 MCI code in ANSIMLST related prompts now lists the message date in the
+   users selected format.
+   <ALPHA 59 RELEASED>
+</code>
+===== 1.10 Alpha 60 =====
+<code>
+ ! Fixed a bug which could cause QWK exported messages to get a few characters
+   truncated from the end of the message.
+ ! [X and [Y MCI codes are no longer parsed in message text.
+ ! Removed critical sections from Raspberry Pi MIS because it was causing some
+   crashes.  I have not tested the effects of this enough to know if MIS will
+   remain stable on a Pi, but it should be usable under Pi now.
+ ! When sending netmail, the INTL was listing the origin and destination
+   addresses in the wrong order.  Should be fixed
+ ! Fixed a bug with MPL char type function results
+ ! Mystic's internal LZH/LHA file viewing functions were not compatible with
+   level 2 files.  Mystic should properly handle level 0,1,2 formats now
+ + New MPL procedure: AppendText (FileName, Text: String).  This procedure
+   will append a single line of text onto a text file.  If the file does
+   not exist, it will be created.  Example:
+      AppendText("c:\test.txt', 'This is a line of text added to test.txt!')
+ + New MPL variables CfgChatStart and CfgChatEnd.  These return the byte
+   of the chat hour start and end variables from the System Configuration
+ + Install program should now copy unix.install.txt to the docs directory
+ + New file in data folder: goodip.txt.  This file works as a way to except an
+   IP address from the DNS blacklist, DNS country check, and the auto ban IP
+   systems.  The format of the file is the same as badip.txt.
+ + Added error checking system into BINKP receive file functions.  If a remove
+   connection sends too much junk, Mystic will terminate the connection.  This
+   is just a shot in the dark at the CPU 100% thing that two people have
+   reported.
+ + Increased the internal Zmodem disk read and write buffer to 32kb in size up
+   from 8k.
+   <ALPHA 60 RELEASED>
+</code>
+===== 1.10 Alpha 61 =====
+<code>
++ Slightly improved output buffering when generating default menus, loading
+   messages in the full screen reader, the message index list, lb file list etc
+ + Mystic now supports inline description importing from text files.  Each text
+   file extension must be defined in the Archive editor with an extract command
+   of "@TEXTDIZ".  When Mystic matches an extension with @TEXTDIZ as the extract
+   command, it will search the contents of the file and import the description
+   between @BEGIN_FILE_ID_DIZ and @END_FILE_ID_DIZ
+ + Mystic now supports using the ansi viewer for viewing text files in the file
+   listing and from within archive viewing.  If an extension is found with a
+   view command of "@TEXTVIEW" then Mystic will display the file using the ANSI
+   viewer (ansiviewer, ansiviewerhelp templates) and it will extract SAUCE.
+ + Mystic now supports using the standard display file function for viewing
+   text files in the file listing.  If an extension is found with a view
+   command of "@TEXTSHOW" Mystic will display the file using the standard
+   file display function.
+ + Updated default archive configuration to support TXT ASC and NFO for DIZ
+   import and file viewing, and ANS for file viewing.  Note that archives that
+   have a first character of @ will now be ignored when the list of archives
+   is presented to the user.  In other words, ANS TXT etc should start with @
+   in their description so the user cannot select them for QWK arc type, etc
+ ! INTL format was still not right so it has now been fixed.  Maybe.  I think!
+ + The DI mci code now does a more accurate baud emulation. In display files
+   you can specify |DI## where ## is a number between 0 and 99 that determines
+   baud rate emulation.  The number maps to a real baud rate now:
+-09 = 300      40-49 = 9600     80-89 = 57600
+-19 = 1200     50-59 = 19200    90-99 = 115200
+-29 = 2400     60-69 = 28800
+-39 = 4800     70-79 = 38400    00    = Full speed
+   So for example if you add |DI25 you will display at emulated 2400 baud
+   and |DI55 you will display at emualted 19200 baud, |DI95 is 115200 etc
+ + The Q key now exits the ansi viewer (in addition to escape)
+ + The Q key now exits lightbar file list (in addition to escape)
+ ! Fixed a bug in the new node chat text wrapping added a few alphas ago
+ ! Page down in the lightbar lister no longer causes it to draw while its
+   scrolling to the end of the file listing.
+ ! LB file lister was showing the prompt twice in a row when the template was
+   displayed the first time.
+ + If an echomail message is sent out through the network while the author is
+   editing it, a message will be displayed to them if they try to save the
+   message (asking confirmation that they really want to resend it again).
+ + New event system type: Hourly.  This event type will execute once every
+   hour at the defined minute.  So for example, if you set the exec minute
+   to 15, it will execuite at 15 minutes past every hour.
+ + Mystic now exports messages in DOS CRLF format even when produced in Linux
+ ! When Mystic gets message lines of 80 characters in the full screen reader it
+   will now assume the terminal automatically wraps the text.
+   <ALPHA 61 RELEASED>
+</code>
+===== 1.10 Alpha 62 =====
+<code>
++ New prompt contains ANSI/ASCII values for TE MCI code:
+      ; Terminal emulation for TE mci code
+      ; word1=ASCII   word2=ANSI
+ASCII ANSI
+ + New prompt contains values for UB mci code:
+      ; UB results (File list type)
+      ; word1=Normal  word2=Lightbar
+Normal Lightbar
+ + New prompt contains values for UE mci code:
+      ; UE results (message editor type)
+      ; word1=line,   word2=full   word3=ask
+Line Full Ask
+ + New prompt contains values for UG MCI code:
+      ; UG results (gender/sex)
+      ; word1=female   word2=male   word3=unknown
+Female Male Unknown
+ + New prompt contains values for UJ MCI code:
+      ; UJ results (message reader type)
+      ; word1=Normal   word2=Lightbar
+Normal Lightbar
+ + New prompt contains values for UQ MCI code:
+      ; UQ results (lightbar quote style)
+      ; word1=standard   word2=windowed
+Standard Windowed
+ + New prompt contains values for various Yes an No text
+      ; Yes and No text used in various places
+      ; Word1=no   word2=Yes
+No Yes
+ + New prompt contains values for various Off an On text
+      ; Off and On text used in various places
+      ; Word1=Off   word2=On
+Off On
+ + New prompt contains values for No/Yes new scan toggles
+      ; New scan toggle yes/no (on/off) toggle text
+      ; Word1=no   word2=Yes
+No Yes
+ + New prompt contains the message subject when editing auto signatures
+      ; Editing auto signature message subject
+Signature Editor
+ + New prompt contains short (3 char) months
+      ; Months of the year (short name) one word per, Jan-Dec separated by a space
+Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
+ + New prompt contains full month names
+      ; Months of the year (long name) one word per, Jan-Dec separated by a space
+January February March April May June July August September October November December
+ ! /B in nodechat was chopping off the first character of the broadcasted message
+ + Refined the baud rate chart slightly so it works in tiers of 10 for the DI
+   MCI code.  Also refined the buffer flushes to (hopefully) perform a little
+   smoother in Windows.
+-09 = 300      40-49 = 9600     80-89 = 57600
+-19 = 1200     50-59 = 19200    90-99 = 115200
+-29 = 2400     60-69 = 28800
+-39 = 4800     70-79 = 38400    00    = Full speed
+ + New DI system is now implemented in Linux.
+ + The Ansiviewer and Ansi gallery menu command options now require you to
+   supply the actual baud rate that you want to display the ANSI files, rather
+   than a 00-99 number that it used to accept.
+   <ALPHA 62 RELEASED>
+</code>
+===== 1.10 Alpha 63 =====
+<code>
+ ! The TAB grid jump in Lightbar/Grid menus was not working correctly
+ + Mystic now delays for 1 second after displaying an MPL execution error
+   message.
+ ! BINKP no longer displays a Remote disconnect/session timeout message when
+   it shouldn't
+ + Aborting an ANSI will now not abort until the current ANSI sequence is
+   completed to prevent any ANSI code bleeding on abort (or until 10+ chars
+   are processed).
+ + Aborting ANSI file display is now based on time (checked every half
+   second).  This was in 1.10 A62 but wasn't documented.
+ + Reworked file buffering in file listings for a nice performance gain
+   particularly when searching file descriptions and on operating systems
+   with poor internal I/O caching.
+ ! Mystic was incorrectly showing the message base editor menu command in
+   the menu command list.
+ + Mystic can now properly handle ANSI in .DIZ file descriptions.  It will
+   parse the ANSI then convert them to PIPE colors and save them that way.
+   <ALPHA 63 RELEASED>
+</code>
+===== 1.10 =====
+<code>
+ ! Mystic's NNTP server was not properly responding to HEAD and BODY commands
+   causing newsreaders to fail that were not using the ARTICLE function to get
+   message data (Pine/Alpine).
+ ! MUTIL auto create and message base importers were not properly setting the
+   creation date of the newly created bases.
+ + Mystic's NNTP server now supports the NEWGROUPS function which allows
+   clients to see when new message bases have been added.
+ ! Some newsreaders would not properly display message text if the ID was not
+   included in the header result from the ARTICLE command.  Mystic now always
+   sends the ID.
+   <1.10 RELEASED FEB 20, 2015>
+</code>