config_server_options
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
config_server_options [2018/01/05 16:14] – content updates - 1.12 a38 additions (work in progress) avon | config_server_options [2022/09/25 21:11] (current) – added max poll threads avon | ||
---|---|---|---|
Line 2: | Line 2: | ||
This menu allows you to set some high level configuration settings for your servers. | This menu allows you to set some high level configuration settings for your servers. | ||
- | As of Mystic 1.12 A38 the sendmail features have not yet been enabled for general use. | + | |
+ | ==== Server Options ==== | ||
Line 10: | Line 11: | ||
| | ||
| | ||
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
+ | | ||
+ | | ||
+ | | ||
| | ||
| | ||
- | |||
There following options can be configured. | There following options can be configured. | ||
=== Domain Name === | === Domain Name === | ||
+ | |||
+ | If you have a domain name associated with your BBS place it here. | ||
+ | |||
+ | The FTP server resolves your configured BBS domain upon start up to get both the IPV4 and IPV6 address. It will also perform this procedure every 1 hour so if a dynamic IP changes it will be detected. | ||
=== Max BBS Nodes === | === Max BBS Nodes === | ||
+ | |||
+ | This defines the max number of nodes you will allow at one time. However, there is slightly more to consider. | ||
+ | |||
+ | BBS Nodes can be spawned by any number of built in Mystic servers, or also from external sources for things such as dial-up modems, local logins from the console, etc. The max BBS nodes is a limit to the sum of all possible ways Mystic can accept BBS node connections. | ||
+ | | ||
+ | In the Servers > Configure servers configuration you will see options to modify or create TELNET, RLogin, and SSH servers. | ||
+ | |||
+ | The settings do not have to add up to Max BBS nodes. | ||
+ | |||
+ | This means you can setup a 20 node BBS and then set up 3 different Telnet server and a SSH server all of which each allow 20 connections, | ||
=== Start Hidden === | === Start Hidden === | ||
- | === Enable | + | Hide node windows when a session begins (Windows only) |
+ | |||
+ | === Max Poll Threads === | ||
+ | |||
+ | Sets the number of concurrent outbound connections when running MIS POLL | ||
+ | |||
+ | === Enable | ||
+ | |||
+ | Enable sendmail functionality | ||
+ | |||
+ | === SMTP Host === | ||
+ | |||
+ | Define sendmail/ | ||
+ | |||
+ | === SMTP IP Type === | ||
+ | |||
+ | Define if V4/V6 use only allowed or default to one/ | ||
+ | |||
+ | === SMTP Login === | ||
+ | |||
+ | SMTP sendmail/ | ||
+ | |||
+ | === SMTP Password === | ||
+ | |||
+ | SMTP sendmail/ | ||
+ | |||
+ | === SM Auth Type === | ||
+ | |||
+ | Select Which type of SMTP sendmail/ | ||
+ | |||
+ | * None | ||
+ | * Login | ||
+ | * Plain | ||
+ | * CRAM-MD5 | ||
+ | |||
+ | === SMTP Use SSL/TLS === | ||
+ | |||
+ | Sendmail now supports opportunistic SSL via the TLS v1.2+ protocol. | ||
+ | |||
+ | ==== STMP Send Config Example ==== | ||
+ | |||
+ | In this example we are going to set things up to allow Mystic to send password email reset codes via a Google Gmail account. | ||
+ | |||
+ | == Steps == | ||
+ | |||
+ | * Create a Gmail account for your Mystic BBS to send emails via by visiting [[https:// | ||
+ | |||
+ | * Take a note of the password and Gmail address you use. e.g. testuser@gmail.com / pw = boguspw | ||
+ | |||
+ | * Run Mystic -CFG | ||
+ | |||
+ | * Head to Configuration > User Password Policy. | ||
+ | |||
+ | * Set 'Allow Reset by E-mail' | ||
+ | |||
+ | * Head to Servers > General Options. | ||
+ | |||
+ | * Set the SMTP settings that are displayed in this screen as follows: | ||
+ | |||
+ | * Ensure you **load the Gmail address and password you created** in the first step. | ||
+ | |||
+ | * Don't worry about ' | ||
+ | |||
+ | |||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | |||
+ | |||
+ | * | ||
+ | |||
+ | * Sign in to your Google account - the one you used to create your new Gmail address with. | ||
+ | * Go to the [[https:// | ||
+ | * Select ' | ||
+ | * Scroll down to the section called 'Less secure app access' | ||
- | === SM Host === | + | Now you are ready to test. |
- | === SM Login === | + | * Make sure you have a test account with a valid email address loaded against the user record. |
+ | * Try to login incorrect three times and ask for a reset via email. | ||
+ | * You should see a ' | ||
+ | * You can check your node logs (for the active user) to see details of what has just happened with their SMTP session. | ||
+ | * The email should arrive in to your test users email account approx. 2-3 minutes later containing a reset code to enter. | ||
- | === SM Password === | ||
- | === SM AuthType === | ||
config_server_options.1515190458.txt.gz · Last modified: 2018/01/05 16:14 by avon