OK, let me start of by saying I am trying to use the mystic binkp server
with other bbs software, hence what may seem like silly questions.

When I have outgoing mail waiting for any node on any FTN network, should
it be in .../mystic/echomail/out/fidonet (the directory specified in mystic
-cfg), or should it be in a directory under that? If it is for a domain
other than 'fidonet', should it be in a different directory under out?

Does there need to be an associated FLO file with it, or is just having the packets there good enough?

Need to know where to move the outbound packets for a network connect that
is FTN but not FIDO. Thanks!

Mike

##Mmr 2.61á.


--- GTMail 1.26
* Origin: CCO BBS * 502/875-8938 * capcity2.synchro.net (21:1/175.0)

When I have outgoing mail waiting for any node on any FTN network, should it be in .../mystic/echomail/out/fidonet (the directory specified in mystic -cfg), or should it be in a directory under that? If it is for a domain other than 'fidonet', should it be in a different directory under out?

Mystic uses /mystic/echomail/out/fidonet for whichever network you flag as
your main address.. then the other nets you carry have their own outbound .. for instance, for me, my main address is 80:519/0 but that is retronet, but since it is my main address Mystic 'assumes' it is fidonet. one of my AKA's
is piNet 314:314/0 and it uses /mystic/echomail/out/pinet.13a as it's outbound

Does there need to be an associated FLO file with it, or is just having the packets there good enough?

BinkD needs a control file (CLO/FLO/HLO/DLO/?UT) It wont do anything with
files in the outbound if they are not associated with one of these control files. ?LO (also known as BSO/ASO (binkly style outbound/amiga style
outbound) is a pretty old format more widely used over frontdoor's netmail attachment to send it's packets

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: internal dimension ÷ idbbs.dlinkddns.com ÷ port 59 (21:1/178)

Mike Powell wrote to All <=-

OK, let me start of by saying I am trying to use the mystic binkp
server with other bbs software, hence what may seem like silly
questions.

No dramas

When I have outgoing mail waiting for any node on any FTN network,
should it be in .../mystic/echomail/out/fidonet (the directory
specified in mystic
-cfg), or should it be in a directory under that? If it is for a
domain other than 'fidonet', should it be in a different directory
under out?

The following assumes that Fidonet is your primary AKA in Mystic's configuration.

For Fidonet:

Your primary Fidonet zone (the zone your Fidonet address is in) outbound will be

/mystic/echomail/out/fidonet

Other Fidonet zones will be:

/mystic/echomail/out/fidonet.NNN, where NNN is the destination zone number in hex.

For othernets:

/mystic/echomail/out/othernet.NNN

For example, my FSX outbound is

/mystic/echomail/out/fsxnet.015 (zone 21).

Does there need to be an associated FLO file with it, or is just having the packets there good enough?

If the packets are raw packets (*.?ut), then the packet with the correct net/node filename is all oyu need. If the packets are compressed bundles, you will need the appropriate FLO file (*.?lo)

Need to know where to move the outbound packets for a network connect
that is FTN but not FIDO. Thanks!

Hope this helps. :)



... Gee! How'd you ever get it to do THAT?
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

m³Mystic uses /mystic/echomail/out/fidonet for whichever network you flag as ³your main address.. then the other nets you carry have their own outbound .. ³for instance, for me, my main address is 80:519/0 but that is retronet, but ³since it is my main address Mystic 'assumes' it is fidonet. one of my AKA's ³is piNet 314:314/0 and it uses /mystic/echomail/out/pinet.13a as it's outbound ÀÄ[NS=>MP]

OK so where does 13a come from? I know you are going to say "hex," but it
is not the kind of hex I learned which would require your 3 digit zone to be
6 in hex. :) I am more familiar with mainframe hex than ascii, I guess. :)


Mike

##Mmr 2.61á. !link NS 11-11-16 16:11


--- GTMail 1.26
* Origin: CCO BBS * 502/875-8938 * capcity2.synchro.net (21:1/175.0)

Hi Mike!

12 Nov 2016 10:21, from Mike Powell -> Night Stalker:

OK so where does 13a come from? I know you are going to say "hex,"

Easy
314=0x13A

Just convert 314 dez to hex, and you end up with 13A.

CU, Ricsi

--- GoldED+/LNX
* Origin: Only a fool has no doubts (21:1/104)