config_echomail_nodes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
config_echomail_nodes [2022/09/26 01:58] – adding netmail logic changes avon | config_echomail_nodes [2023/01/03 01:42] – [Page 4 of 6 - BinkP] server type options expanded avon | ||
---|---|---|---|
Line 159: | Line 159: | ||
=== 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: | If no route is found from the Route string then Mystic will now attempt to automatically route Netmail based on some basic address logic: | ||
Line 169: | Line 169: | ||
* 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 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. | ||
- | This new system allows for Netmail to work automatically without any knowlege | + | 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 allows for Netmail to work automatically without any knowledge | ||
=== Uplink === | === Uplink === | ||
Line 333: | 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 359: | 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 === |
config_echomail_nodes.txt · Last modified: 2023/01/03 01:49 by avon