Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages! You are not logged in. Login here for full access privileges. |
Previous Message | Next Message | Back to Mystic BBS <-- <--- | Return to Home Page |
|
||||||
From | To | Subject | Date/Time | |||
Paul Hayton | Ben Ritchey | Re: netmail routing |
July 12, 2018 3:57 PM * |
|||
On 07/11/18, Ben Ritchey pondered and said... BR> St> doesn't stop you from sending routed netmail or anything. Stripping BR> St> out nodes from the internal nodelist just stops them from coming up i BR> St> searches. BR> BR> Well, without knowing that a node is Pvt (which is the case when BR> excluded) it can't possibly know how to route a message for a Pvt node. BR> {chuckle} It may get BR> routed to your uplink who can then host route properly I guess... The process is Mystic generates an internal nodelist that is used in the nodelist browser feature and also as a prompt for users when attempting to search for and send a message to a netmail style base. The way that internal nodelist directory is built is determinate upon the nodelists selected using the nodefile values and the switches used in the [MergeNodeLists] stanza [snip] [MergeNodeLists] ; Strip nodes marked as DOWN? strip_down = true ; Strip nodes marked as PRIVATE? strip_private = true nodefile=d:\nodelists\nodelist nodefile=d:\nodelists\agoranet [snip] Static is correct that the cosmetic nodelist lookup won't stop a sender sending netmail to a private node. But the caveat is that mystic -cfg > configuration > message setting > force NL match = No. If set to yes, then a user will only be allowed to compose a netmail to the addresses in the internally built nodelist directory. Regardless, if 'force NL match' is set to 'no' and someone composes a message to a PVT node then Mystic will handle the netmail the same way it does all the rest. If the address is known to the composing system as an echomail node Mystic will route it direct to the node. Else, Mystic will start at the first defined echomail node and look at routing info against it to determine if it can route the netmail via that echomail node. If not it continues on down the list checking each echomail node for routing instructions that will allow it to route the netmail via a subsequent echomail node. To use Zone 21 as an example a fsxNet node that sends netmail to a PVT node will have it's netmail routed by Mystic via a HUB (21:1/100 , 21:2/100, 21:3/100, 21:4/100) to the PVT node concerned. Best, Paul --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32) * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100) |
||||||
|
Previous Message | Next Message | Back to Mystic BBS <-- <--- | Return to Home Page |
Execution Time: 0.0762 seconds If you experience any problems with this website or need help, contact the webmaster. VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved. Virtual Advanced Copyright © 1995-1997 Roland De Graaf. |