Hello Avon,

A question or two. Currently, I have a Win64 version of Mystic installed. That I was contemplating to use as a regional Fido system. I currently have Mystic setup to send Netmail's as Crash\Direct. If I write and export a netmail message Mystic will send it out as routed. If I add the node number that the netmail was addressed to to the node manager in Mystic. Then Mystic will send the netmail message out Crash to the destination address. Am I missing something here?

Question two. MakeNL (Nodelist Manager) needs to know what directory that Mystic uses to store outgoing netmail messages so that it can create and crash out regional nodelist update segments. I was looking to see where that location
might be.

Years ago I just used BinkD, HPT, and Golded for the same purpose.

Heck... :-) I also see where you can specify in Mystic where files that are\were
attached to message are to be stored. I also see in the docs where it states that a file can be attached to any outgoing messages including netmails. But I haven't been able to find where I can actually attach a file to a outgoing netmail message. This is something that I need Mystic to be able to do. Again, am I missing an option and\or command.

Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128.1)

On 06/15/18, Jeff Smith said the following...

Hi Jeff,

currently have Mystic setup to send Netmail's as Crash\Direct. If I
write and export a netmail message Mystic will send it out as routed. If
I add the node number that the netmail was addressed to to the node manager in Mystic. Then Mystic will send the netmail message out Crash
to the destination address. Am I missing something here?

In order for Mystic to know the information about the node your trying to
send the netmail to, you will need to compile the nodelists. This is done
using the 'mutil.ini' file. Just specify the locations of the nodelists, and run 'mutil nodelist.ini', or whatever you name it. Then Mystic will be able
to crash directly to the node.

Question two. MakeNL (Nodelist Manager) needs to know what directory that Mystic uses to store outgoing netmail messages so that it can create and crash out regional nodelist update segments. I was looking to see where that location might be.

What I do here, as I use MakeNL for two networks, is set up the nodes you
will be sending the nodelist segments to, with a filebox. Then just have
MakeNL move the files into that sub-diretory, and Mystic will send them out.

Unfortunately, Mystic doesn't have the ability to utilize the *.msg style messages, and only supports JAM.

Heck... :-) I also see where you can specify in Mystic where files that are\were
attached to message are to be stored. I also see in the docs where it states that a file can be attached to any outgoing messages including

I'm not sure if that is still an option or not. If you do get it figured out, let me know... ;)


---

Black Panther
a.k.a. Dan Richter
Sysop - Castle Rock BBS (RCS)
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
The sparrows are flying again....

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

Hello Black!

15 Jun 18 19:58, you wrote to me:

On 06/15/18, Jeff Smith said the following...

In order for Mystic to know the information about the node your trying
to send the netmail to, you will need to compile the nodelists. This
is done using the 'mutil.ini' file. Just specify the locations of the nodelists, and run 'mutil nodelist.ini', or whatever you name it. Then Mystic will be able to crash directly to the node.

I already have the Fidonet nodelist compiled. I checked and the nodelist.txt file exists in the /data directory and the nodes address info exists in the nodelist.txt file

Question two. MakeNL (Nodelist Manager) needs to know what
directory that Mystic uses to store outgoing netmail messages so
that it can create and crash out regional nodelist update
segments. I was looking to see where that location might be.

What I do here, as I use MakeNL for two networks, is set up the nodes
you will be sending the nodelist segments to, with a filebox. Then
just have MakeNL move the files into that sub-diretory, and Mystic
will send them out.

Yeah, I was thinking that I might end up having to make use of the filebox capability.

Unfortunately, Mystic doesn't have the ability to utilize the *.msg
style messages, and only supports JAM.

That was the conclusion that I had come to also. Sadly, some utilities are limited to *.msg style message format.

Heck... :-) I also see where you can specify in Mystic where
files that are\were attached to message are to be stored. I also
see in the docs where it states that a file can be attached to
any outgoing messages including

I'm not sure if that is still an option or not. If you do get it
figured out, let me know... ;)

I seem to recall being told that Mystic doesn't currently have the
capability to attach a file to a netmail message. That may also be
based upon the fact that Mystic uses JAM for it's netmail messagebase
file type.


Jeff


--- GoldED+/LNX 1.1.5-b20170303 / Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: The Ouijaboard II - Anoka, MN (21:1/128)

On 06/15/18, Black Panther pondered and said...

On 06/15/18, Jeff Smith said the following...

currently have Mystic setup to send Netmail's as Crash\Direct. If I write and export a netmail message Mystic will send it out as routed. I add the node number that the netmail was addressed to to the node manager in Mystic. Then Mystic will send the netmail message out Cras to the destination address. Am I missing something here?

In order for Mystic to know the information about the node your trying to send the netmail to, you will need to compile the nodelists. This is done using the 'mutil.ini' file. Just specify the locations of the nodelists, and run 'mutil nodelist.ini', or whatever you name it. Then Mystic will
be able to crash directly to the node.

This is true, but also if you set 'force NL match' to 'No' in the config > message base settings menu then you can state a FTN address without it
needing to be present in the internal compiled phone book.

Mystic uses the following logic when handling netmails Jeff.

[snip]

+ Mystic, when routing Netmail, will now first compare the destination
address against all configured echomail nodes. If there is a direct match
Mystic will route the Netmail automatically to that node without reviewing
the Route Info.

If there is no direct match, Mystic will then look at the Route Info
for each Echomail node (starting at the first entry) until it finds a
match and redirect netmail through that system.

[snip]

If you're unsure about or what to confirm the top-down route priority then
you can run FIDOPOLL ROUTE to display current settings :)

Question two. MakeNL (Nodelist Manager) needs to know what directory Mystic uses to store outgoing netmail messages so that it can create crash out regional nodelist update segments. I was looking to see whe that location might be.

What I do here, as I use MakeNL for two networks, is set up the nodes you will be sending the nodelist segments to, with a filebox. Then just have MakeNL move the files into that sub-diretory, and Mystic will send them out.

Yes agree with Dan on this one.

Heck... :-) I also see where you can specify in Mystic where files th are\were
attached to message are to be stored. I also see in the docs where it states that a file can be attached to any outgoing messages including

I'm not sure if that is still an option or not. If you do get it figured out, let me know... ;)

I too am unsure.

Best, Paul

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 06/17/18, Avon said the following...

This is true, but also if you set 'force NL match' to 'No' in the config

message base settings menu then you can state a FTN address without it

needing to be present in the internal compiled phone book.

Oooops. I forgot about that setting... :)


---

Black Panther
a.k.a. Dan Richter
Sysop - Castle Rock BBS (RCS)
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
The sparrows are flying again....

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)