Hello There,

Being that I haven't used Mystic in a situation where it is in
network coordinator environment. I feel the need to ask the question.
How does one use Mystic to handle older style opus netmail messages?
Nodelist processors and such are looking for a netmail folder and not
a JAM based netmail area.


I know I could write a bash script to look for the necessary file(s)
and when found move then to a filebox to be sent out. I was curious
as to if Mystic could handle it on it's own.

I realize that I am asking this more often lately.

Am I missing something?


Jeff:-)

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Fsxnet: The Twisted Ba (21:1/128)

On 12 Mar 2019 at 11:47p, Jeffs pondered and said...

I know I could write a bash script to look for the necessary file(s)
and when found move then to a filebox to be sent out. I was curious
as to if Mystic could handle it on it's own.

I realize that I am asking this more often lately.

In terms of moving files from A to B within a given computer you can use
Mystic to fidopoll an address and set the session as directory type. The set inbound and outbound paths to tell fidopoll where to place and pick up files from. That can help shift things between two bits of kit on the same box. I
do something like this with frontdoor at NET 3

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

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

Jeffs wrote to All <=-

Being that I haven't used Mystic in a situation where it is in
network coordinator environment. I feel the need to ask the question.
How does one use Mystic to handle older style opus netmail messages? Nodelist processors and such are looking for a netmail folder and not
a JAM based netmail area.

I know I could write a bash script to look for the necessary file(s)
and when found move then to a filebox to be sent out. I was curious
as to if Mystic could handle it on it's own.

Hmm, never really had this issue in the network that I run (DixieNet)
using Mystic as the main mail hub. Sorry.

... Email returned to sender -- insufficient voltage.
--- MultiMail/OS/2 v0.50
* Origin: fsxNet: Omicron Theta * Southaven, MS * winserver.org (21:2/136)