Differences

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

--- config_server_options [2018/12/31 23:02] – adding requested example avon
+++ config_server_options [2018/12/31 23:06] – adding requested example avon
@@ Line 84: / Line 84: @@
 == Steps  ==
-  * Create a Gmail account for your Mystic BBS to send emails via by visiting [[https://www.google.com/gmail/|Gmail]]
+  * Create a Gmail account for your Mystic BBS to send emails via by visiting [[https://www.google.com/gmail/|Gmail]].
   * Take a note of the password and Gmail address you use. e.g. testuser@gmail.com / pw = boguspw
@@ Line 90: / Line 90: @@
   * Run Mystic -CFG
-  * Head to Configuration > User Password Policy
+  * Head to Configuration > User Password Policy.
-  * Set 'Allow Reset by E-mail' to Yes
+  * Set 'Allow Reset by E-mail' to Yes.
-  * Head to Servers > General Options
+  * Head to Servers > General Options.
   * Set the SMTP settings that are displayed in this screen as follows:
@@ Line 121: / Line 121: @@
-  *   [[cryptlib|Mystic BBS uses Cryptlib]] in order to perform the encryption for SSH and SSL-based servers and clients. You need to ensure you have this installed for your OS so Mystic can use it to make a successfull SSL/TLS connection to Gmail.
+  *   [[cryptlib|Mystic BBS uses Cryptlib]] in order to perform the encryption for SSH and SSL-based servers and clients. You need to **ensure you have this installed first** so Mystic can use it to make a successful SSL/TLS connection to Gmail.
-    * Sign in to your Google account - the one you used to create your new Gmail address with
+    * Sign in to your Google account - the one you used to create your new Gmail address with.
     * Go to the [[https://myaccount.google.com|account maintenance]] page.
     * Select 'Security' from the options on the left hand navigation.
-    * Scroll down to the section called 'Less secure app access' and turn this ON
+    * Scroll down to the section called 'Less secure app access' and turn this ON.
 Now you are ready to test.
@@ Line 132: / Line 132: @@
   * 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 'success' message after approx 4-7 seconds. You can check you node log for the active user to see details of what has happened with the SMTP session that just ran.
+  * You should see a 'success' message after approx 3-5 seconds.
-  * The email should arrive in your test users email account approximately 3-4 minutes later with a reset code to enter.
+  * 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.