config_echomail_nodes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
config_echomail_nodes [2022/09/26 01:51] – remove dated ssl info 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 message bases do not need to be linked to any Echomail nodes in order for Mystic to attempt exporting. | ||
- | Mystic, when routing | + | === Netmail |
- | the Route Info. | + | |
- | If there is no direct match, Mystic will then look at the Route Info for each Echomail Node (starting at the first entry) until it finds a match and redirect | + | 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. | ||
+ | |||
+ | * 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 | ||
+ | |||
+ | To further expand on the automatic Netmail routing logic, Mystic will now perform a FidoNet fuzzy zone match when auto routing Netmail. | ||
+ | |||
+ | To reiterate: For almost everyone, there is never a need touch the Route field in your Echomail node editor. | ||
+ | |||
+ | This system | ||
=== Uplink === | === Uplink === | ||
Line 324: | Line 337: | ||
==== Page 4 of 6 - BinkP==== | ==== Page 4 of 6 - BinkP==== | ||
- | |||
BINKP Hostname │ net1.fsxnet.nz | BINKP Hostname │ net1.fsxnet.nz | ||
IP Type │ IPV4 2:Security | IP Type │ IPV4 2:Security | ||
- | | + | Server Type │ Normal |
- | Time Out │ 30 | + | Password |
- | Block Size │ 16384 5:FTP | + | Time Out │ 30 |
- | | + | Block Size │ 16384 6:Dir Toss |
+ | | ||
Hide AKAs │ Yes | Hide AKAs │ Yes | ||
- | | + | |
- | │ | + | Upload Limit │ 0 |
- | │ | + | Download Limit │ 0 |
│ | │ | ||
│ | │ | ||
│ | │ | ||
│ Page 4 of 6 | │ Page 4 of 6 | ||
- | |||
A Binkp section has the following options you should look at and in most cases set up: | A Binkp section has the following options you should look at and in most cases set up: | ||
Line 350: | 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 | 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 | ||
+ | * Direct SSL : Connect with a direct SSL connection | ||
+ | * StartTLS (If Available) : Use TLS when available | ||
+ | * StartTLS (Required) | ||
+ | |||
+ | 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 === | === Password === | ||
Line 372: | 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? | 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' | ||
+ | |||
+ | 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. | ||
+ | |||
+ | 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. | ||
+ | |||
+ | === 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 ==== | ==== Page 5 of 6 - FTP ==== |
config_echomail_nodes.txt · Last modified: 2023/01/03 01:49 by avon