introduction
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
introduction [2016/05/15 05:18] – mide info added avon | introduction [2023/01/20 03:30] – updated mis poll switches avon | ||
---|---|---|---|
Line 10: | Line 10: | ||
MYSTIC -CFG This tells Mystic to start in local configuration mode. | MYSTIC -CFG This tells Mystic to start in local configuration mode. | ||
+ | | ||
+ | MYSTIC -ANSI This invokes the built in ANSI editor using the syntax | ||
+ | | ||
+ | open that file otherwise it will create an empty buffer. | ||
+ | |||
+ | The ANSI editor can load display files with color codes from | ||
+ | | ||
+ | can save in ASCII or Pipe Code or ANSI and includes variable | ||
+ | line length saving for ANSI files as well as some display | ||
+ | | ||
+ | |||
+ | MYSTIC -AUTH Check password authentication for a user by supplying the | ||
+ | | ||
+ | | ||
+ | exit immediately (or FALSE if incorrect). | ||
+ | | ||
+ | MYSTIC -C$ This specifies the user's Country name which will be assigned | ||
+ | to the UO MCI code and ultimately saved to the user's record | ||
+ | as their last known country. | ||
+ | |||
+ | MYSTIC -CP$ This tells Mystic in Unix environments to start in a | ||
+ | | ||
| | ||
MYSTIC -HOST$ | MYSTIC -HOST$ | ||
Line 16: | Line 38: | ||
MYSTIC -IP$ This specifies the user's IP address which should be passed | MYSTIC -IP$ This specifies the user's IP address which should be passed | ||
into Mystic by the telnet server. | into Mystic by the telnet server. | ||
+ | |||
+ | MYSTIC -L This tells Mystic to start in a local login mode. This | ||
+ | | ||
+ | your local console. | ||
+ | where Mystic is not able to tell the difference between | ||
+ | a local console login and a remote user. | ||
MYSTIC -N# This specifies a specific node number. | MYSTIC -N# This specifies a specific node number. | ||
no reason to use this, as Mystic will automatically select | no reason to use this, as Mystic will automatically select | ||
- | an available node. Ex: -N1 tells Mystic to start node 1. | + | an available node. In fact it is not recommended to use this |
- | | + | at all. Ex: -N1 tells Mystic to start node 1. |
+ | |||
+ | MYSTIC -NEWUSER | ||
+ | using the following key=value pairs: | ||
+ | |||
+ | handle=usernamehere | ||
+ | name=realnamehere | ||
+ | pass=passwordhere | ||
+ | email=emailhere | ||
+ | level=seclevelhere | ||
+ | menu=start | ||
+ | |||
+ | At a minimum Mystic requires the handle, realname, and | ||
+ | password fields to be set. Mystic does NOT apply the | ||
+ | password policy to the supplied password in these | ||
+ | situations. | ||
+ | 249 and any attempt to set a security of 250 or higher | ||
+ | will result in the user being created with a security | ||
+ | level of 0. The menu option sets the user's start | ||
+ | menu that will be loaded when they log in. | ||
+ | |||
+ | Mystic will print TRUE or FALSE to STDIO depending on | ||
+ | whether or not the user was properly created. | ||
+ | occur when minimum values are not supplied or when a | ||
+ | user already exists. | ||
+ | |||
+ | Example: | ||
+ | |||
+ | mystic -newuser handle=g00r00 name=g00r00 pass=password | ||
+ | |||
+ | If the optional " | ||
+ | line then Mystic will create the user if they do not exist | ||
+ | but update them if they do exist, provided that the user | ||
+ | to be updated is not currently logged into the BBS or being | ||
+ | edited in the user editor. | ||
+ | |||
+ | Example: | ||
+ | |||
+ | mystic -newuser update handle=g00r00 email=new@gmail.com | ||
+ | |||
+ | The above example would update user g00r00 with the email | ||
+ | address supplied. | ||
+ | | ||
MYSTIC -T# This specifies the number of minutes the user will be | MYSTIC -T# This specifies the number of minutes the user will be | ||
| | ||
to only an hour even if they have many hours of time left | to only an hour even if they have many hours of time left | ||
+ | | ||
+ | MYSTIC -TEXT This invokes the built in text editor using the syntax | ||
+ | | ||
+ | open that file otherwise it will create an empty buffer. | ||
| | ||
MYSTIC -TID# This specifies the socket handle when using Mystic with a | MYSTIC -TID# This specifies the socket handle when using Mystic with a | ||
third party telnet server under Windows | third party telnet server under Windows | ||
- | | + | |
+ | MYSTIC -TT This option which will override any detected TerminalType from | ||
+ | | ||
+ | | ||
MYSTIC -U$ This specifies the username to login to Mystic with and must | MYSTIC -U$ This specifies the username to login to Mystic with and must | ||
be used along side the -P command to supply the password. | be used along side the -P command to supply the password. | ||
Line 37: | Line 114: | ||
The above example will automatically attempt to login as the | The above example will automatically attempt to login as the | ||
Joe User. | Joe User. | ||
+ | |||
+ | MYSTIC -VER Prints the Mystic version number and exits | ||
| | ||
MYSTIC -X$ This specifies a MPL program to execute and then exit Mystic | MYSTIC -X$ This specifies a MPL program to execute and then exit Mystic | ||
Line 47: | Line 126: | ||
after logging in as Joe User, and then exit the BBS after | after logging in as Joe User, and then exit the BBS after | ||
| | ||
+ | |||
+ | If command arguments need to be passed to the executed script | ||
+ | then they must be enclosed with quotations such as: | ||
+ | |||
+ | mystic -uJoe_User -pMYPASSWORD " | ||
+ | |||
+ | MYSTIC -Y$ This specifies a PYTHON program to execute and then exit Mystic | ||
+ | | ||
+ | in order to tell Mystic which user to run the PYTHON program as | ||
+ | | ||
+ | | ||
+ | |||
+ | The above will execute testpython.mpy from the scripts directory | ||
+ | after logging in as Joe User, and then exit the BBS after | ||
+ | | ||
+ | |||
| | ||
==== MIS - Mystic Internet Server ==== | ==== MIS - Mystic Internet Server ==== | ||
Line 53: | Line 148: | ||
protocols. | protocols. | ||
- | Telnet, POP3, SMTP, FTP, NNTP, BINKP, Events | + | TELNET, RLOGIN, SSH, BINKP, FTP, NNTP, POP3, SMTP, HTTP, Events |
Note that the POP3, SMTP servers are used for Mystic BBS internal ' | Note that the POP3, SMTP servers are used for Mystic BBS internal ' | ||
Line 63: | Line 158: | ||
variable if it exists to find the directory where MYSTIC.DAT resides. | variable if it exists to find the directory where MYSTIC.DAT resides. | ||
- | The options | + | When running in Linux/macOS keep in mind that by default the operating system will not let a service bind to a port less than 1025 unless it is a ROOT user (in Linux) and NOT AT ALL in MacOS. In Linux, MIS has the ability to switch from root back to whatever the user and group is that owns the executable AFTER it binds to the ports it needs for the server. |
+ | |||
+ | sudo ./mis | ||
+ | |||
+ | Note: This will **not** run MIS as root. It will only use root to immediately bind the ports and then it will switch to the user who owns the executable. | ||
+ | |||
+ | === MIS POLL === | ||
+ | |||
+ | Since Mystic 1.12 A47 MIS offers a POLL function/ | ||
+ | |||
+ | Optional switches for MIS POLL are: | ||
+ | |||
+ | POLL SEND - Only send/poll if node has new outbound messages | ||
+ | POLL FORCED [Type] | ||
+ | POLL UPLINK [Type] | ||
+ | POLL [Address] | ||
+ | POLL LIST - List active echomail nodes | ||
+ | POLL ROUTE [Address] - Show configured netmail routing (Optional address) | ||
+ | POLL SEARCH [Text] | ||
+ | POLL KILLBUSY [Mode] - Delete BSY files [App, Echo, All] (Blank/ | ||
+ | |||
+ | === MIS CONFIGURATION === | ||
+ | |||
+ | The options for configuring MIS are found in the //Servers// menu within the Mystic BBS Configuration System by running the following command: | ||
MYSTIC -CFG | MYSTIC -CFG | ||
+ | You can enable/ | ||
+ | |||
+ | Setting up a telnet BBS is as simple as configuring then loading MIS and telnetting in! :) | ||
+ | |||
+ | === IP BLOCKING + EXCEPTIONS === | ||
+ | |||
+ | MIS will check your Mystic DATA directory for file named BLACKLIST.TXT It will use this file to check against the IP addresses of incoming connections. | ||
+ | you would simply add a line into the BLACKLIST.TXT file with that IP address. | ||
+ | |||
+ | IP blocking supports wildcards too, so for example, you could put 123.123.123.* and block any IP address that begins with 123.123.123. | ||
+ | |||
+ | If an IP address is blocked, Mystic will attempt to send them the contents of the file " | ||
+ | |||
+ | If this file does not exist, it will simply print " | ||
+ | |||
+ | You can also add a WHITELIST.TXT file the Mystic DATA directory. This file will exempt an IP address from the DNS blacklist, DNS country check, and the auto ban IP systems. | ||
+ | |||
+ | Entries in both BLACKLIST.TXT and WHITELIST.TXT can contain a mixture of both IPV4 and IPV6 addresses and can contain a single wildcard, using an asterisk to mask an IP range. | ||
+ | |||
+ | Refer also to the [[config_edit_ip_blacklist|Edit IP Blacklist]] and [[config_edit_ip_whitelist|Edit IP Whitelist]] sections of the Wiki. | ||
+ | |||
+ | === DUPLICATE IP CONNECTIONS === | ||
+ | |||
+ | MIS will block an IP from opening multiple connections to the BBS. If a person is already connected to Mystic and they attempt to open a second connection, MIS will attempt to send them the contents of the file | ||
+ | " | ||
+ | |||
+ | If the file does not exist, it will simply send them "Only 1 connection(s) per user" and disconnect only their second connection. | ||
- | You can enable/ | + | Their first connection will remain untouched. |
- | listening ports, and some other options. | + | |
- | Keep in mind that Linux will require a root user by default to bind to | + | === BUSY NOTIFICATIONS === |
- | server ports less than 1024, so if you enable your telnet server and | + | |
- | cannot connect, try a port higher than 1024 to make sure it is working. | + | |
- | Setting up a telnet BBS is as simple as loading | + | If a connection |
+ | print " | ||
==== MUTIL - Mystic Utilities ==== | ==== MUTIL - Mystic Utilities ==== | ||
Line 87: | Line 230: | ||
==== FIDOPOLL ==== | ==== FIDOPOLL ==== | ||
- | This program | + | This executable has been retired as of Mystic 1.12 A47 and replaced my 'MIS POLL' but if you have an older copy of Mystic here are the details. FIDOPOLL was a program |
- | Optional switches for FIDOPOLL | + | Optional switches for FIDOPOLL |
- | FIDOPOLL LIST - List configured Echomail nodes | + | FIDOPOLL LIST |
- | FIDOPOLL ROUTE | + | FIDOPOLL ROUTE - Show netmail route information |
- | FIDOPOLL SEND - Only send/poll if node has new outbound messages | + | FIDOPOLL SEND |
- | FIDOPOLL FORCED [type] - Poll/send to all nodes of session [type] (blank/ | + | FIDOPOLL FORCED [type] |
- | FIDOPOLL [Address] | + | FIDOPOLL [Address] |
+ | FIDOPOLL SEARCH [data] | ||
+ | FIDOPOLL KILLBUSY [ALL] - Reset busy flags for all echomail nodes | ||
+ | " | ||
+ | only be used when Mystic+Utilities are NOT running | ||
- | EchoMail nodes are configured in the | + | If you are still using FIDOPOLL we suggest you update your Mystic version and start using MIS POLL. It's a far better experience. |
+ | |||
+ | EchoMail nodes are configured in the Mystic BBS Configuration System under the ' | ||
==== QWKPOLL ==== | ==== QWKPOLL ==== | ||
- | Placeholder text | + | QWKPOLL automatically deals with QWK and REP packets during polling. |
- | ==== MBBSUITL - Mystic BBS Utilities ==== | + | The export and import functions are not needed, and only provided for systems that may want to use an alternative transport method. |
- | Mystic BBS Utilities is a depreciating set of utilities that are slowly being absorbed in to MUTIL. | + | Syntax: QWKPOLL [ALL] |
- | + | [Qwk Network Index] | |
- | In recent times the command line options for this program have started to be removed and now appear as stanzas in .ini configuration file(s) used by MUTIL. | + | |
- | + | ||
- | At present the following options are available: | + | |
- | + | ||
- | Usage: MBBSUTIL < | + | |
| | ||
- | The following command line options are available: | + | [EXPORT] [Index/ALL] [PATH TO CREATE REP] |
+ | [IMPORT] [Index/ALL] [PATH OF QWK PACKET] | ||
| | ||
- | -AREASOUT < | + | |
- | -BKILL <ID> < | + | |
- | | + | |
- | -BSORT | + | |
- | | + | |
- | -FSORT Sort file base entries by filename | + | |
- | -MTRASH | + | |
- | -NOCHECK | + | |
- | -UKILL | + | |
==== NODESPY ==== | ==== NODESPY ==== | ||
- | Placeholder text | + | NodeSpy is a program that will allow you to snoop, kick, and chat with users who are connected to your BBS. It will also provide you with BBS usage statistics and graphs. |
+ | |||
+ | In addition, NodeSpy also has a terminal mode that offers a full blown ANSI BBS telnet client with dialing directory, scrollback, and Zmodem with ZEDZAP file transfers! | ||
+ | |||
+ | It is important to note that NodeSpy does not currently monitor BBS users while they are using doors nor does it offer a chat option to engage with bbs users. | ||
==== MIDE - Mystic Integrated Development Environment ==== | ==== MIDE - Mystic Integrated Development Environment ==== | ||
- | Mystic Integrated Development Environment or MIDE is a development tool that aids budding coders in building scripts using Mystic Programming Language (MPL). | + | Mystic Integrated Development Environment or MIDE is a development tool that aids budding coders in building scripts using Mystic Programming Language (MPL). |
- | ==== MPLC - Mystic BBS Programming Language Compiler ==== | + | You will find this tool in the /mystic directory. Run it using the following command. |
- | The Mystic BBS Programming Language Compiler allows sysops to compile their own scripts written in Mystic Programming Language (MPL). | + | MIDE |
+ | | ||
- | Scripts are written | + | |
+ | ==== MPLC: Mystic Programming Language Compiler ==== | ||
+ | |||
+ | The Mystic BBS Programming Language Compiler allows sysops to compile their | ||
+ | own scripts | ||
+ | created using source file (.mps) and then compiled into executable files | ||
+ | (.mpx). The source files are just typical text files that can be edited with | ||
+ | any text editor or the MIDE utility that ships with Mystic. | ||
+ | |||
+ | You will find this tool in the /mystic directory. | ||
+ | |||
+ | Check out the /mystic/ | ||
Available options to use this program are: | Available options to use this program are: | ||
- | MPLC [filename] | + | MPLC [filename] Compile a specific |
+ | |||
+ | MPLC -T | ||
+ | current directory or the directory defined by mysticbbs | ||
+ | environment variable, and then uses Themes path to compile all | ||
+ | scripts in each theme' | ||
| | ||
- | MPLC -ALL Compile all scripts | + | MPLC -ALL |
+ | directories | ||
| | ||
- | + | MPLC -C | |
+ | |||
+ | MPLC -F Works just like -T but also accepts a filemask to compile any | ||
+ | matching files in each theme' | ||
+ | example: mplc -f bulletin* | ||
+ | |||
+ | MPLC -P [path] | ||
+ | |||
+ | MPLC -R [path] | ||
introduction.txt · Last modified: 2023/01/20 03:36 by avon