Differences

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

--- config_echomail_nodes [2022/09/26 01:56] – adding netmail logic changes avon
+++ config_echomail_nodes [2023/01/03 01:49] (current) – [Page 4 of 6 - BinkP] upload/download limits added avon
@@ Line 157: / Line 157: @@
 NetMail message bases do not need to be linked to any Echomail nodes in order for Mystic to attempt exporting.
-==== Netmail Routing Logic ====
+=== Netmail Routing Logic ===
-Netmail will now first always try to route using the Route strings defined for each node.  Previously it would look for a direct address match first before doing this.
+Netmail will first always try to route using the Route strings defined for each node.
 If no route is found from the Route string then Mystic will now attempt to automatically route Netmail based on some basic address logic:
-First it will look for a direct address match in Echomail Nodes and if one is found it will route directly to the node.
+  * First it will look for a direct address match in Echomail Nodes and if one is found it will route directly to the node.
-If there is no direct match then Mystic will perform some logic to select the best node that it can find.  If your system gets a Netmail for 1:123/123.1 and there is no direct match, Mystic will look for a 1:123/123 node.  If there isn't one, then it will look for a 1:123 node with priority given to the 1:123/1 if exists.  If a node is still not found then Mystic will look for a zone match, and finally if no zone match is found then the Netmail will fail to route.
+  * If there is no direct match then Mystic will perform some logic to select the best node that it can find.  If your system gets a Netmail for 1:123/123.1 and there is no direct match, Mystic will look for a 1:123/123 node.  If there isn't one, then it will look for a 1:123 node with priority given to the 1:123/1 if exists.
-This new system allows for Netmail to work automatically without any knowlege of routing being required for most people while still allowing full control for power users.
+  * If a node is still not found then Mystic will look for a zone match, and finally if no zone match is found then the Netmail will fail to route.
+To further expand on the automatic Netmail routing logic, Mystic will now perform a FidoNet fuzzy zone match when auto routing Netmail.  If a zone is between 1 and 6 they will find a match to a hub which is also part of a zone 1 through 6 if no other (better) routing match could be found.
+To reiterate: For almost everyone, there is never a need touch the Route field in your Echomail node editor.  If you ever want to test where a Netmail will route you can type "mis poll route <address>" and it will tell you where Mystic will route a message to that address based on your current configuration.
+This system allows for Netmail to work automatically without any knowledge of routing being required for most people while still allowing full control for power users.
 === Uplink ===
@@ Line 331: / Line 337: @@
 ==== Page 4 of 6 - BinkP====
    BINKP Hostname │ net1.fsxnet.nz                            1:General
    IP Type        │ IPV4                                      2:Security
-   Password       │ *****                                     3:Groups
+   Server Type    │ Normal                                    3:Groups
-   Time Out       │ 30                                        4:BINKP
+   Password       │ ********                                  4:BINKP
-   Block Size     │ 16384                                     5:FTP
+   Time Out       │ 30                                        5:FTP
-   CRAM-MD5       │ Yes                                       6:Dir Toss
+   Block Size     │ 16384                                     6:Dir Toss
+   CRAM-MD5       │ Yes
    Hide AKAs      │ Yes
-                  │
+   Escape Mode    │ Auto
-                  │
+   Upload Limit   │ 0
-                  │
+   Download Limit │ 0
                   │
                   │
                   │
                   │                                          Page 4 of 6
 A Binkp section has the following options you should look at and in most cases set up:
@@ Line 357: / Line 362: @@
 Do you wish to use IPV4 or IPV6 when using MIS POLL to connect to this system? Or do you wish to set a preferred connection type and then a fallback type? e.g. IPV6 + IPV4 or IPV4 + IPV6
+=== Server Type ===
+There are four possible options for this setting:
+  * Normal                  : Do not use SSL at all
+  * Direct SSL              : Connect with a direct SSL connection
+  * StartTLS (If Available) : Use TLS when available
+  * StartTLS (Required)     : Always require SSL connection to remote
+The StartTLS Required option will refuse to authenticate with any server that does not offer the opportunistic TLS upgrading. These features require that CryptLib is present and detected by Mystic.
 === Password ===
@@ Line 379: / Line 395: @@
 Hide alternative network addresses during a BinkP handshake. When your system polls this EchoMail Node will it only show the network address you have set up for the same Zone this EchoMail Node has in common with or it will show all your defined EchoMail addresses?
+=== Escape Mode ===
+Mystic's BINKP server now has a default "Escape mode" option which will  apply to any unknown connections that do not have a configuration in the Echomail nodes.  Echomail nodes have their own individual setting for this    in the node editor.
+This setting determines how Mystic will escape special characters in filenames and defaults to the Auto setting.
+When set to **Auto**, Mystic will automatically try to determine the escape mode by using the VERSION frame sent by the mailer.  If no version frame is found, Mystic will use FTS standard modern \x## escape mode.
+When set to **Legacy**, Mystic will use the \## format of file escaping which is used in some legacy mailers such as Argus, Internet Rex, and older versions of Mystic.
+When set to **Modern**, Mystic will use the \x## format which is preferred or even required by some newer mailers such as BinkD, Radius, and BinkIT.
+It is highly recommended to always keep these set to AUTO unless there is a very specific reason not to.  The escape mode will be logged after authentication if the loglevel is set to Verbose or higher.
+=== Upload Limit ===
+Set the upload speed limit: (Used when you send files to this node)
+BINKP has the ability to limit the bandwidth used when sending or  receiving files.  Setting any of these values to 0 disables the limit and causes them to operate at full speed.  Any non-zero value sets the maximum rate in Kilobytes (KB) to use for the connection. This setting overrides MIS POLL/BINKP settings if enabled.
+=== Download Limit ===
+Set the download speed limit: (Used when you receive files from this node). This setting overrides MIS POLL/BINKP settings if enabled.
 ==== Page 5 of 6 - FTP ====