User Tools

Site Tools


introduction

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
introduction [2017/10/31 03:34] – removed -PATH switch, option revoked alpha 35 avonintroduction [2023/01/20 03:36] (current) – revisions to allow and denylist syntax avon
Line 11: Line 11:
   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 
 +                 mystic -ansi <filename>. If <filename> is supplied it will
 +                 open that file otherwise it will create an empty buffer.
 +                 
 +                 The ANSI editor can load display files with color codes from 
 +                 PCBoard,Wildcat, Mystic's pipe codes, and ANSI.  The editor 
 +                 can save in ASCII or Pipe Code or ANSI and includes variable 
 +                 line length saving for ANSI files as well as some display 
 +                 options that can be set specifically to Mystic BBS
 +                 
 +  MYSTIC -AUTH   Check password authentication for a user by supplying the
 +                 following syntax: -AUTH <username> <password> If the
 +                 password is correct, Mystic will print TRUE to STDIO and
 +                 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 -CP$    This tells Mystic in Unix environments to start in a
                  particular codepage (UTF8 or CP437).  Ex: -CPUTF8 or -CP437                  particular codepage (UTF8 or CP437).  Ex: -CPUTF8 or -CP437
Line 18: Line 37:
      
   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.  Ex: -IP125.132.54.741                            +                 into Mystic by the telnet server.  Ex: -IP125.132.54.741 
 +                  
 +  MYSTIC -L      This tells Mystic to start in a local login mode.  This 
 +                 option should be supplied whenever you are logging in from 
 +                 your local console.  It is particularly desired in Unix 
 +                 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.  There is usually   MYSTIC -N#     This specifies a specific node number.  There is usually
                  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  This allows a new user to be created from the command line 
 +                   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.  The security level also cannot be above 
 +                    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.  Failures 
 +                    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 "update" command is provided on the command 
 +                    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
                  permitted to use this session.  Ex: -T60 limits the user                  permitted to use this session.  Ex: -T60 limits the user
                  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 
 +                 mystic -text <filename>. If <filename> is supplied it will
 +                 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 
 +                 TELNET/RLOGIN. ./mystic -ttANSI 
 +                                    
   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.  If                  be used along side the -P command to supply the password.  If
Line 67: Line 141:
                  after logging in as Joe User, and then exit the BBS after                  after logging in as Joe User, and then exit the BBS after
                  execution.                  execution.
 +                 
      
 ==== MIS - Mystic Internet Server ==== ==== MIS - Mystic Internet Server ====
Line 73: Line 148:
 protocols.  It can support one or all of the following: protocols.  It can support one or all of the following:
  
-TelnetPOP3SMTP, FTP, NNTP, BINKP, Events+TELNETRLOGINSSH, BINKP, FTP, NNTP, POP3, SMTP, HTTP, Events
  
 Note that the POP3, SMTP servers are used for Mystic BBS internal 'Email' only at this time. The Events system is used by Mystic to call other programs based on time of day or as semaphores are created that trigger events such as importing echomail and/or netmail. Note that the POP3, SMTP servers are used for Mystic BBS internal 'Email' only at this time. The Events system is used by Mystic to call other programs based on time of day or as semaphores are created that trigger events such as importing echomail and/or netmail.
Line 83: 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 for MIS can be found in the //Servers// menu within the Mystic BBS Configuration System by running the following command:+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.  So in Linux you can simply do a:
  
-  MYSTIC -CFG+  sudo ./mis server
  
 +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 ===
  
-You can enable/disable different server types, change their listening ports, and some other options.+Since Mystic 1.12 A47 MIS offers a POLL function/switch. This replaces the previously used FIDOPOLL binary that was retired after Mystic 1.12 A46. The POLL switch enables the server to send and receive echomail and netmail packets to configured EchoMail Nodes. There are three polling options than can be configured for EchoMail nodes - BINKP, FTP, or Directory-based transmission.
  
-Keep in mind that Linux will require a root user by default to bind to server ports less than 1024so if you enable your telnet server and cannot connect, try a port higher than 1024 to make sure it is working.+Optional switches for MIS POLL are: 
 + 
 +  POLL SEND            - Only send/poll if node has new outbound messages 
 +  POLL FORCED [Type]   - Poll/send to all nodes of session [Type] (Blank/All) 
 +  POLL UPLINK [Type]   - Poll all Uplink nodes of session [Type] (Blank/All) 
 +  POLL [Address]       - Poll/send echomail node [Address] (ex: 46:1/100) 
 +  POLL LIST            - List active echomail nodes 
 +  POLL ROUTE [Address] - Show configured netmail routing (Optional address) 
 +  POLL SEARCH [Text]   - Search nodelist for [Text] 
 +  POLL KILLBUSY [Mode] - Delete BSY files [App, Echo, All] (Blank/Echo) 
 + 
 +=== 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 
 + 
 +You can enable/disable different server types, change their listening ports, and some other options.
  
-Setting up a telnet BBS is as simple as loading MIS and telnetting in! :)+Setting up a telnet BBS is as simple as configuring then loading MIS and telnetting in! :)
  
-=== IP BLOCKING ===+=== IP BLOCKING + EXCEPTIONS ===
  
-MIS will check your Mystic DATA directory for file named "badip.txt"It will use this file to check against the IP addresses of incoming connections.  For example, if you wanted to block 123.123.123.123 +MIS will check your Mystic DATA directory for file named denylist.txt It will use this file to check against the IP addresses of incoming connections.  For example, if you wanted to block 123.123.123.123 
-you would simply add a line into the badip.txt file with that IP address.+you would simply add a line into the denylist.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 200:
 If this file does not exist, it will simply print "BLOCKED" to the connection's terminal and disconnect them. If this file does not exist, it will simply print "BLOCKED" to the connection's terminal and disconnect them.
  
-You can also add a "goodip.txtfile the Mystic DATA directory. This file will exempt an IP address from the DNS blacklist, DNS country check, and the auto ban IP systems.  The format of the file is the same as "badip.txt"If you know of certain IP addresses you never want to see auto banned on your system - "goodip.txtis a great way to ensure that never happens!+You can also add a allowlist.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.  The format of the file is the same as denylist.txt If you know of certain IP addresses you never want to see auto banned on your system - allowlist.txt is a great way to ensure that never happens!
  
-There is currently a developmental MIS2 server also available to play with :)  It uses whitelist.txt and blacklist.txt respectively in the Mystic DATA directory. These files work the same way as the MIS counterparts. +Entries in both denylist.txt and allowlist.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.  For example "127.*" would block any IPV4 address that begins with "127." IPV6 works in the same way, expand the IPV6 address up to the point where you want to wildcard it, such as "014f:*"
  
-Entries in these lists can contain a mixture of both IPV4 and IPV6 addresses and can contain a single wildcard, using an asterisk to mask an IP range For example "127.*" would block any IPV4 address that begins with "127." IPV6 works in the same way, expand the IPV6 address up to the point where you want to wildcard it, such as "014f:*"+Refer also to the [[config_edit_ip_blacklist|Edit IP Denylist]] and [[config_edit_ip_whitelist|Edit IP Allowlist]] sections of the Wiki.
  
 === DUPLICATE IP CONNECTIONS === === DUPLICATE IP CONNECTIONS ===
Line 121: Line 216:
  
 === 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 this file does not exist, it will simply 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 this file does not exist, it will simply
Line 136: Line 230:
 ==== FIDOPOLL ==== ==== FIDOPOLL ====
  
-This program sends and receives echomail and netmail packets tor configured EchoMail Nodes. It uses one of three configured options to do so - BINKP, FTP, or Directory-based transmission. +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 was used to send and receive echomail and netmail packets to configured EchoMail Nodes. It used one of three configured options to do so - BINKP, FTP, or Directory-based transmission. 
  
-Optional switches for FIDOPOLL are:+Optional switches for FIDOPOLL were:
  
-  FIDOPOLL LIST          - List configured Echomail nodes +  FIDOPOLL LIST           - List configured Echomail nodes 
-  FIDOPOLL ROUTE         - Show netmail route information +  FIDOPOLL ROUTE          - Show netmail route information 
-  FIDOPOLL SEND          - Only send/poll if node has new outbound messages +  FIDOPOLL SEND           - Only send/poll if node has new outbound messages 
-  FIDOPOLL FORCED [type] - Poll/send to all nodes of session [type] (blank/all) +  FIDOPOLL FORCED [type]  - Poll/send to all nodes of session [type] (blank/all) 
-  FIDOPOLL [Address]     - Poll/send echomail node [Address] (ex: 46:1/100) +  FIDOPOLL [Address]      - Poll/send echomail node [Address] (ex: 46:1/100) 
-  FIDOPOLL SEARCH [data] - Search nodelist for [DATA] can be address or text +  FIDOPOLL SEARCH [data]  - Search nodelist for [DATA] can be address or text 
-  FIDOPOLL KILLBUSY      - Reset busy flags for all echomail nodes+  FIDOPOLL KILLBUSY [ALL] - Reset busy flags for all echomail nodes 
 +                            "ALL" also kills application busy files and should 
 +                            only be used when Mystic+Utilities are NOT running 
 + 
 +If you are still using FIDOPOLL we suggest you update your Mystic version today and start using MIS POLL. It's a far better experience.
  
 EchoMail nodes are configured in the Mystic BBS Configuration System under the 'Configuration' menu. EchoMail nodes are configured in the Mystic BBS Configuration System under the 'Configuration' menu.
Line 167: Line 265:
       QWKPOLL ALL IMPORT /bbs/qwknet - Import QWK packets from /bbs/qwknet       QWKPOLL ALL IMPORT /bbs/qwknet - Import QWK packets from /bbs/qwknet
  
-==== MBBSUTIL -  Mystic BBS Utilities ====+==== NODESPY ====
  
-Mystic BBS Utilities is a depreciating set of utilities that are slowly being absorbed in to MUTIL.+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.  Think of this as your "Waiting for call" screen
  
-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. +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!
  
-At present the following options are available: +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.
- +
-  Usage: MBBSUTIL <Options> +
-   +
-  The following command line options are available: +
-   +
-  -AREASOUT <File>        Export AREAS.BBS format file in <File> +
-  -BKILL    <ID> <Days>   Delete BBSes which haven't been verified in <DAYS> +
-  -BPACK                  Pack all BBS lists +
-  -BSORT    <ID> <Type>   Sorts and packs BBS list by <type> +
-  -FIXINDEX               Fix wrong perm index for user/msg/file bases +
-  -FSORT                  Sort file base entries by filename +
-  -MTRASH   <File>        Delete messages to/from users listed in <File> +
-  -NOCHECK                Bypass online user check at startup +
-  -UKILL    <Days>        Delete users who have not called in <DAYS> +
- +
- +
-==== NODESPY ==== +
- +
-Placeholder text+
  
 ==== MIDE - Mystic Integrated Development Environment ==== ==== MIDE - Mystic Integrated Development Environment ====
Line 198: Line 277:
 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.  This program allows MPS source files to be edited and compiled, while offering some other features that a normal text editor does not. 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.  This program allows MPS source files to be edited and compiled, while offering some other features that a normal text editor does not.
  
-You will find this tool in the /mystic/scripts directory. Run it using the following command.+You will find this tool in the /mystic directory. Run it using the following command.
  
   MIDE   MIDE
Line 204: Line 283:
  
  
-==== MPLC Mystic BBS Programming Language Compiler ====+==== MPLCMystic Programming Language Compiler ====
  
-The Mystic BBS Programming Language Compiler allows sysops to compile their own scripts written in Mystic Programming Language (MPL).  This program translates a MPS source file into a MPX executable file.  A                    MPS source file is a text file which contains programming commands recognized by the MPE engine.  These files can be edited with any text editoror the supplied MIDE program described above.+The Mystic BBS Programming Language Compiler allows sysops to compile their 
 +own scripts written in Mystic Programming Language (MPL).  MPL programs are 
 +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.
  
-Check out the /mystic/scripts directory for examples of MPS files.+You will find this tool in the /mystic directory. 
 + 
 +Check out the /mystic/themes/default/scripts directory for examples of MPS files.
  
 Available options to use this program are: Available options to use this program are:
  
-  MPLC [filename]  Compile a MPL script e.g. MPLC mpldemo.mps+  MPLC [filename] Compile a specific MPL script. Example: MPLC mpldemo.mps 
 +   
 +  MPLC -T         Attempts to read theme configuration from mystic.dat in the 
 +                  current directory or the directory defined by mysticbbs 
 +                  environment variable, and then uses Themes path to compile all 
 +                  scripts in each theme's scripts directory.
          
-  MPLC -ALL        Compile all scripts found+  MPLC -ALL       Compile all scripts in current directory and sub 
 +                  directories
      
- +  MPLC -C         Compile all scripts in current directory only 
 +                    
 +  MPLC -F         Works just like -T but also accepts a filemask to compile any 
 +                  matching files in each theme's script directory.  For 
 +                  example: mplc -f bulletin*          
 +   
 +  MPLC -P [path]  Compile all scripts in [path] 
 +   
 +  MPLC -R [path]  Compile all scripts in [path] in its sub-directories
  
introduction.1509438885.txt.gz · Last modified: 2017/10/31 03:34 by avon

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki