Differences

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

--- whats_new_112 [2018/03/25 16:05] – updated to 1.12 a38 avon
+++ whats_new_112 [2018/12/27 20:42] – updated to 1.12 a41 avon
@@ Line 2674: / Line 2674: @@
    <ALPHA 1.12 A38 RELEASED -- Jan 1, 2018>
+</code>
+===== 1.12 Alpha 39 =====
+<code>
+ + New Python command: backspace (number, destructive).  This function sends
+   (number) backspaces and if (destructive) is True, then it will also
+   delete the character.  If False it will only move the cursor backwards.
+ + Record data changes for user database:
+     - First on and last on dates are now stored in Unix timestamp format.
+     - Expire, last password change, and last e-mail validation dates now
+       use julian day number
+     - IP field extended to support IPV6, host extended to 80 characters
+     - Vote tracking extended from 20 to 99
+     - Added space for variable iteration PBKDF2-HMAC-SHA512 encrypted user
+       passwords.
+     - Added User country field for historical storage
+     - Local QWK Path is now split into Local QWK Path and Local REP Path
+ + Record data changes for message base database:
+     - Expanded name to 60 characters
+     - Removed Sponsor field
+     - Added Read EchoACS and Post EchoACS
+     - Created date changed from packed DOS to Unix timestamp format
+ + Record data changes for file base database:
+     - Extended name to 60 characters
+     - Extended echotag to 40 characters
+     - Added Passthrough EchoACS
+     - Created date changed from packed DOS to Unix timestamp format
+ + Record data changes for events database:
+     - Added a unique ID to each event
+     - Added OSType attribute to each event
+     - Added new statistical tracking attributes
+     - Removed Node number from BBS type event
+     - Added field to support enhanced semaphore event system
+ + Record data changes for servers database: Added more space for more server
+   types and options.
+ + Installation program will now question the installer at the beginning to
+   help determine the local console codepage on Linux platforms.
+ + Mystic message searching now allows full logical boolean searches along
+   with order of operations.  The following tokens are used:
+     & = AND
+     | = OR
+     ! = NOT
+   Parentheses can be used to group results.  If you want to search for a
+   single word or user you can still just type in the word, but otherwise
+   you now have the options to do searching like:
+      (g00r00 & released) | pre-alpha
+   This would return any message that contained both g00r00" AND "released",
+   OR it contained the word "pre-alpha"
+   Searches are case insensitive and will search the From, To, Subject, and
+   message content (excluding kludge lines).
+ + New door command line code %C.  This is replaced by the user's current
+   codepage as either "CP437" or "UTF8".
+ + Mystic will now track the country detected during country blocking within
+   each user's session.  A new MCI code "UO" will return the user's country
+   of origin as determined by the country blocker in MIS.
+ + Mystic's installation file install.exe can now be ran to copy over your
+   binary files for you by command line:
+     install replace <root Mystic path>
+   Windows seems to be blocking this from running on my Windows test system
+   for some reason, so I am looking into a way around whatever it is doing.
+   You may need to rename it to something like "temp.exe" in Windows to get
+   this to work :\
+ + ANSI editor now has a "CRLF at EOF" which always defaults to Yes.  If this
+   is Yes, Mystic will save a CRLF at the end of the ANSI file so that the
+   cursor moves to the next line.  If No, then Mystic will not.
+ + ANSI editor now shows a "File saved" confirmation box after saving.
+ + ANSI editor now retains the changed filename between save dialog boxes
+ + CTRL+X will now exit the ANSI editor, asking to save if the file has been
+   changed first.
+ + When in the full text and ANSI editors, the delete key will now allow files
+   to be deleted within the Open file dialog box.
+ ! Mystic was not properly handling MSGID fields created by Synchronet when
+   replying to Echomail via Netmail
+ ! Mystic will no longer refuse Netmails that use the Synchronet-style MSGID
+ ! Bugfixes to ANSI editor save functions, particularly when saving without
+   clear screen enabled.
+ + New ANSI editor buffers will now default to saving with "Clear Screen Yes"
+ ! FTP server was showing QWK packet when logged in as Anonymous
+ + Mystic now has a new feature which can be enabled in the File Base Settings
+   called "Download FTP".  When this is enabled to Yes, Mystic will ask the
+   user if they'd like to download their queued files via an FTP link instead
+   of using a file transfer protocol.
+   The FTP link will contain a virtual directory that contains all of the
+   files in their batch queue, and will expire after 1 hour.  The user can
+   use their web browser or FTP client to connect to the FTP URL and list
+   and download the files that they queued on the BBS.  Access enforcement
+   and statistical tracking will be applied via the virtual FTP directory
+   just as it would if the user was downloading the file from the BBS.
+   This feature requires that Mystic's FTP server is enabled and properly
+   configured, and that Anonymous FTP access is enabled in the Server
+   settings.  This means proper firewall configuration and valid BBS domain
+   Four new prompts will go along with this.  If you are using the default
+   prompts you can simply copy over the default.txt to your data directory,
+   but if you have modified the prompts then you'll need to add these new
+   prompts into your default.txt and any other themes you use.  They are
+   located in the upgrade.txt or the default.txt from a fresh installation.
+   An HTTP equivalent will be enabled in a future build.
+ + MIS now has a basic HTTP server.  The server can be created in the server
+   editor within the configuration.  A webroot path must be defined, which
+   points to a directory where your website files and configuration will
+   exist.  For example, if you set webroot to c:\mystic\webroot\ then you
+   will need to create two subdirectories under it (cfg and www):
+      c:\mystic\webroot\cfg\
+      c:\mystic\webroot\www\
+   In the www folder will be where you place your website files.  The CFG
+   folder will hold various configuration values for the web server in the
+   future.  Note this is a very barebones server at this point only really
+   capable of serving basic websites, but I intend to work on it further as
+   I find time.
+ + ANSI editor now has block options.  CTRL+B can be used to select a block
+   of text to be centered on.
+ + ANSI editor now has a block option for filling a block with a character,
+   an attribute or both.
+ + ANSI editor now has a block option to select a block and center text found
+   within the selected block (using the center of the selected block as the
+   center point)
+ + Event system will now recalcuate the event state every 10 seconds, this
+   has been increased from 5 seconds in order to reduce load of an updated
+   semaphore system
+ + The "Semaphore" event system has been enhanced to allow specifying boolean
+   logic of semaphore files that must exist (or not) to trigger an event. A
+   new field has been added to define which semaphore files should be removed
+   when the event is ran.  The usual boolean evaluation tokens that are used
+   in ACS, message searching, etc, all apply here as well: () to define order,
+   !=NOT, &=AND |=OR.   An example usage might be:
+      Event Type: Semaphore
+       Semaphore: (echomail.in|netmail.in)!fidopoll.bsy
+      Kill After: echomail.in|netmail.in
+   The above example says to trigger the event if echomail.in OR netmail.in
+   exists but NOT if fidopoll.bsy exists.  The result would be that the
+   command line would run when there is incoming net/echomail but it'd also
+   wait for fidopoll to finish running (if it is) before kicking off.
+   The Kill After field says that when it runs it should delete echomail.in
+   and netmail.in.  Each file specified here should be separated by a pipe
+   character (|).
+   For existing systems, the upgrade program will automatically populate the
+   "Kill after" field with the currently configured semaphores but for new
+   events you'll now need to define which semaphores to delete when it runs.
+ + Semaphore events will now delete the semaphore files when it executes
+   instead of at the time the semaphores are detected.
+ + Semaphore events now dynamically update their "run state" until the point
+   in which they execute.  This means that if a semaphore event triggers but
+   another event is running which causes it to be flagged "Run next", it will
+   continue to evaluate the semaphore files up until the moment it runs. If
+   the state of those semaphores changes between being flagged as Run Next and
+   actually executing, the event will detect it and adjust itself accordingly.
+ ! Fixed a bug in the socket code that could sometimes cause a lost connection
+   to not be detected if it happens while sending data to the client.  This
+   could be a major cause for those who've had some "ghost node" issues.
+ ! Who's Online was not pausing when the BBS had enough nodes to fill up
+   multiple pages.
+ + NodeSpy now has an option to connect via IPV4, IPV6, or to default to
+   either V4/V6 and then fallback to using the other if it cannot resolve
+   the address.
+ + Echomail nodes can now be configured to default to resolving via IPV4 or
+   V6, with a fallback to the other one if the address cannot be resolved.
+ + FidoPoll will now attempt to use IPV6 if it is available and then fallback
+   to IPV4 when connecting to unsecure nodelist via a nodelist lookup.
+ + MIS event status will now display the date and time when the event was
+   last executed as well as the last result returned from execution.  If you
+   are a A39 pre-alpha tester, note that any events you've created in the
+   Event editor with A39 may have to be recreated for this tracking to work
+   because the "Event ID" was always getting set to 0 in earlier builds.
+ + SENDMAIL now has an IPType similar to those added to Fidopoll, echomail
+   nodes, Nodespy, etc.
+ ! Mystic BINKP should no longer fail CRAM-MD5 negotiations when a BINKP
+   option is listed after the CRAM-MD5 handshake in the options frame.
+ + Mystic FIDOPOLL FTP send functions will now log FTP session data to the
+   log file, similar to what it does with BINKP.
+ + Mystic FIDOPOLL FTP will now automatically prepend a / to a directory if   it is not configured in Mystic's echomail node configuration with a slash
+   it is not configured in Mystic's echomail node configuration with a /
+ + QWKPOLL will now log to "qwkpoll.log" in the log files directory.
+ + QWKPOLL will now log all FTP client/server exchanges in qwkpoll.log
+ + MIS will now attempt to detect any ghost nodes and will reset the node
+   data under many different circumstances.  If this happens, it will be
+   logged in mis.log with an explaination as to why it was assumed to be
+   a ghost node.  This combined with other recent stability improvements
+   should help quite a bit with long term uptime of the terminal nodes and
+   servers.
+ + Echomail node configuration: Echomail node address input now is a single
+   input instead of splitting out zone, net, node and point into their own
+   fields.  This is done to make a little more room on the form for other
+   options.
+ + Echomail node configuration: Nodes now have a "SysOp Name" field.
+ + Mystic Python has a new function: Delay (milliseconds) causes the problem
+   to wait for a specific number of milliseconds.
+ + All Mystic executables will now either display the compiled version
+   date/time or have a -ver/-version option to do the same.
+ + New menu command: MF (View draft message posts).  This command allows
+   users to view and resume any saved draft message posts.  If the user
+   has no drafts a simple message will be printed saying there are no
+   saved drafts.
+   Drafts are automatically saved when a user runs out of time, gets
+   disconnected for inactivity or loses/drops connection in the middle of
+   posting or while replying to a message.  If Mystic has any sort of error
+   while saving the message, it will also creat a draft of the message for
+   the user.
+   If the optional data of /SCAN is supplied, Mystic will check to see if
+   there are any drafts, and prompt the user if they would like to
+   review their saved drafts ONLY if they have drafts.  If they do not do
+   drafts, the command will simply do nothing.  Ideally you could put this
+   somewhere during your login process, as the new default install does in
+   prelogin.mnu
+   Six new prompts (532-537) go along with this. If you are using the default
+   prompts you can simply copy over the default.txt to your data directory,
+   but if you have modified the prompts then you'll need to add these new
+   prompts into your default.txt and any other themes you use.  They are
+   located in the upgrade.txt or the default.txt from a fresh installation.
+ + New ACS command "OD" returns TRUE if the user has any draft message posts
+   saved.
+ + New MCI code "MF" shows the number of draft messages saved for the current
+   user.
+ + Posting a message now no longer enforces group requirements when evaluating
+   the "PostACS"
+ + The message editor now has a "Save as draft" option from the command menu.
+   This means you will need to add that command to the menu if you use a
+   custom template for your message editor, otherwise replace msg_editor.ini
+   with the newer one from the installation.
+   See upgrade.txt for instructions on adding the command or use the default
+   msg_editor.ini as a guideline.
+ + Two new Python functions: pwrite and pwriteln.  These work just like the
+   write/writeln or rwrite/rwriteln except they only resolve pipe color codes
+   and not all MCI codes.
+ + Echomail ACS is active.  Note: YOU MUST BE USING MUTIL TO PROCESS ECHOMAIL
+   AND .TIC FOR THIS SYSTEM TO WORK.  Mystic cannot apply security to third
+   party tossers.
+   This system is just like User access system except that it applies to
+   echomail nodes.  Each echomail node has its own security level, group
+   memberships (to echomail groups) and a set of acess flags.  The following
+   commands are available within EACS:
+      s<level>  : Echomail node must have a Security Level greater than or
+                  equal to <level>
+      g<number> : Echomail node must be a member of Echomail group ID equal
+                  to <number>
+      f<flag>   : Echomail node must have flag <flag> which is a letter
+                  between A to Z.
+      u<number> : Echomail node must have a unique ID of <number>.  This
+                  allows security to be applied to specific nodes (ID is
+                  shown in echomail node editor).
+   Just like user ACS, Echomail ACS can also use parenthesis and boolean
+   evaulation.
+ + Echomail ACS has been activated for message base subscribing/reading. A
+   new field in each Message base configuration called "List EACS" defines
+   the ACS requires for an echommail node to be able to see, subscribe, or
+   unsubscribe to the area via AreaFix
+   Hubs can still manually link a base to a node regardless of security, so
+   for example if you wanted to force nodes to always carry a specific echo
+   area, you would give them the base and then set the "List EACS" to an
+   access they do not have (or even use % which is "never" in ACS terms). With
+   this setup in place, the node cannot add or remove the area, they can only
+   perform rescans.
+ ! When hatching/tossing files, MUTIL will now properly randomly generate a
+   random 8 letter .tic filename if one already exists of the same name as
+   the archive.
+ + The FU (File upload) menu command now has a new optional data command
+   called "/current".  If this option is specified, Mystic will attempt
+   to upload to the current file base even if a specific file base has been
+   configured for uploads.
+ + The GH and GI (Goodbye and Hang up Immediately) menu commands have a new
+   optional data option.  If "/RECYCLE" supplied, Mystic will log the current
+   user out and restart the session as if the user just connected to the BBS.
+ + The XL (Matrix Login) command now as a new optional data option.  If /FULL
+   is supplied, the typical Matrix login will be immediately skipped and the
+   user will be presented the standard login process.  This is intended to
+   allow people to use the Matrix login for things other than a Matrix-style
+   log in.
+ + MUTIL [ImportEchoMail] now has a new option: default_rescan.  This option
+   allows the SysOp to define the default parameters used when a downlink
+   requests a %RESCAN on all message bases.  In the past this defaulted to
+   "R=250".  MUTIL will continue to default to that value if it is not defined
+   in the .ini file, otherwise it will adopt whatever is defined.  Be sure to
+   define a valid command otherwise RESCAN will not work.  See the default
+   MUTIL.INI for more information.
+ + MUTIL now has a new option under the [General] section: "logcache".  This
+   can be a true or false value.  If true, MUTIL will cache the log file
+   meaning it will write the log file in chunks of "8KB" instead of every
+   line being written.  This is the default and HIGHLY recommended setting for
+   MUTIL. If set to false, MUTIL will physically open the log file and write
+   each individual log line to the file and then close it.  Setting this to
+   false will most likely significantly reduce performance.
+ + Mystic AREA/FILEFIX wasn't properly reporting +1 to Netmail when processing
+   a request.
+ ! Fixed a bug in Areafix RESCAN when using the R= command, caused by changes
+   to my JAM code back when I was optimizing the statistical calculation for
+   the Index reader.
+ + New MPL function DateUnix returns the current date/time in Unix format
+ + New MPL function DateU2D (unixdate): Converts <unixdate> to a DOS date
+ + New MPL function DateD2U (dosdate): Converts <dosdate> to a Unix date
+ + AreaFix responses now list the message base name along with the echotag
+ + AreaFix rescans now show the total messages exported
+ + AreaFix %LIST command now has an option parameter to perform boolean
+   capable searches on the echotag and message base name.  These work just
+   like msg searches with parenthesis (&)AND (|) OR (!) NOT functionality:
+      %LIST BBS            - List areas that contains "BBS"
+      %LIST BBS!Renegade   - List areas that contains "BBS" but not "Renegade"
+ + AreaFix now has a "%ALL" command.  Using "%ALL" or "%+ALL" will add all
+   areas the node has access to.  Using "%-ALL" will remove all nodes the
+   area has access to.  The command has an option second parameter which will
+   perform a boolean capable search on the echotag and message base name:
+      %ALL                 - Add all bases the node has access to (but not
+                             subbed)
+      %-ALL                - Remove all bases the node has subscribed to
+      %ALL BBS!Renegade    - Add all that contain "BBS" but not "Renegade" in
+                             the echotag or base name
+      %-ALL BBS!Renegade   - Remove all bases that contain "BBS" but not
+                             "Renegade" in the echotag or base name
+ + File Bases now have an "List EACS".  This Echomail ACS works identically
+   to the Message Base version, allowing hubs to define which nodes have
+   access to list, subscribe, and receive get files from an echoed file base
+ + FileFix %LIST function now has an optional second parameter to perform
+   boolean searches in the same was as Areafix.
+ + FileFix now has an %ALL function that mimics the functionality of the
+   Areafix equivalent.
+   <ALPHA 1.12 A39 RELEASED -- April 20, 2018>
+</code>
+===== 1.12 Alpha 40 =====
+<code>
+ + Door command lines now have %R which will return the user name without
+   underscores in the name.
+ ! Fixed a bug where groups could be created with a duplicate ID.  You may
+   wish to double check you groups to make sure none of them have the same
+   ID.
+ ! Fixed a bug in Python GotoXY function that would cause a crash when using
+   it.
+ + The MUTIL ImportNA function now allows a "use_ansi" default value to be
+   defined when creating message bases.
+ + The MUTIL Echomail Import function now allows a "use_ansi" default value
+   to be defined when automatically creating message bases.
+ + The MUTIL ImportMessageBase function now allows a "use_ansi" default value
+   to be defined when creating message bases.
+ + MIS FTP now logs when a SysOp deletes a file from a filebase via FTP
+ + MIS FTP/NNTP/SMTP/POP3 servers now have a better idle/timeout system which
+   will cause the server to shutdown more gracefully when exiting MIS with
+   active connections.
+ + New menu command: M! This is a rewrite of the message area index reader
+   rebuilt to work identically to the file base index lister.  See the
+   msg_index.ini file for more details.  Command line option is the template
+   name or default to msg_index.ini if none is specified.  I am not removing
+   the old one just yet so that people have time to adapt to the new version
+   and to test it for issues, but please note the old one will likely be
+   replaced by this new one eventually once the features are all done and
+   tested.
+ + New MPL variable: UserPosts contains the number of posts a user has made
+ + New MPL variable: UserDLs contains the number of downloads user has made
+ + New MPL variable: UserULs contains the number of uploads user has made
+ + Mystic now has a new User Editor which doesn't look a whole lot different
+   than the old one, except that it incorporates some newer ideas that were
+   introduced into the Echomail Node editor that makes jumping around between
+   pages of information easier.  One major thing to note is that you can no
+   longer view user passwords and can now only "reset" user passwords.
+   Like the other page-based editors you can scroll from the first or last
+   item to change page, use the tab key, the pageup/down keys, the left
+   and right arrows, or enter a page number directly to shift between pages.
+ + Mystic now has a password policy in System Configuration where the minimum
+   password length can be set along with number of required capital letters,
+   numbers, and symbols.  It is highly recommended that the minimum password
+   length is set to at least 7 characters.  Some default prompts have been
+   updated to support this new feature: 18, 419, 420. If you have custom
+   themes, you should take a look at the new defaults and consider updating
+   your custom prompts as well.
+ + Mystic now allows the option to store passwords in case insensitive
+   cleartext and case insensitive hashing using industry standard methods for
+   password storage.
+ + Mystic now allows passwords to be stored using PBKDF2 with SHA512-bit
+   hashing at variable configurable iterations.  What does this mean?  The
+   biggest benefit is that when enabled, Mystic will never store a user's
+   password anywhere in the BBS system.  This system is the same system used
+   for Password Managers such as LastPass, 1Password and operating systems
+   such as MacOS.  In fact, with its variable iterations Mystic could be
+   considered to be more secure as those products in terms of cracking a
+   user's password hash.
+   Two new options are added into the Password Policy options, the first is a
+   password storage method which has three options:
+      ClearText Case Insensitive       (This was the legacy storage method)
+      ClearText Case Sensitive
+      PBKDF2 SHA512 Hash               (This is also case sensitive)
+   It is highly recommended to use password hashing and stop using cleartext
+   passwords.  With password hashing enabled, a person could be given your
+   users.dat and they still would not be able get a user's password.
+   The second option is VERY important when using PBKDF2 and that is the
+   number of iterations the process will use when hasing a password.  The
+   default value is 1000 and may be considered a little low in terms of
+   enterprise level password storage but it works at a reasonable speed for most
+   systems.  In general, the higher the number of iterations the more secure it
+   is, but the longer it will take for Mystic to store or check a password.
+   Setting this value to 10,000 on an original Raspberry Pi for example may
+   cause Mystic to take 10+ seconds to store or check a password and for many
+   that may be too slow.
+   It is recommended that it is kept at 3000 or lower for performance reasons
+   unless you know what you are doing.  Even at this level PBKDF2 with a 512
+   bit hashing system is more secure than any other BBS software today.  If
+   you find the delay for 1000 is too short you can adjust the value but just
+   beware that if you change hardware someday, those values still remain...
+   The way the system works is that a user's password is stored in the format
+   configured at the time their password is set, including the iterations. The
+   password remains stored in this format even if you change the storage method
+   until the user changes their password or you reset it using the user editor.
+   It is important that you do not set the iteration level too high for the
+   hardware you are using to run your BBS now or in the future.
+ + Mystic user passwords have now been expanded to 25 characters maximum.
+ + Mystic now allows passwords to be reset via Internet e-mail.  This option
+   can be enabled in System Configuration -> Password Policy and will require
+   that the SMTP sendmail/relay options are configured in the Server General
+   Options tab.  The user must also have a valid e-mail address assigned to
+   their user account.
+   If enabled, the user will be sent an e-mail with a randomly generated code
+   and then prompted by the BBS to enter the code.  Upon entering the code
+   the user will be prompted to change their password and finally logged into
+   the BBS as if they had typed their password in correctly.
+new prompts have been added to the themes to support this new feature
+   most having 4 promptinfo MCI codes active: &1=min length  &2=min caps
+   &3=min nums  &4=min symbols.  These new prompts (538-546) will need to
+   be added to your custom themes if you have them.  See the upgrade.txt
+   for more information.
+ + New Configuration theme: Turbo Vision.  Not really a favorite of mine,
+   but one of the goals of this theme option is for nostalgia preservation
+   and the TurboVision look was widely used in the BBS scene.
+ + Mystic's built in RAR archive functions should now work with newer RAR5
+   format RAR files.  If you encounter any issues viewing a RAR file please
+   e-mail me a link to download the same file or the file itself so I can
+   take a look at it.  Keep in mind Mystic does not allow you to view
+   encrypted archives.
+ + Changed the e(X)it command in the text editor to (Q)uit to match that of
+   the ANSI editor.
+ + New ACS function "OV" returns true if the user has validated their current
+   e-mail address.
+ + Email address fields have been expanded to 60 characters, input field
+   length by default is 40 characters (up from 35).
+ + Mystic will now validate that the user enters a valid e-mail address
+   format when prompting for e-mail address during new user application and
+   when editing user information.  Two new prompts have been added that will
+   be displayed when they enter an invalid e-mail address: #463, #486.  You
+   should update your prompts based on the new defaults.
+ + New menu command: -V (Validate e-mail address).  This function will send
+   a code to the user's e-mail address and then prompt them to enter it on
+   the BBS.  Upon entering the code successfully, the "OV" ACS command will
+   begin to report true.  If the optional data field contains a security level
+   Mystic will also update the user's security profile. The OV ACS can also be
+   used in order to perform any number of actions if validation is successful.
+   New prompts have been added to support this: #547-#552.  You will need to
+   add these if you have custom themes.
+ + Mystic now supports CNET Control-Y color codes.  These work in file
+   description .DIZ importing, in file descriptions, in message reading, in
+   Mystic's file/ANSI viewer and ANSI gallery, and Mystic's ANSI editor can
+   now load CNET color coded files.  Thanks to NuSkooler for initial info
+   about the color codes.
+ + New Python function: "logerror(string)".  This creates an entry into the
+   global error log of the string passed to it, and also creates an entry in
+   the current node log as well.
+ + The group editors now have a Move function that allows repositioning the
+   order of groups.  Simply Copy a group and them move to where you want to
+   place it and select Move.
+ + The file base editor now also has a move function.
+ ! When tagging a bunch of bases in the message base editor and selecting
+   Sort, it was possible to press ESCAPE and wipe out your message base
+   configuration entirely.  Fixed.  Sorry to anyone affected by this.
+ ! Fixed a bug in the global message base editor where setting the Max Msgs
+   value could cause the value to get garbled when updating the bases.
+ + Two new options to the GD menu command (Display a file):
+      /MCI   - If this option is supplied, Mystic will not filter out any MCI
+               codes including pipe colors.
+      /ABORT - If this option is supplied, Mystic will not allow the display
+               file to be aborted.  By default they are allowed.
+ + Mystic's SMTP sendmail function now supports opportunistic SSL via the
+   TLS v1.2+ protocol.  Combined with CRAM-MD5 authenication, this provides
+   encryption of both the password handshake and the overall session.
+ + Message Box MCI codes no longer automatically pad the header text with a
+   space on each side. This makes it consistent with other box functions and
+   allows a bit more flexibility.
+ + MUTIL echo import now gives a more meaningful message when a PKT password
+   is defined and there is no echomail node configured for the origin address
+ + Mystic BINKP server and FIDOPOLL now support opportunistic SSL (TLS v1.2+)
+   using a proprietary extension of the BINKP protocol.  This means that it
+   will only work with other Mystic BBS clients and servers, but I do plan
+   to document the extension and send it to the authors of other mailers in
+   hopes that it can be standardized.
+   BINKP server settings now have a "Use SSL" setting which can be set to
+   one of three settings:
+      No     : BINKP server will not offer SSL extension at all
+      Yes    : BINKP server WILL offer SSL extension optionally
+      Forced : BINKP server will refuse all connections not using SSL
+   EchoMail Nodes now have a similar setting which will be used when polling
+   for new mail:
+      No     : FIDOPOLL will not use SSL extension at all
+      Yes    : FIDOPOLL WILL use SSL if the server supports it
+      Forced : FIDOPOLL will refuse to exchange mail with a server
+               unless it supports SSL
+ + For those of you who downloaded the A40 pre-alpha before Dec 16th, you
+   will have password issues.  To fix this you can copy over the latest
+   upgrade.exe and place your A39 users.dat into DATA and execute "upgrade
+   password".
+ + Message bases with an origin line set to a blank will now inherit the
+   default value set in System Configuration > Message Settings.  This is how
+   it was supposed to work but it wasn't.  The origin line will now also be
+   blank when creating a new message base, instead of setting the value to
+   the current default.  This also includes MUTIL import/create functions.
+ + The random origin line selection engine (@ORIGIN=) will now be processed
+   if it is defined in the default origin line.  In the past it was only
+   processed when defined for an individual message base.
+ ! Mystic will no longer make echomail bundles with a bracket in the filename
+   extension which could happen in a certain circumstance.
+ ! Fixed a bug where Mystic was adding a point to the INTL kludge origin/dest
+   addresses when dealing with point systems.
+ + Message Base editor now has a /A command to select all bases.
+ + File Base editor now has a /A command to select all bases.
+ + File Base editor now has a /G Global Editor similar to the Message Base
+   editor
+ + Echomail nodes now have an "Encryption Key" option.  When this option is
+   set to a non-blank value, Mystic will encrypt all of the contents of
+   Netmail messages to this node with an AES-256 encryption.  This completes
+   a fully encrypted echomail solution as both transport and private messages
+   are secured.
+   This is done in a way that is completely transparent to unsupporting
+   systems, meaning that you can still route netmail through systems and they
+   will not harm the encrypted netmails!  The encryption also hides the
+   message subject, so when combined with Area/Filefix passwords will no
+   longer be readable. You must have Cryptlib installed for this to work.
+   The other echomail node must of course have the same key configured for
+   your node in order to decrypt the netmail when it arrives.  This works the
+   same way as any other password setting in echomail nodes.
+   When routing Netmail, Mystic will intelligently re-encrypt the message
+   between routing points when possible.  In other words if you have a point
+   system who sends from 555:1/2.1 to 555:1/1 but is routed through 555:1/2,
+   Mystic at 555:1/2 will know that it has an encryption agreement between
+   both 555:1/2.1 and 555:1/1 so it will decrypt the message from 555:1/2.1
+   and then reencrypt it for 555:1/1 before routing it.
+ + Mystic Area/Filefix will now accept commands that start and end with a
+   percentage sign (as opposed to just starting with) so: %LIST and %LIST%
+   will work, for example.
+ ! Mystic wasn't properly using UTC time when adding the @VIA kludge while
+   routing Netmail (it was using local system time).
+ ! Reviewed Netmail routing with point systems and corrected a couple little
+   bugs with addressing.  This will hopefully have no negative effect on any
+   other behavior.
+ + Mystic BINKP now sends the local time and time zone information whenever
+   it connects to another BINKP server.
+ + MUTIL MsgPack now no longer users the Mystic temp directories while
+   packing message bases.  Instead, it creates temp files in the same
+   directory as the message base.  This should allow MsgPack to continue to
+   rename files when message bases are stored on different devices than the
+   root Mystic directory.
+ + New MPL function to go along with new password engine:
+     Function CheckPW (PW: String) : Boolean;
+   This function checks the supplied PW against the current loaded User
+   and returns true if the password matches or false if it does not.
+ + New MPL function to go along with new password engine:
+     Procedure SetPW (PW: String);
+   This procedure sets the password for the currently loaded users (ie
+   the User storeed in the current User variables)
+ + New MPL function to go along with new password engine:
+     Procedure ValidPW (PW: String) : Byte;
+   This procedure checks the password passed in PW against the configured
+   password policy and returns a result depending on its status:
+= Password does not meet min length
+= Password does not meet min cap letters
+= Password does not meet min symbols
+= Password does not meet min numbers
+   <ALPHA 1.12 A40 RELEASED -- Dec 25, 2018>
+</code>
+===== 1.12 Alpha 41 =====
+<code>
+ ! Fixed the broken SSH that creeped its way into A40.
+ + Changed the date format in message quoting to "DD MMM YYYY"
+ ! MUTIL echo export should no longer toss messages back to the origin node
+   <ALPHA 1.12 A41 RELEASED -- Dec 27, 2018>
 </code>