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 [2018/01/03 15:02] – removed mbbsutil references - fully depreciated in 1.12 A37 avon | introduction [2020/09/06 22:05] – g00r00 | ||
---|---|---|---|
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 -CP$ This tells Mystic in Unix environments to start in a | MYSTIC -CP$ This tells Mystic in Unix environments to start in a | ||
Line 18: | Line 33: | ||
| | ||
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 | ||
+ | |||
+ | 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. | ||
+ | |||
+ | 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 | ||
+ | | ||
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 -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 67: | Line 119: | ||
after logging in as Joe User, and then exit the BBS after | after logging in as Joe User, and then exit the BBS after | ||
| | ||
+ | |||
| | ||
==== MIS - Mystic Internet Server ==== | ==== MIS - Mystic Internet Server ==== | ||
Line 73: | Line 126: | ||
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 86: | Line 139: | ||
MYSTIC -CFG | MYSTIC -CFG | ||
- | |||
You can enable/ | You can enable/ | ||
Line 94: | Line 146: | ||
Setting up a telnet BBS is as simple as loading MIS and telnetting in! :) | Setting up a telnet BBS is as simple as loading MIS and telnetting in! :) | ||
- | === IP BLOCKING === | + | === IP BLOCKING |
- | MIS will check your Mystic DATA directory for file named " | + | 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 badip.txt file with that IP address. | + | 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. | 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. | ||
Line 105: | Line 157: | ||
If this file does not exist, it will simply print " | If this file does not exist, it will simply print " | ||
- | You can also add a " | + | 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. |
- | There is currently | + | Entries in both BLACKLIST.TXT and WHITELIST.TXT can contain |
- | Entries in these lists can contain a mixture of both IPV4 and IPV6 addresses and can contain a single wildcard, using an asterisk | + | Refer also to the [[config_edit_ip_blacklist|Edit |
=== DUPLICATE IP CONNECTIONS === | === DUPLICATE IP CONNECTIONS === | ||
Line 121: | Line 173: | ||
=== BUSY NOTIFICATIONS === | === BUSY NOTIFICATIONS === | ||
- | |||
If a connection is made when all of the nodes configured for telnet are being used, MIS will attempt to send them the contents of busy.txt from the Mystic DATA directory. | If a connection is made when all of the nodes configured for telnet are being used, MIS will attempt to send them the contents of busy.txt from the Mystic DATA directory. | ||
Line 140: | Line 191: | ||
Optional switches for FIDOPOLL are: | Optional switches for FIDOPOLL are: | ||
- | 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] - Search nodelist for [DATA] can be address or text | + | FIDOPOLL SEARCH [data] |
- | FIDOPOLL KILLBUSY | + | FIDOPOLL KILLBUSY |
+ | " | ||
+ | only be used when Mystic+Utilities are NOT running | ||
EchoMail nodes are configured in the Mystic BBS Configuration System under the ' | EchoMail nodes are configured in the Mystic BBS Configuration System under the ' | ||
Line 175: | Line 228: | ||
Mystic Integrated Development Environment or MIDE is a development tool that aids budding coders in building scripts using Mystic Programming Language (MPL). It's a text editor which helps you to create MPX programs. | Mystic Integrated Development Environment or MIDE is a development tool that aids budding coders in building scripts using Mystic Programming Language (MPL). It's a text editor which helps you to create MPX programs. | ||
- | You will find this tool in the /mystic/ | + | You will find this tool in the /mystic directory. Run it using the following command. |
MIDE | MIDE | ||
Line 185: | Line 238: | ||
The Mystic BBS Programming Language Compiler allows sysops to compile their own scripts written in Mystic Programming Language (MPL). | The Mystic BBS Programming Language Compiler allows sysops to compile their own scripts written in Mystic Programming Language (MPL). | ||
- | Check out the / | + | 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 MPL script e.g. MPLC mpldemo.mps |
| | ||
- | MPLC -ALL Compile all scripts found | + | MPLC -ALL |
| | ||
+ | MPLC -T | ||
+ | mysticbbs environment variable, and then uses Themes | ||
+ | path to compile. | ||
+ | |||
+ | MPLC -T / | ||
+ | directory, and then uses Themes path to compile | ||
+ | |||
+ | MPLC -F | ||
+ | matching the supplied mask contained in any directories | ||
+ | under the Theme directory. Example: mplc -f bulletin* | ||
introduction.txt · Last modified: 2023/01/20 03:36 by avon