Domains, zone numbers, primary address and outbound directories
From
Björn Wiberg@2:201/137 to
g00r00 on Sat Jul 23 14:16:37 2022
Hello g00r00!
It appears that Mystic (or rather mutil) always creates outbound packets/bundles in zone-numbered outbound directories for all domains which do not correspond to the domain of the primary echomail address.
For example, if I have an echomail address 21:1/202 with domain "fsxnet" marked as primary, it will use the Outbound Primary directory (in my case /mnt/bbs/echomail/out/fsxnet) for packets/bundles, at least for zone 21 (which currently is the only zone within fsxNet).
But for domains of other FTNs -- for which my echomail addresses cannot be marked as primary, as there can only be one echomail address flagged as primary -- a zone number will always be appended to the outbound directory.
E.g. for FidoNet, with an echomail address of 2:201/137 and the domain "fidonet", the outbound directory will become /mnt/bbs/echomail/out/fidonet.002, and not /mnt/bbs/echomail/out/fidonet (as
I would prefer).
Is it in some way possible to make Mystic (mutil) not add zone numbers to the outbound directory for those other FTNs? I.e., to have one primary address defined within each domain?
Just wondering, as I've been wading through binkd configuration and ifcico source code to see whether it is possible for those + Mystic to coexist with a common baseline for outbound directory naming...
Thanks in advance!
Best regards
Bj”rn
--- Mystic BBS v1.12 A48 2022/07/15 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)