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:39] – echomail secuity avon | config_echomail_nodes [2019/03/16 17:55] – added ssl/tls for echomail nodes avon | ||
---|---|---|---|
Line 257: | Line 257: | ||
=== Security Level === | === Security Level === | ||
- | You can set ACS rules for this EchoMail node. | + | You can set ACS rules for this EchoMail node. Refer to discussion info in the Echomail Node Security section below. |
=== Access Flags === | === Access Flags === | ||
- | You can set access flags for this EchoMail Node. | + | 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 ==== | ||
- | The beginning | + | The beginnings |
- | Different functions throughout the echomail system will eventually have "Echo ACS" strings which work just like the user ACS strings that we're familiar with. For example, you might have "Hatch File EACS" in a file base where you could say that you wanted only echomail nodes within a particular group to be able to hatch files, or a particular security level or access flag(s), or even by static echomail node ID. For example: | + | 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]]. For example, you might have "Hatch File EACS" in a file base where you could say that you wanted only echomail nodes within a particular group to be able to hatch files, or a particular security level or access flag(s), or even by static echomail node ID. For example: |
Hatch File EACS: g2|s255|fH|u10 | Hatch File EACS: g2|s255|fH|u10 | ||
Line 277: | Line 277: | ||
==== 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 298: | ||
==== 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 314: | ||
│ | │ | ||
│ Page 4 of 6 | │ Page 4 of 6 | ||
+ | |||
- | A Binkp session | + | A Binkp section |
=== BINKP Hostname === | === BINKP Hostname === | ||
Line 323: | Line 324: | ||
=== 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 330: | ||
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 343: | ||
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