config_echomail_nodes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
config_echomail_nodes [2018/01/04 02:31] – [Page 5 of 6 - FTP] avon | config_echomail_nodes [2022/09/26 01:31] – adding 'uplink' content avon | ||
---|---|---|---|
Line 9: | Line 9: | ||
From the opening screen you can see EchoMail Node that have already been created. | From the opening screen you can see EchoMail Node that have already been created. | ||
- | | + | ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ |
- | | + | |
- | | + | ─────────────────────────────────────────────────────────────────────────── |
- | | + | |
- | | + | |
- | | + | |
- | Press / for command list | + | |
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | | ||
+ | ─────────────────────────────────────────────────────────────────────────── | ||
+ | Press / for command list | ||
+ | | ||
The / key reveals a command list menu. | The / key reveals a command list menu. | ||
- | | + | I Insert |
- | C Copy | + | |
- | D Delete | + | |
- | E Exports | + | |
+ | F FileBone Exports | ||
+ | 1 Send AreaFix | ||
+ | 2 Send FileFix | ||
+ | 3 Netmail SysOp | ||
+ | | ||
- | This menu allows you to add or remove EchoMail Nodes from the system. You can also copy an existing EchoMail Node and paste (or move) the copied nodes to elsewhere on the list. The ' | + | This menu allows you to add or remove EchoMail Nodes from the system. |
+ | |||
+ | You can copy an existing EchoMail Node and paste (or move) the copied nodes to elsewhere on the list. | ||
+ | |||
+ | The 'Echomail | ||
+ | |||
+ | The ' | ||
+ | |||
+ | The next three options allow you to quickly and easily contact an EchoMail node to communicate with the SysOp or to add/remove message and file bases or anything else the Area/ | ||
+ | |||
+ | * 'Send Areafix' | ||
+ | * 'Send Filefix' | ||
+ | * ' | ||
+ | |||
+ | If you want these options to work correctly for you it pays to set up the next section with the correct information and ensure you complete all the fields you need to. | ||
Pressing the Enter key on an existing EchoMail Node (or a new EchoMail node) reveals the following screen. | Pressing the Enter key on an existing EchoMail Node (or a new EchoMail node) reveals the following screen. | ||
- | In this example an EchoMail Node has been set up for the fsxNet HUB (21:1/100) to send/ | + | In this example an EchoMail Node has been set up for the fsxNet HUB (21:1/100) to send/ |
==== Page 1 of 6 - General ==== | ==== Page 1 of 6 - General ==== | ||
+ | ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Node ID 1 (21: | ||
| | ||
- | | + | |
- | Zone │ 21 | + | SysOp Name │ Paul Hayton |
- | Net | + | Address |
- | Node │ 100 5:FTP | + | Domain |
- | Point | + | Session Type │ BinkP 6:Dir Toss |
- | | + | |
- | | + | |
| | ||
| | ||
Route Info │ 21:* | Route Info │ 21:* | ||
+ | | ||
Max PKT Size │ 512 | Max PKT Size │ 512 | ||
Max ARC Size │ 2048 | Max ARC Size │ 2048 | ||
Use Filebox | Use Filebox | ||
- | | + | |
+ | Crash Limiter | ||
+ | | ||
+ | | ||
There are a number options you can set on page 1. | There are a number options you can set on page 1. | ||
Line 58: | Line 89: | ||
Define the name of the system you are connecting with. | Define the name of the system you are connecting with. | ||
- | === Zone === | + | === SysOp Name === |
- | + | ||
- | Set the Network Zone of this EchoMail Node. | + | |
- | + | ||
- | === Net === | + | |
- | + | ||
- | Set the Network Net of this EchoMail Node | + | |
- | + | ||
- | === Node === | + | |
- | Set the Network Node of this EchoMail Node | + | Define |
- | === Point === | + | === Address |
- | Set the Network | + | Set the Network |
=== Domain === | === Domain === | ||
- | Set the Domain Name of Network e.g. fsxnet | + | Set the Domain Name of Network. It's best to keep it lowercase and check you spell it correctly. |
=== Session Type === | === Session Type === | ||
Line 134: | Line 157: | ||
the Route Info. | the Route Info. | ||
- | If there is no direct match, Mystic will then look at the Route Info for each Echomail | + | If there is no direct match, Mystic will then look at the Route Info for each Echomail |
+ | |||
+ | === Uplink === | ||
+ | |||
+ | This flag can either be set to Yes or No for each Echomail Node. It works in tandem with MIS POLL UPLINK and is similar to the MIS POLL FORCED command, but instead will only force a poll of Echomail Nodes with the Uplink flag set to Yes. | ||
=== Max PKT Size === | === Max PKT Size === | ||
Line 173: | Line 200: | ||
Defines the drive and directory pathway that is associated with the Filebox to be used with this EchoMail Node. If the directory does not exist then Mystic will offer to create it. | Defines the drive and directory pathway that is associated with the Filebox to be used with this EchoMail Node. If the directory does not exist then Mystic will offer to create it. | ||
+ | |||
+ | === Crash Limiter === | ||
+ | |||
+ | This feature is still being developed. The idea is that when FidoPoll 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. | ||
+ | |||
+ | Keep an eye on this section of the Wiki and we'll update it as the feature evolves ;-) | ||
==== Page 2 of 6 - Security ==== | ==== Page 2 of 6 - Security ==== | ||
+ | ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Node ID 1 (21: | ||
PKT Password | PKT Password | ||
- | FIX Password | + | FIX Password |
- | TIC Password | + | TIC Password |
- | | + | |
- | | + | |
- | │ 6:Dir Toss | + | |
│ | │ | ||
│ | │ | ||
Line 213: | Line 249: | ||
Without this password set your Mystic BBS will ignore the files it receives and/or move them in to the BAD directory defined in the [FileToss] stanza of your MUTIL .ini file | Without this password set your Mystic BBS will ignore the files it receives and/or move them in to the BAD directory defined in the [FileToss] stanza of your MUTIL .ini file | ||
+ | |||
+ | === Encryption Key === | ||
+ | |||
+ | Echomail nodes now have an " | ||
+ | |||
+ | This is done in a way that is completely transparent to unsupporting systems, meaning that you can still route netmail through systems and they will not harm the encrypted netmails! | ||
+ | |||
+ | The other echomail node must of course have the same key configured for your node in order to decrypt the netmail when it arrives. | ||
+ | |||
+ | When routing Netmail, Mystic will intelligently re-encrypt the message between routing points when possible. | ||
=== Security Level === | === Security Level === | ||
- | Placeholder text - this feature under development 1.12 A38 | + | You can set ACS rules for this EchoMail node. Refer to discussion info in the Echomail Node Security section below. |
=== Access Flags === | === Access Flags === | ||
- | Placeholder text - this feature under development 1.12 A38 | + | You can set access flags for this EchoMail Node. Refer to discussion info in the Echomail Node Security section below. |
+ | |||
+ | === Echomail Node Security ==== | ||
+ | |||
+ | Echomail node security is here! The easiest way to think about how this system works is to relate an Echomail node to the way security works for a user in your BBS. Each node will have a security | ||
+ | |||
+ | Different functions throughout the echomail system will eventually have "Echo ACS" strings which work just like the [[access_control|user ACS strings that we're familiar with]]. | ||
+ | |||
+ | Hatch File EACS: g2|s255|fH|u10 | ||
+ | |||
+ | The above would say that any echomail node that is a member of Echomail group 2, OR any node that has a security level of 255 OR any Echomail node that has flag H can hatch files to that file base. The Echomail node with the ID of #10 can also hatch. | ||
+ | |||
+ | The following commands are available within EACS: | ||
+ | |||
+ | s< | ||
+ | equal to < | ||
+ | g< | ||
+ | to < | ||
+ | f< | ||
+ | between A to Z. | ||
+ | u< | ||
+ | allows security to be applied to specific nodes (ID is | ||
+ | shown in echomail node editor). | ||
+ | |||
+ | Just like user ACS, Echomail ACS can also use parenthesis and boolean evaulation. | ||
+ | |||
+ | Echomail ACS has been activated for message base subscribing/ | ||
+ | |||
+ | Hubs can still manually link a base to a node regardless of security, so for example if you wanted to force nodes to always carry a specific echo area, you would give them the base and then set the "List EACS" to an access they do not have (or even use % which is " | ||
+ | |||
+ | This is a very powerful system for managing an Echomail network, and EACS strings will be added to various functions in the future as seen fit. | ||
==== Page 3 of 6 - Groups ==== | ==== Page 3 of 6 - Groups ==== | ||
- | Echo Group 01 │ None | + | Echo Group 01 │ fsxNet |
Echo Group 02 │ None 2:Security | Echo Group 02 │ None 2:Security | ||
Echo Group 03 │ None 3:GROUPS | Echo Group 03 │ None 3:GROUPS | ||
Line 241: | Line 317: | ||
| | ||
- | Placeholder text - this feature under development 1.12 A38 | + | Define which EchoMail groups |
==== Page 4 of 6 - BinkP==== | ==== Page 4 of 6 - BinkP==== | ||
- | + | ||
- | BINKP Hostname │ agency.bbs.geek.nz: | + | BINKP Hostname │ agency.bbs.nz: |
IP Type │ IPV4 2:Security | IP Type │ IPV4 2:Security | ||
- | | + | |
Time Out │ 30 4:BINKP | Time Out │ 30 4:BINKP | ||
Block Size │ 16384 5:FTP | Block Size │ 16384 5:FTP | ||
| | ||
+ | Use SSL/ | ||
Hide AKAs │ Yes | Hide AKAs │ Yes | ||
- | │ | ||
│ | │ | ||
│ | │ | ||
Line 261: | Line 337: | ||
│ | │ | ||
│ Page 4 of 6 | │ Page 4 of 6 | ||
+ | |||
- | A Binkp session | + | A Binkp section |
=== BINKP Hostname === | === BINKP Hostname === | ||
Line 270: | Line 347: | ||
=== IP Type === | === IP Type === | ||
- | Do you wish to use IPV4 or IPV6 when using Fidopoll to connect to this system? | + | Do you wish to use IPV4 or IPV6 when using Fidopoll to connect to this system? |
=== Password === | === Password === | ||
Line 276: | Line 353: | ||
Set the session password your Mystic BBS will send to this EchoMail Node when you poll it using Fidopoll or it connects to your Mystic BinkP server and attempts to send your system Echomail, Netmail and/or other files. | Set the session password your Mystic BBS will send to this EchoMail Node when you poll it using Fidopoll 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 to avoid hassles. | + | This password is case sensitive. Be warned some non-Mystic systems have issues with this. Best advice keep everything UPPERCASE |
=== Timeout === | === Timeout === | ||
Line 289: | Line 366: | ||
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 === | ||
Line 341: | Line 431: | ||
==== Page 6 of 6 - Dir Toss ==== | ==== Page 6 of 6 - Dir Toss ==== | ||
- | === Directory Toss === | + | |
+ | | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ 6:DIR TOSS | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ Page 6 of 6 | ||
+ | | ||
A Directory session has the following options you should set: | A Directory session has the following options you should set: |
config_echomail_nodes.txt · Last modified: 2023/01/03 01:49 by avon