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 revision Previous revision
Next revision
Previous revision
introduction [2017/08/31 05:10]
avon fixed typo - thanks to Darryl for the catch :)
introduction [2021/02/01 14:31]
g00r00
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 -PATH   Opens dialog box where Mystic's base system directories +  MYSTIC -NEWUSER  This allows new user to be created from the command line 
-                 can be configured.  This is useful for when switching +                   using the following key=value pairs: 
-                 operating systems or moving Mystic to a new directory name +                    
-   +                      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 
 +  
   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 -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 71: Line 125:
                  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 77: Line 132:
 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 90: Line 145:
  
   MYSTIC -CFG   MYSTIC -CFG
- 
  
 You can enable/disable different server types, change their listening ports, and some other options. You can enable/disable different server types, change their listening ports, and some other options.
Line 98: Line 152:
 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 + 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 BLACKLIST.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 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 109: Line 163:
 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.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 "badip.txt". If you know of certain IP addresses you never want to see auto banned on your system - "goodip.txt" is a great way to ensure that never happens!+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.  The format of the file is the same as BLACKLIST.TXT. If you know of certain IP addresses you never want to see auto banned on your system - WHITELIST.TXT is a great way to ensure that never happens!
  
-There is currently 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 BLACKLIST.TXT and WHITELIST.TXT can contain 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 Blacklist]] and [[config_edit_ip_whitelist|Edit IP Whitelist]] sections of the Wiki.
  
 === DUPLICATE IP CONNECTIONS === === DUPLICATE IP CONNECTIONS ===
Line 125: Line 179:
  
 === 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 144: Line 197:
 Optional switches for FIDOPOLL are: Optional switches for FIDOPOLL are:
  
-  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
  
 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 170: Line 225:
       QWKPOLL 1 EXPORT /bbs/qwknet   - Create REP packet in /bbs/qwknet       QWKPOLL 1 EXPORT /bbs/qwknet   - Create REP packet in /bbs/qwknet
       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 ==== 
- 
-Mystic BBS Utilities is a depreciating set of utilities that are slowly being absorbed in to MUTIL. 
- 
-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 <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 ==== ==== NODESPY ====
Line 202: Line 234:
 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 212: Line 244:
 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 editor, or 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).  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 editor, or the supplied MIDE program described above.
  
-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 MPL script e.g. MPLC mpldemo.mps
          
-  MPLC -ALL        Compile all scripts found+  MPLC -ALL       Compile all scripts found
      
 +  MPLC -T         Attempts to read mystic.dat from current directory or 
 +                  mysticbbs environment variable, and then uses Themes 
 +                  path to compile. 
 +   
 +  MPLC -T /mybbs  Attempts to read mystic.dat from the supplied root 
 +                  directory, and then uses Themes path to compile 
 +                   
 +  MPLC -F         Attempts to read the Theme path and then compile any files 
 +                  matching the supplied mask contained in any directories 
 +                  under the Theme directory. Example: mplc -f bulletin*         
  
  
introduction.txt · Last modified: 2021/02/01 14:31 by g00r00