whats_new_112
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
whats_new_112 [2021/12/23 11:21] – g00r00 | whats_new_112 [2023/01/18 01:13] – 1.12 A48 released avon | ||
---|---|---|---|
Line 15: | Line 15: | ||
If you spot something you think looks amiss with these notes please contact us using the contact info found on this Wiki. | If you spot something you think looks amiss with these notes please contact us using the contact info found on this Wiki. | ||
+ | \\ | ||
+ | \\ | ||
+ | \\ | ||
+ | \\ | ||
+ | \\ | ||
+ | \\ | ||
\\ | \\ | ||
\\ | \\ | ||
Line 5382: | Line 5388: | ||
| | ||
in the ImportEchoMail stanza. | in the ImportEchoMail stanza. | ||
+ | |||
+ | <ALPHA 1.12 A47 RELEASED -- December 25, 2021> | ||
+ | |||
</ | </ | ||
+ | |||
+ | < | ||
+ | |||
+ | + The MUTIL FileToss TIC import now has an " | ||
+ | systems that use a case sensitive file system. | ||
+ | true and when set to true, Mystic will accept case variations of the | ||
+ | filename. | ||
+ | | ||
+ | For example: If the filename defined inside the TIC file is " | ||
+ | but the file on disk is " | ||
+ | are the same file even though they are not on a case sensitive OS. | ||
+ | | ||
+ | Mystic will also dynamically update the " | ||
+ | to match the filename case of the file on disk when tossing to any | ||
+ | downlinks. | ||
+ | | ||
+ | + Mystic will now execute an " | ||
+ | has logged in. This is ran directly after the user enters their password | ||
+ | and passes through all login checks and stat resets. | ||
+ | | ||
+ | + Mystic will now execute a " | ||
+ | has logged in and went through the entire login process, just before it | ||
+ | sends them to their start menu. | ||
+ | | ||
+ | Here is an outline of the login events: | ||
+ | | ||
+ | BEFORE USER IS LOGGED IN: | ||
+ | | ||
+ | - Connection received, ask for system password if enabled | ||
+ | - Display closed.xxx if password check is failed | ||
+ | - Display Mystic Version | ||
+ | - Execute connect.mpx | ||
+ | - Detect/ask for terminal settings | ||
+ | - Ask for theme selection if ask theme on startup is enabled | ||
+ | - Execute startup.mpx | ||
+ | - If startup newuser then start newuser application | ||
+ | - If startup userlogin then log in user and skip matrix/ | ||
+ | - Execute matrix menu if enabled until user login | ||
+ | - If no matrix menu then display prelogin.xxx | ||
+ | - If no matrix menu then show login prompt until user login | ||
+ | | ||
+ | AFTER USER IS LOGGED IN (includes after new user app): | ||
+ | | ||
+ | - Load/reset stats, user stats, ask for new password if expired | ||
+ | - The following login steps are skipped for QWK network accounts | ||
+ | but are otherwise executed for normal user logins: | ||
+ | - Set or ask for invisible login if configured | ||
+ | - Update whos online data, add call to lastcaller data | ||
+ | - Execute after_login.mpx | ||
+ | - Display login1-9.xxx | ||
+ | - Display sl#.xxx | ||
+ | - Display flag1#.xxx | ||
+ | - Display flag2#.xxx | ||
+ | - Display birthday.xxx | ||
+ | - Check for forced voting questions | ||
+ | - Execute before_menus.mpx | ||
+ | - If QWK network user goto QWK network menu | ||
+ | - If standard user goto user's start menu or default start menu if user | ||
+ | does not have a start menu assigned to them | ||
+ | | ||
+ | + Menus now have a "Reset Activity" | ||
+ | set to Yes, any user activity will reset the TIMER counter for all menu | ||
+ | types. | ||
+ | | ||
+ | + Internally generated Standard menus now have a left and right margin indent | ||
+ | settings for 160+ columns (was only 80 and 132 previously). | ||
+ | | ||
+ | + The "Start Menu" field in the Security Profile editor no longer copies onto | ||
+ | the user's record when upgrading user access. | ||
+ | user the Start Menu field on the user editor no longer auto populates with | ||
+ | the Default start menu from System Configuration. | ||
+ | | ||
+ | Instead, Mystic checks the start menu for the user's security profile on | ||
+ | login. | ||
+ | | ||
+ | IF: User's record has a custom start menu defined, use it as start menu | ||
+ | ELSE: If User's security level profile has a start menu defined, use it | ||
+ | ELSE: Use default start menu from System Configuration> | ||
+ | | ||
+ | Mystic will also now log which start menu is being loaded when a user logs | ||
+ | in. " | ||
+ | | ||
+ | It might be a good idea if upgrading to check your security profiles to make | ||
+ | sure the start menu field is set to a blank or a value that you want for | ||
+ | users with those settings otherwise users could get an error loading menu | ||
+ | error when logging in. | ||
+ | | ||
+ | ! Fixed a few message editor display quirks that found their way into A47 | ||
+ | final release. | ||
+ | | ||
+ | + New Python function for assistance in locating display and configuration | ||
+ | files: | ||
+ | | ||
+ | function find_display (<base filename> | ||
+ | | ||
+ | This function takes a base filename and returns the full path and | ||
+ | filename of a display file that would be displayed after applying | ||
+ | the user's emulation settings, screen size, and random selection | ||
+ | system to it. If no file is found a blank value is returned. | ||
+ | | ||
+ | If no path is included then Mystic will use the current theme' | ||
+ | display path and if nothing is found, it will search through the | ||
+ | theme' | ||
+ | matching file. | ||
+ | | ||
+ | If a path is included in the base name, Mystic will search only | ||
+ | within that path and base filename. | ||
+ | | ||
+ | For example: | ||
+ | filename = find_display(" | ||
+ | | ||
+ | (In this case filename may have a value of these examples): | ||
+ | c: | ||
+ | c: | ||
+ | | ||
+ | Because no path was used it will also search for inherited themes | ||
+ | based on the theme' | ||
+ | in that path: | ||
+ | | ||
+ | filename = find_display(" | ||
+ | Result then might be: " | ||
+ | | ||
+ | + New Python function for assistance in locating configuration files or | ||
+ | other file types using Mystic' | ||
+ | | ||
+ | function find_config (<base filename>, | ||
+ | | ||
+ | This function searches for the base filename and file extension and | ||
+ | returns a valid file (if found) after applying the user's terminal | ||
+ | size and random selection system. | ||
+ | as the find_display function but does not apply the terminal | ||
+ | emulation file extensions and instead uses the extension you supply. | ||
+ | | ||
+ | If no path is included in the base filename then Mystic will use the | ||
+ | theme' | ||
+ | configuration. | ||
+ | | ||
+ | filename = find_config(" | ||
+ | | ||
+ | The result of this might be values such as: | ||
+ | c: | ||
+ | c: | ||
+ | | ||
+ | If you want Mystic to search only in one path and not perform theme | ||
+ | inheritance when it cannot find something, then include a path with | ||
+ | the base filename: | ||
+ | | ||
+ | filename = find_config(" | ||
+ | | ||
+ | ! Mystic when creating a downloadable file list Mystic was leaving the user | ||
+ | in the last file base that was processed instead of keeping them in the base | ||
+ | they were in when the download started. | ||
+ | | ||
+ | + New Python function setlogininfo (username, password, new) | ||
+ | | ||
+ | This function works as part of startup.mps script execution to set the login | ||
+ | details for automated logins via script. | ||
+ | " | ||
+ | | ||
+ | + New Python function isvalidpw (password) : boolean | ||
+ | | ||
+ | This function returns true if the passed password is valid when compared to | ||
+ | the password policy configured in System Configuration. | ||
+ | | ||
+ | + Two new MCI codes to display current time in 24-hour time format: | ||
+ | | ||
+ | TM - Displays current time in HH:MM 24-hour format | ||
+ | TS - Displays current time in HH:MM:SS 24-hour format | ||
+ | | ||
+ | + New Prompt #328 for the standard archive viewer command prompt, when the | ||
+ | user does not have access to download files. | ||
+ | | ||
+ | If you have never modified prompt #328 in your themes then this prompt | ||
+ | will update on its own. If you have customized prompt #328 previously | ||
+ | then you will need to reset it to the default value in the prompt editor | ||
+ | for your themes that have customized it. | ||
+ | | ||
+ | + Mystic' | ||
+ | apply to any unknown connections that do not have a configuration in the | ||
+ | Echomail nodes. | ||
+ | in the node editor. | ||
+ | | ||
+ | This setting determines how Mystic will escape special characters in | ||
+ | filenames and defaults to the Auto setting. | ||
+ | | ||
+ | When set to Auto, Mystic will automatically try to determine the escape | ||
+ | mode by using the VERSION frame sent by the mailer. | ||
+ | is found, Mystic will use FTS standard modern \x## escape mode. | ||
+ | | ||
+ | When set to Legacy, Mystic will use the \## format of file escaping which | ||
+ | is used in some legacy mailers such as Argus, Internet Rex, and older | ||
+ | versions of Mystic. | ||
+ | | ||
+ | When set to Modern, Mystic will use the \x## format which is preferred or | ||
+ | even required by some newer mailers such as BinkD, Radius, and BinkIT. | ||
+ | | ||
+ | It is highly recommended to always keep these set to AUTO unless there is | ||
+ | a very specific reason not to. The escape mode will be logged after | ||
+ | authentication if the loglevel is set to Verbose or higher. | ||
+ | | ||
+ | + New Python function isuserpw (user_password_data, | ||
+ | | ||
+ | This function tests the password against data from a user dictionary and | ||
+ | returns true or false if the password supplied matches the user's password | ||
+ | | ||
+ | For example: | ||
+ | | ||
+ | user = getuser(0); | ||
+ | | ||
+ | if (isuserpw(user[' | ||
+ | writeln(" | ||
+ | else: | ||
+ | writeln(" | ||
+ | | ||
+ | ! When a bad name was found in trashcan.dat, | ||
+ | applicant that the user name is unacceptable while still continuing along | ||
+ | in the new user process. | ||
+ | | ||
+ | + New MCI code " | ||
+ | connections. | ||
+ | | ||
+ | + New MCI code " | ||
+ | the BBS system. | ||
+ | and if a user on another node is invisible to the current user, then | ||
+ | they will be excluded from this number. | ||
+ | | ||
+ | + New option for the " | ||
+ | optional data is supplied, Mystic will not display the whos online list but | ||
+ | instead force recalculation of active users (returned by the NA MCI code). | ||
+ | | ||
+ | Mystic will automatically update the NA MCI code value on its own so for | ||
+ | almost everyone this will never be needed. | ||
+ | | ||
+ | + Fixed a bug where termtype could be chopped off or blank if longer than | ||
+ | 10 characters. | ||
+ | version. | ||
+ | whatsnew: | ||
+ | | ||
+ | MPL and MPY both have a termtype which returns the terminal type as sent | ||
+ | via TELNET and RLOGIN sessions. | ||
+ | left out and apparently wasn't working well anyway. :) | ||
+ | | ||
+ | + Mystic now has a -TT command line option which will override any detected | ||
+ | TerminalType from TELNET/ | ||
+ | | ||
+ | + Mystic' | ||
+ | denylist which better describes what it actually does. If you are | ||
+ | upgrading you should rename blacklist.txt to denylist.txt and | ||
+ | whitelist.txt to allowlist.txt in your DATA folder. | ||
+ | | ||
+ | + TRASHCAN.DAT has been renamed to " | ||
+ | better describes what it actually does. If you are upgrading you should | ||
+ | rename your TRASHCAN.DAT file to badusers.txt in your DATA folder. | ||
+ | | ||
+ | ! MUTIL FileToss was not properly handling the REPLACE keyword when tossing | ||
+ | a TIC replacing a file with a space in the filename. | ||
+ | | ||
+ | ! MUTIL FilePack was not properly setting the OFFLINE flag when check_files | ||
+ | was enabled, remove_missing was disabled, and a file was physically removed | ||
+ | | ||
+ | + When running MUTIL without supplying an INI file on the command line, it | ||
+ | will first search for mutil.ini in the current directory but if not found | ||
+ | it will now also check to see if ' | ||
+ | and then search for the path defined there for mutil.ini. | ||
+ | | ||
+ | + Mystic will now automatically reset the base type to Local and remove other | ||
+ | network settings if you try to change them for the local mailbox base (the | ||
+ | first base) using the Message Base editor. | ||
+ | | ||
+ | ! Fixed a bug in the internally generated menus when using a higher column | ||
+ | size count. | ||
+ | | ||
+ | + MUTIL now has an " | ||
+ | and sends the SysOp a report of dormant message bases. | ||
+ | configured to automatically delete the message base, generate an Areafix | ||
+ | unsubscribe Netmail to your uplink, remove downlinks, and free up all | ||
+ | disk space used by the dormant message echo. | ||
+ | | ||
+ | Because it relies heavily on a complex configuration, | ||
+ | available when you are using Mystic for your echomail tossing solution. | ||
+ | | ||
+ | See the [EchoUnlink] stanza in the default MUTIL.INI that ships with | ||
+ | Mystic for configuration options. | ||
+ | that define what a dormant echo is, what actions should be taken if any, | ||
+ | and what echotags should be excluded (if any). | ||
+ | | ||
+ | ! Fixed a bug where the / | ||
+ | the newer routing logic from A47. | ||
+ | | ||
+ | ! Fixed a bug where the / | ||
+ | newer routing logic from A47. | ||
+ | | ||
+ | + When searching for messages, Mystic will now allow you to search for a | ||
+ | MSGID. | ||
+ | enter the message ID ie " | ||
+ | | ||
+ | + Mystic' | ||
+ | calls into the BBS. Prompt #141 will how use &D to show this number | ||
+ | | ||
+ | ! When autocreating a message echo during echomail import, Mystic would | ||
+ | consider inactive echomail nodes as potential uplinks when calculating | ||
+ | the uplink. | ||
+ | | ||
+ | ! Mystic will no longer allow PKT passwords to come from inactive nodes. | ||
+ | This was originally allowed so that Fix messages could be processed from | ||
+ | inactive nodes. | ||
+ | | ||
+ | + Message Bases now have an " | ||
+ | fields will be changed to " | ||
+ | signatures will not be used in an Anonymous base even if the signature is | ||
+ | enabled. | ||
+ | | ||
+ | + To further expand on the automatic Netmail routing logic, Mystic will now | ||
+ | perform a FidoNet fuzzy zone match when auto routing Netmail. | ||
+ | is between 1 and 6 they will find a match to a hub which is also part of | ||
+ | a zone 1 through 6 if no other (better) routing match could be found. | ||
+ | | ||
+ | To reiterate: For almost everyone, there is never a need touch the Route | ||
+ | field in your Echomail node editor. | ||
+ | Netmail will route you can type "mis poll route < | ||
+ | tell you where Mystic will route a message to that address based on your | ||
+ | current configuration. | ||
+ | | ||
+ | + Mystic' | ||
+ | allows for connections on a stadard BinkP port to automatically " | ||
+ | to a secure TLS connection if both the client and server support it. | ||
+ | | ||
+ | Two new options have been added, one in Server Configuration and one for | ||
+ | EchoMail Node Configuration: | ||
+ | | ||
+ | EchoMail Nodes now have an expanded " | ||
+ | configuration page. Four possible options: | ||
+ | | ||
+ | Normal | ||
+ | Direct SSL : Connect with a direct SSL connection | ||
+ | StartTLS (If Available) : Use TLS when available | ||
+ | StartTLS (Required) | ||
+ | | ||
+ | The StartTLS Required option will refuse to authenticate with any server | ||
+ | that does not offer the opportunistic TLS upgrading. | ||
+ | | ||
+ | BINKP Server Configuration now has a new "Allow StartTLS" | ||
+ | determines how your server will operate. | ||
+ | | ||
+ | No : Never allow opportunistic TLS connections | ||
+ | Yes : Offer to use TLS connection with clients when available | ||
+ | Forced : Require a secure SSL/TLS connection with client always | ||
+ | | ||
+ | The Forced option will cause the BINKP server to refuse any connection that | ||
+ | is not TLS. The client must connect via Direct SSL or on the standard port | ||
+ | and then upgrade to TLS. All non-secure clients will be refused. | ||
+ | | ||
+ | As usual these features will require that CryptLib is present and detected | ||
+ | by Mystic. | ||
+ | | ||
+ | + New door command line MCI codes: %X and %Y return the user's terminal size | ||
+ | (X and Y) and %E returns the user's terminal type (if known) | ||
+ | | ||
+ | ! CHAIN.TXT was always writing column 80 even when the user's terminal size | ||
+ | was larger. | ||
+ | | ||
+ | ! PING responses were not including the PKT password when sending to a node | ||
+ | with PKT passwords enabled. | ||
+ | | ||
+ | ! Fixed a bug in file indexing that was causing duplicate file searching and | ||
+ | mass uploads to behave strangely within Mystic BBS (MUTIL was ok). As a | ||
+ | result everyone should run "mutil -run packfilebases" | ||
+ | indexes properly. | ||
+ | | ||
+ | + Mystic event editor now has a /Move option similar to what is found in the | ||
+ | message and file base editors. | ||
+ | | ||
+ | + Mystic events now have an option to automatically prefix command line calls | ||
+ | in Linux with " | ||
+ | | ||
+ | ! Mystic' | ||
+ | maximum filename length if a file is found to be longer than whatever the | ||
+ | current maximum allowed length is. This was intended but was only working | ||
+ | for traditional uploads and blind uploads. | ||
+ | | ||
+ | + MUTIL' | ||
+ | TRUE. When set to true, Mass Upload will automatically rename filenames | ||
+ | that are longer than the maximum allowed filename. | ||
+ | | ||
+ | + MUTIL' | ||
+ | when importing single line file definitions where the first word is the | ||
+ | filename (this format cannot support spaces) followed by a long line of | ||
+ | text that is the file description. | ||
+ | | ||
+ | + When importing TIC files, Mystic will now wrap the DESC tag when using it | ||
+ | for a file description. | ||
+ | FILE_ID.ANS/ | ||
+ | | ||
+ | + By request: Added a " | ||
+ | user to press escape twice immediately after connecting. | ||
+ | connect.mps and compile in your scripts directory (assuming you are not | ||
+ | already using a connect script) if you wish to use it. | ||
+ | | ||
+ | + The !C menu command to create a semaphore now adds three lines of text to | ||
+ | the semaphore file: | ||
+ | | ||
+ | Line 1: User ID | ||
+ | Line 2: User Handle | ||
+ | Line 3: Node number | ||
+ | | ||
+ | If no user was logged in when this was created the ID will be -1 and the | ||
+ | handle blank. | ||
+ | | ||
+ | ! Fixed a bug in Message Base packer that could cause LR pointer to be set | ||
+ | incorrectly when packing/ | ||
+ | | ||
+ | + BINKP will now show periodic updates during file transfer, updating roughly | ||
+ | every 10 seconds during the transfer. | ||
+ | line when a file is confirmed to be sent or received instead of only at the | ||
+ | start. | ||
+ | | ||
+ | + BINKP now has the ability to limit the bandwidth used when sending or | ||
+ | receiving files. | ||
+ | and causes them to operate at full speed. | ||
+ | maximum rate in Kilobytes (KB) to use for the connection. | ||
+ | | ||
+ | Two new options have been added to the BINKP Server configuration as well | ||
+ | as in Server > General Settings for MIS POLL and in EchoMail nodes for | ||
+ | specific nodes to override those other settings: | ||
+ | | ||
+ | BINKP Server setting: (Server > Servers > BINKP) | ||
+ | | ||
+ | Download speed limit (for your server when you receive files) | ||
+ | Upload speed limit (for your server, when you send files) | ||
+ | | ||
+ | MIS POLL setting (Server > General Options): | ||
+ | | ||
+ | Download speed limit (for your client, when you receive files) | ||
+ | Upload speed limit (for your client, when you send files) | ||
+ | | ||
+ | EchoMail Node setting (Overrides MIS POLL/BINKP settings if enabled): | ||
+ | | ||
+ | Download speed limit: (Used when you receive files from this node) | ||
+ | Upload speed limit: (Used when you send files to this node) | ||
+ | | ||
+ | + BINKP clients will now respond to a LIMIT frame sent from the remote | ||
+ | connection which allows the receiving server to tell the sender the rate | ||
+ | that it would like files to be sent. Mystic will not accept a LIMIT frame | ||
+ | less than 2KB (1024 x 2 bytes) and will set anything lower than that to | ||
+ | 2KB. | ||
+ | | ||
+ | This is helpful when using bandwidth limits because it is possible for the | ||
+ | sending system to send all of the data for a file at full speed into the | ||
+ | Internet void and then timeout while waiting for a response. (This happens | ||
+ | if the server is using a limited bandwidth and hasn't actually received the | ||
+ | file within the sender' | ||
+ | | ||
+ | + EchoNode editor now has a Global editor for editing some values across many | ||
+ | tagged Echomail nodes, including the new node-specific bandwidth limiters. | ||
+ | | ||
+ | + BINKP received/ | ||
+ | to the hundredth of a second in its log messages. | ||
+ | | ||
+ | + The AREAS.BBS export in MUTIL now has a " | ||
+ | to false will cause MUTIL to export all bases in AREAS.BBS not just the | ||
+ | Networked bases. | ||
+ | | ||
+ | + The default value for the " | ||
+ | configurable on a per-theme basis. | ||
+ | used as the default for the To field. | ||
+ | you don't have to do anything but you may need to reset it to default in | ||
+ | the prompt editor otherwise. | ||
+ | | ||
+ | + MUTIL ImportEchoMail now has a " | ||
+ | create JAM filenames in the DOS 8.3 file format. | ||
+ | | ||
+ | 0 = Do not use 8.3 filename (uses echotag for filename) | ||
+ | 1 = Use shortened 8.3 filename (trimmed based on the echotag name) | ||
+ | 2 = Use random hex 8.3 filename | ||
+ | | ||
+ | + MUTIL GoldEd export now has an option to set the group value which can be | ||
+ | up to 6 characters/ | ||
+ | when exporting data. | ||
+ | | ||
+ | + MUTIL GoldEd export now has the option to define a zone and if set to a non | ||
+ | zero value will only export bases where the base's network address matches | ||
+ | the configured zone (use if you only want to export FidoNet for example). | ||
+ | | ||
+ | + MUTIL TopList will now allow @RN to be used in the template to show the | ||
+ | user's real name instead of @NA which uses the user handle. | ||
+ | | ||
+ | + The Message Base editor now has a /B option to Select By Network. | ||
+ | | ||
+ | + The File Base editor now has a /B option to Select By Network. | ||
+ | | ||
+ | ! Mystic default install was accidentally installing a startup.mps and | ||
+ | startup.mpx file. If you are not already using a custom startup script | ||
+ | then you should make sure to delete them from your theme' | ||
+ | directory as they are not intended to be included or installed. | ||
+ | | ||
+ | + FTP server now has an option to test uploads in server options. | ||
+ | to replace with the path and filename of the upload for tests. | ||
+ | tests will end up in the file listings flagged as " | ||
+ | | ||
+ | + The FTP server will now send robots.txt from the DATA folder if any FTP | ||
+ | client requests it at the root directory. | ||
+ | include a robots.txt that denies all crawling. | ||
+ | | ||
+ | ! FTP server was failing when changing directories to any FTP directory name | ||
+ | that had a period in the name. | ||
+ | | ||
+ | + New MCI code: DN returns the configured BBS domain name | ||
+ | | ||
+ | + New .INI file can be placed in a Theme' | ||
+ | folder to allow customization of the validate e-mail address e-mail | ||
+ | contents. | ||
+ | | ||
+ | The default installation now comes with a emailval.ini file in the DATA | ||
+ | folder which can be used to learn more. | ||
+ | | ||
+ | + New .INI file can be placed in a Theme' | ||
+ | folder to allow customization of the password reset e-mail contents. | ||
+ | | ||
+ | The default installation now comes with a resetpw.ini file in the DATA | ||
+ | folder which can be used to learn more. | ||
+ | | ||
+ | + The Coord1 in the message editor template (msg_editor.ini by default) now | ||
+ | defines the text attrbute used when doing things such as line clears. | ||
+ | option inheritantly allows for editors with non-black backgrounds to | ||
+ | function as expected. | ||
+ | | ||
+ | ! Creating a user in the user editor was not properly setting their tagline | ||
+ | default setting. | ||
+ | | ||
+ | ! Mystic will no longer show "user is marked unavailable" | ||
+ | a system broadcast to a node with message availability disabled. | ||
+ | | ||
+ | ! When paging another user for user to user chat, Mystic will no longer show | ||
+ | that the node is unavilable if enter is pressed on the node number prompt. | ||
+ | | ||
+ | ! Mystic will no longer display "This base is marked mandatory" | ||
+ | all bases on or off in the scan settings for message/ | ||
+ | | ||
+ | ! MIS was not properly returning the " | ||
+ | ACS strings. | ||
+ | | ||
+ | ! The badusers.txt check was case sensitive when it should have been | ||
+ | insensitive | ||
+ | | ||
+ | + FTP server now logs if an upload test passes or fails and the result code | ||
+ | when it does fail. | ||
+ | | ||
+ | ! Mystic user to user split and line chats were not exiting properly if the | ||
+ | remote user dropped connection. | ||
+ | | ||
+ | ! Netmail PING responses were not properly setting the message date field | ||
+ | | ||
+ | ! Fixed a bug where MUTIL could add a 0:0/0 address in the VIA kludge when | ||
+ | routing Netmail between FidoNet zones. | ||
+ | | ||
+ | ! MIS FTP server was allowing logins when the user was flagged locked out | ||
+ | | ||
+ | ! MIS SMTP server will now refuse to allow e-mail sent from any user who | ||
+ | is locked out. | ||
+ | | ||
+ | ! MIS NNTP server will now refuse to allow logins from locked out users | ||
+ | | ||
+ | ! MIS POP3 server will now refuse to allow logins from locked out users | ||
+ | | ||
+ | ! Fixed a number of bugs when toggling QWK network scan settings for a QWK | ||
+ | network user. | ||
+ | | ||
+ | ! Fixed a number of bugs when toggling new scan settings with compression | ||
+ | turned off. | ||
+ | | ||
+ | + Mystic now tracks the number of doors opened by a user when using a DOOR | ||
+ | menu command. | ||
+ | command line in optional data to tell Mystic not to increment the users | ||
+ | door count. | ||
+ | | ||
+ | + New ACS commands: | ||
+ | | ||
+ | O1 : True if user posted during this call | ||
+ | O2 : True if user sent local e-mail during this call | ||
+ | O3 : True if user uploaded during this call | ||
+ | O4 : True if user downloaded during this call | ||
+ | O5 : True if user opened a door during this call | ||
+ | | ||
+ | + Mystic now updates callers.dat (Last caller information) when exiting the | ||
+ | BBS to include some additional statistics: | ||
+ | | ||
+ | Time spent online (Stored in seconds. 0=Still online) | ||
+ | Number of posts made during call | ||
+ | Number of emails sent during call | ||
+ | Number of files uploaded | ||
+ | Number of file data uploaded in kilobytes | ||
+ | Number of files downloaded | ||
+ | Number of files downloaded in kilobytes | ||
+ | Number of doors opened | ||
+ | Current state at logoff of all access flags (set 1) | ||
+ | Current state at logoff of all access flags (set 2) | ||
+ | | ||
+ | The 10 optional user data fields are also saved when the user logs out. | ||
+ | Along with flags, these can be used to track custom data throughout a | ||
+ | session. | ||
+ | | ||
+ | + Menu editor will now pop up a notification if you reach the max number of | ||
+ | action items per menu command and try to paste or insert a new command. | ||
+ | | ||
+ | + User access flags and Echomail node security flags now have a new editor | ||
+ | which allows for more ways to toggle flags and also allows for a | ||
+ | description to be assigned to each flag. | ||
+ | | ||
+ | ! The NA imports in MUTIL were accidentally dupe checking against the | ||
+ | filename not the EchoTag, causing the import to not catch duplicates in | ||
+ | some situations (where filename was not equal to the echo tag). | ||
+ | | ||
+ | + New MCI code FLxx retuns the ON/OFF prompt depending on the user flag | ||
+ | state. | ||
+ | return on/off state of the user's A flag in flag set 1. | ||
+ | | ||
+ | + New MCI code FDxx returns the flag description where xx defines the set | ||
+ | and the flag. For example FD1A would return the description for flag | ||
+ | set 1, flag A. | ||
+ | | ||
+ | + New MCI code HXxx sends a hex byte. For example ASCII 254 is FE in | ||
+ | hex so HXFE would send out ASCII 254. | ||
+ | | ||
+ | + Built a new Python loader which will do better at trying to find your | ||
+ | Python information when the Python2 and Python3 library paths are not | ||
+ | set in System Configuration > General Settings. | ||
+ | should now be more likely to work. | ||
+ | | ||
+ | ! Fixed a bug in user to user split screen chat where backspace was not | ||
+ | updating in the terminal. | ||
+ | | ||
+ | ! Fixed a bug in user to user split screen chat where the screen could get | ||
+ | corrupted and go crazy if the user was doing something that used the newer | ||
+ | template format (such as posting a message in the editor, ANSI viewer, etc) | ||
+ | | ||
+ | + Optimized MUTIL' | ||
+ | | ||
+ | + The "MIS POLL SEARCH" | ||
+ | accidentally missing. | ||
+ | | ||
+ | + I noticed that pipedoor.ini is not mentioned in the whats new. I don't | ||
+ | remember when it was added, but Mystic creates an ini-like door drop file | ||
+ | called pipedoor.ini. | ||
+ | on with additional fields since it uses a key=value pair on each line. | ||
+ | | ||
+ | There is a doorkit I was working on with the same name that may be released | ||
+ | at some point. | ||
+ | | ||
+ | + New MCI code: LF loads the last font. Reminder: Font MCI codes only | ||
+ | work when a theme' | ||
+ | | ||
+ | + New MCI code LC loads the last color mode (ICE/ | ||
+ | system MCI codes only work when a theme' | ||
+ | | ||
+ | + Mystic now reads column information from SAUCE when importing FILE_ID.ANS | ||
+ | files and uses them to render if found. | ||
+ | file descriptions found in some art packs that were saved in an odd column | ||
+ | size like 44 characters. | ||
+ | | ||
+ | If you see an ANSI description that isn't showing properly, edit it while | ||
+ | listing files and press I to reimport the DIZ to possibly fix it. | ||
+ | | ||
+ | + Mystic will now switch fonts and color modes if a theme has font and/or | ||
+ | color modes set and an ANSI .DIZ file description has SAUCE with font | ||
+ | or color information. | ||
+ | | ||
+ | This means listing files in an Amiga font with blinking text, Mystic will | ||
+ | switch to CP437 and ICE colors just for the ANSI description and then | ||
+ | revert back to the previous font/color mode. The result is ANSI | ||
+ | descriptions showing properly in Amiga themes and Amiga descriptions showing | ||
+ | properly in ANSI themes. | ||
+ | | ||
+ | Here is a screen capture to demonstrate: | ||
+ | | ||
+ | In the screenshot, the theme is Amiga font yet Mystic enables ICE and | ||
+ | CP437 just to display the description because the FILE_ID.ANS has SAUCE | ||
+ | information that explains it should be CP437 with ICE colors. | ||
+ | prompt and filename in Amiga font while description is ANSI | ||
+ | | ||
+ | Note: Existing ANSI file descriptions need to be reimported before they | ||
+ | will work. Files that were imported to the BBS before Mystic was SAUCE | ||
+ | aware will not have these new features and fixes. | ||
+ | | ||
+ | ! Fixed a bug that was causing IPV6+IPV4 (Default IPV6) to not properly | ||
+ | fallback to IPV4 if the IPV6 connection failed. | ||
+ | | ||
+ | + New MCI code |SI returns the " | ||
+ | through (as defined in the Server Configuration) or blank if the connection | ||
+ | did not source through MIS. | ||
+ | | ||
+ | + New command line -SID< | ||
+ | which will become the value of the |SI MCI code (for use with a 3rd party | ||
+ | server). | ||
+ | | ||
+ | <ALPHA 1.12 A48 RELEASED -- January 15, 2023> | ||
+ | | ||
+ | </ |
whats_new_112.txt · Last modified: 2023/01/18 01:15 by avon