Mystic uses the Binkley style outbound format for its outgoing files so it's not all that hard. You just need to manually create a flow file in one of your outbound directories.
Assuming you're sending a file to another fsxNet node in your same zone, you would put the flow file into whichever outbound directory you set for your fsxnet domain. Just use /ftn/out/fsxnet as an example. You would then create a text file with the address of the destination node as the filename in a specific format and use .ilo as the filename extension. The first four positions of the filename would be the destination net in hex, the last four positions would be the node in hex. Using your address (21:3/110) as an example:
The net 3 translates to 0x0003 in hex, so the first four letters of the filename are 0003. The node 110 translates to 0x006E so the second half if 006E. The extension of .ilo tells the mailer to send the file immediately. So the filename ends up being /ftn/out/fsxnet/0003006E.ilo for that destination.
The file itself is just a text file with the path and filename(s) you wish to send, one on each line.
Things get more complex if there's already a flow file for the destination node in the outbound directory. In that case it's best to wait for the mailer to finish with that delivery unless you know what you're doing.
I'm probably explaining all of this horribly.
There used to be a number of small utilities to do this all for you much like XROBOT does for FrontDoor mailers. It's unfortunate they all seem to have been lost over time. :(
I believe Mystic also does fileboxes. Those are much easier but it's a bit overkill to create one for a node you're not regularly sending files to.
I really need to learn how to do that. Not sure if it's something
Mystic can do.
--- MultiMail/Win v0.52
* Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)