Hi All,

SysOps setting up new Mystic installations from scratch using release A39 should change the default in the [Mergenodelists] section within the mutil.ini file for strip_private from true to false! This also applies to renamed .ini files that do the mergenodelists option. :)

I just setup an A39 Mystic from scratch and missed this setting, which comes with the erroneous default set to true!


.-- Keep the faith, -------------------------------------------------.
| |
| Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
| Email: fido4cmech(at)lusfiber.net |
| Home page: http://cmech.dynip.com/homepage/ |
| |
`-------- WildCat! BBS 24/7 +1-337-984-4794 any BAUD 8,N,1 -------'

... Husbands are like fires. They go out if unattended. -Zsa Zsa Gabor
--- GoldED+/W32-MSVC v1.1.5-g180710-b20180710 ... via Mystic BBS!
* Origin: FIDONet - The Positronium Remote (1:393/68.8)

On 07/11/18, Ben Ritchey said the following...

SysOps setting up new Mystic installations from scratch using release
A39 should change the default in the [Mergenodelists] section within the mutil.ini file for strip_private from true to false! This also applies
to renamed .ini files that do the mergenodelists option. :)

I noticed this when first setting it up and changed it as well, but it doesn't stop you from sending routed netmail or anything. Stripping out nodes from the internal nodelist just stops them from coming up in searches.

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Subcarrier BBS (1:249/400)

* An ongoing debate between Static and Ben Ritchey rages on ...

On 07/11/18, Ben Ritchey said the following...

SysOps setting up new Mystic installations from scratch using
release A39 should change the default in the [Mergenodelists]
section within the mutil.ini file for strip_private from true to
false! This also applies to renamed .ini files that do the
mergenodelists option. :)

I noticed this when first setting it up and changed it as well, but it doesn't stop you from sending routed netmail or anything. Stripping
out nodes from the internal nodelist just stops them from coming up in searches.

Well, without knowing that a node is Pvt (which is the case when excluded) it can't possibly know how to route a message for a Pvt node. {chuckle} It may get

routed to your uplink who can then host route properly I guess...


.-- Keep the faith, -------------------------------------------------.
| |
| Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
| Email: fido4cmech(at)lusfiber.net |
| Home page: http://cmech.dynip.com/homepage/ |
| |
`-------- WildCat! BBS 24/7 +1-337-984-4794 any BAUD 8,N,1 -------'

... Pudding is good for you.
--- GoldED+/W32-MSVC v1.1.5-g20180710-b20180710 ... via Mystic BBS!
* Origin: FIDONet - The Positronium Remote (1:393/68.8)

On 07/11/18, Ben Ritchey pondered and said...

doesn't stop you from sending routed netmail or anything. Stripping out nodes from the internal nodelist just stops them from coming up i searches.

Well, without knowing that a node is Pvt (which is the case when
excluded) it can't possibly know how to route a message for a Pvt node. {chuckle} It may get
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)

*
* On Thursday 12 Jul 2018 193 at 03:57 PM,
* Paul Hayton said to Ben Ritchey,
* about Re: netmail routing ...
*

Ok, thanks Paul. Same thing I described for routing {g}


.-- Keep the faith, -------------------------------------------------.
| |
| Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
| Email: fido4cmech(at)lusfiber.net |
| Home page: http://cmech.dynip.com/homepage/ |
| |
`-------- WildCat! BBS 24/7 +1-337-984-4794 any BAUD 8,N,1 -------'

... I'm a vegetarian, you know, and pork is my favorite vegetable.
--- GoldED+/W32-MSVC v1.1.5-g20180710-b20180710 ... via Mystic BBS!
* Origin: FIDONet - The Positronium Remote (1:393/68.8)

On 07/11/18, Ben Ritchey said the following...

Well, without knowing that a node is Pvt (which is the case when
excluded) it can't possibly know how to route a message for a Pvt node. {chuckle} It may get routed to your uplink who can then host route properly I guess...

Mystic will route through your configured uplink even if the target node is listed. The routing logic of its internal mailer is pretty simple. I'm not
sure it even stores host relationships.

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Subcarrier BBS (1:249/400)