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 [2019/03/16 17:41] – echomail secuity avon | config_echomail_nodes [2022/09/26 01:31] – adding 'uplink' content avon | ||
---|---|---|---|
Line 70: | Line 70: | ||
| | ||
Route Info │ 21:* | Route Info │ 21:* | ||
+ | | ||
Max PKT Size │ 512 | Max PKT Size │ 512 | ||
Max ARC Size │ 2048 | Max ARC Size │ 2048 | ||
Line 156: | 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 265: | Line 270: | ||
=== Echomail Node Security ==== | === Echomail Node Security ==== | ||
- | The beginnings of 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 | + | 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]]. | 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]]. | ||
Line 272: | Line 277: | ||
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 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. | 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. | ||
Line 277: | Line 300: | ||
==== 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 298: | Line 321: | ||
==== Page 4 of 6 - BinkP==== | ==== Page 4 of 6 - BinkP==== | ||
+ | |||
BINKP Hostname │ agency.bbs.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 314: | Line 337: | ||
│ | │ | ||
│ Page 4 of 6 | │ Page 4 of 6 | ||
+ | |||
- | A Binkp session | + | A Binkp section |
=== BINKP Hostname === | === BINKP Hostname === | ||
Line 323: | 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 329: | 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 342: | 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 === |
config_echomail_nodes.txt · Last modified: 2023/01/03 01:49 by avon