So i like to play with things and try to figure them out. I created a test
FTN network to play with in my lab I have 2 mystic servers running one as
the hub and one as the client. I got the echomail message bases to work just fine. The issue i'm having is with the filebases. the base is created on
the hub and set to export to the client node just like the message bases. however i'm not getting the files on the client. After i upload the file to the hub and try and do a poll from the client i get nothing. I must be
missing something somewhere any ideas.

Thanks

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: New Mystic BBS (21:1/189)

On 01/31/17, Malthous pondered and said...

like the message bases. however i'm not getting the files on the client. After i upload the file to the hub and try and do a poll from the client
i get nothing. I must be missing something somewhere any ideas.

Mystic will not by default toss files to echo nodes if files are simply uploaded to a file base. It does toss them if it's processing the file if the file is linked to an associated .TIC file.

In short, the file hatching side of Mystic is still a work in progress. You will see g00r00 had started on it as there are ACS settings in the file base that link to other (as yet to be enabled / written) code that will allow you
to define who can can hatch files etc.

As yet that functionality has yet to be completed.

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Hello Malthous!

31 Jan 17 22:36, you wrote to all:

files on the client. After i upload the file to the hub and try and
do a poll from the client i get nothing. I must be missing something somewhere any ideas.

Yea, your missing the issue that mystic can NOT create it's own TIC files. It only supports processing FDN TIC files that IT can process itself from your main systems inbound. Meaning, Mystic clones whatever TIC's it actually receives, then writes a NEW TIC for the Echonode that are linked to be exported. When this happens, Mystic will copy TIC+files to your echonode File Boxes, it will also delelte said TIC+files when they have benn sucessfully send

out to your other linked systems.

--- GoldED+/W32-MSVC 1.1.5-b20160201
* Origin: flupH * fluph.darktech.org (21:1/105)

On 01/31/2017 05:36 PM, Malthous wrote:

So i like to play with things and try to figure them out. I created a test FTN network to play with in my lab I have 2 mystic servers running one as the hub and one as the client. I got the echomail message bases to work just fine. The issue i'm having is with the filebases. the base is created on the hub and set to export to the client node just like the message bases. however i'm not getting the files on the client. After i upload the file to the hub and try and do a poll from the client i get nothing. I must be missing something somewhere any ideas.

Thanks

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: New Mystic BBS (21:1/189)

Yup, sounds normal. Mystic is Alpha and that's not working without a
..tic file. It needs something to create a valid .tic or a filebox to
send it out. Not sure of the details. You can use an external program to
do it, but it's not a built in thing yet. Check with Avon and others as
to what they do.

--- Mystic BBS/NNTP v1.12 A31 (Raspberry Pi)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

Avon wrote to Malthous <=-

Mystic will not by default toss files to echo nodes if files are simply uploaded to a file base. It does toss them if it's processing the file
if the file is linked to an associated .TIC file.

In short, the file hatching side of Mystic is still a work in progress. You will see g00r00 had started on it as there are ACS settings in the file base that link to other (as yet to be enabled / written) code that will allow you to define who can can hatch files etc.

As yet that functionality has yet to be completed.

There are ways and means. I use a script that generates a .tic and places it and the file to be hatched into Mystic's inbound, so mutil can toss it and pass it on to other systems in the file echo, as if it came from another system. My approach uses either a fake address (if you're the ZC/NC), or a point address (if you're a node), as a virtual origin address for the file.


... After Tuesday, even the calender says WTF.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

bcw142 wrote to All <=-

Yup, sounds normal. Mystic is Alpha and that's not working without a
..tic file. It needs something to create a valid .tic or a filebox to
send it out. Not sure of the details. You can use an external program
to do it, but it's not a built in thing yet. Check with Avon and others
as to what they do.

See my previous message, I described my system for hatching files.


... Politics = Poly(many) + tics(blood sucking parasites)
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

There are ways and means. I use a script that generates a .tic and
places it and the file to be hatched into Mystic's inbound, so mutil can toss it and pass it on to other systems in the file echo, as if it came from another system. My approach uses either a fake address (if you're

Would you by chance be able to provide any info on the specs/format of the
.tic file did some googling but have come up empty.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: New Mystic BBS (21:1/189)

Malthous wrote to Vk3jed <=-

Would you by chance be able to provide any info on the specs/format of
the .tic file did some googling but have come up empty.

I got some help from Avon, and a couple of other BBSs carry the spec. I could hatch my "hatch" script to FSX, which builds the .tic line by line. It was written to work with Mystic, but could work with other TIC processors.


... Command not found. Damn, it was here a minute ago... hold on...
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

On 02/07/17, Vk3jed said the following...

Malthous wrote to Vk3jed <=-

Would you by chance be able to provide any info on the specs/format o the .tic file did some googling but have come up empty.

I got some help from Avon, and a couple of other BBSs carry the spec. I could hatch my "hatch" script to FSX, which builds the .tic line by
line. It was written to work with Mystic, but could work with other TIC processors.

Sounds like something that should be shared. :)

+- $s.s$s.s$ ----------------------------------------+
| $ý"$$$"ý$ twinklebbs.homeip.net |
| .$$$. winkle BBS twinklebbs.homeip.net:8080 |
+-- .$$$$$. -----------------------------------------+
$ý"~"ý$ Christopher Malo aka Pequito!

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Twinkle BBS (21:1/126)

Pequito wrote to Vk3jed <=-

Sounds like something that should be shared. :)

It was going to be, but Paul and I have a disagreement about one aspect of configuring it, and what he was asking to me to do didn't make logical sense (and I doubt it would work). I will tweak the documentation to suggest what I think should work and not upset network and zone coordinators. :)


... A bird in the hand's better than one overhead.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

On 02/08/17, Vk3jed pondered and said...

It was going to be, but Paul and I have a disagreement about one aspect
of configuring it, and what he was asking to me to do didn't make
logical sense (and I doubt it would work). I will tweak the
documentation to suggest what I think should work and not upset network and zone coordinators. :)

I'm trying to recall this. From memory my main concern was that if used in fsxNet file echos it could lead to a situation where any node could hatch out any file to any file echos and all nodes attached to it, unchecked.

That's something from a ZC and NC perspective I am not comfortable about.

It's really just a reflection of where g00r00 got to in the development of
file hatching within Mystic. i.e. it's still a work in progress and there are very few checks and balances from a network / HUB point to view to manage
that process.

I note that DM runs an 'uplink' file echo (or similar) in Dorenet so nodes
can use that to send to his HUB for him to in turn send out to others. If required I could look at doing that also if you we're to publicly release
your tool.

I really just want to avoid a situation described above and be able to manage file distribution within the network. Something I'm sure you will understand I'd want to be able to do :)

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Hi Malthous!

07 Feb 2017 01:03, from Malthous -> Vk3jed:

Would you by chance be able to provide any info on the specs/format of
the .tic file did some googling but have come up empty.

http://ftsc.org/docs/fts-5006.001

CU, Ricsi

--- GoldED+/LNX
* Origin: Deadlines amuse me (21:1/104)