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:46] – avon | config_echomail_nodes [2023/01/03 01:42] – [Page 4 of 6 - BinkP] server type options expanded avon | ||
---|---|---|---|
Line 86: | Line 86: | ||
=== Active === | === Active === | ||
- | A simple yes/now setting - unless you set this to ' | + | A simple yes/now setting - unless you set this to ' |
=== Description === | === Description === | ||
Line 109: | Line 109: | ||
* Binkp - Fidpoll will send/ | * Binkp - Fidpoll will send/ | ||
- | * FTP - Fidopoll | + | * FTP - MIS POLL will send/ |
- | * Directory - Fidopoll | + | * Directory - MIS POLL will send bundles to/from locally configured inbound and outbound directories instead of using BINKP or FTP. |
Depending on the option you choose here, pages 4, 5, or 6 of the configuration settings will need to be configured also. | Depending on the option you choose here, pages 4, 5, or 6 of the configuration settings will need to be configured also. | ||
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 176: | Line 189: | ||
=== Use Filebox === | === Use Filebox === | ||
- | A Filebox is a directory you can place any file in to that will be sent to your EchoMail Node when you next poll it using Fidopoll | + | A Filebox is a directory you can place any file in to that will be sent to your EchoMail Node when you next poll it using MIS POLL or it polls your Mystic BBS. |
There are three options for this setting | There are three options for this setting | ||
* No - Don't enable this feature | * No - Don't enable this feature | ||
- | * Yes- Send files to EchoMail Node if you Fidopoll | + | * Yes- Send files to EchoMail Node if you MIS POLL it or if it polls your Mystic BBS |
* Hold - Only send files to the EchoMail Node if it polls your Mystic BBS | * Hold - Only send files to the EchoMail Node if it polls your Mystic BBS | ||
// | // | ||
Line 206: | Line 219: | ||
=== Crash Limiter === | === Crash Limiter === | ||
- | This feature is still being developed. The idea is that when FidoPoll | + | This feature is still being developed. The idea is that when MIS POLL sends files via BINKP it will skip queueing any files for sending larger than this value. It forces EchoMail nodes to poll and collect these files vs a HUB system spending time transferring large files to them. The value is defined in kilobytes. |
At present there is no logic built in to this feature. That means if you set say a value of 1000 Mystic will send .TIC files that accompany a hatched file to an EchoMail node but if the actual hatched file is larger than 1000kb it will not send at the same time. This can cause issues for the receiving EchoMail node. | At present there is no logic built in to this feature. That means if you set say a value of 1000 Mystic will send .TIC files that accompany a hatched file to an EchoMail node but if the actual hatched file is larger than 1000kb it will not send at the same time. This can cause issues for the receiving EchoMail node. | ||
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 |
- | Use SSL/ | + | |
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 346: | Line 357: | ||
=== BINKP Hostname === | === BINKP Hostname === | ||
- | Set the DNS hostname (and port if required) for the EchoMail Node you will poll using Fidopoll. | + | Set the DNS hostname (and port if required) for the EchoMail Node you will poll using MIS POLL. |
=== IP Type === | === IP Type === | ||
- | Do you wish to use IPV4 or IPV6 when using Fidopoll | + | 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 === | ||
- | Set the session password your Mystic BBS will send to this EchoMail Node when you poll it using Fidopoll | + | Set the session password your Mystic BBS will send to this EchoMail Node when you poll it using MIS POLL or it connects to your Mystic BinkP server and attempts to send your system Echomail, Netmail and/or other files. |
This password is case sensitive. Be warned some non-Mystic systems have issues with this. Best advice keep everything UPPERCASE and limited to no more than 8 characters to avoid hassles. | This password is case sensitive. Be warned some non-Mystic systems have issues with this. Best advice keep everything UPPERCASE and limited to no more than 8 characters to avoid hassles. | ||
Line 369: | Line 391: | ||
Use MD5 hashing when connecting as a client? This hides session passwords so they are not sent in plain text. It's a good idea to use this. | Use MD5 hashing when connecting as a client? This hides session passwords so they are not sent in plain text. It's a good idea to use this. | ||
- | |||
- | === Use SSL/TLS === | ||
- | |||
- | Mystic BINKP server and FIDOPOLL now support opportunistic SSL (TLS v1.2+) using a proprietary extension of the BINKP protocol. This means that it will only work with other Mystic BBS clients and servers, but the author plans to document the extension and send it to the authors of other mailers in hopes that it can be standardized. | ||
- | |||
- | EchoMail Nodes now have three settings which can be used when polling for new mail: | ||
- | |||
- | No : FIDOPOLL will not use SSL extension at all | ||
- | Yes : FIDOPOLL WILL use SSL if the server supports it | ||
- | Forced : FIDOPOLL will refuse to exchange mail with a server | ||
- | | ||
- | |||
- | This setting is experimental at present so your mileage may vary. If you're having issues connecting to other systems it's best to set this to ' | ||
=== Hide AKAs === | === Hide AKAs === |
config_echomail_nodes.txt · Last modified: 2023/01/03 01:49 by avon