Subj : Re: HPT To : TassieBob From : Zip Date : Sun Jul 10 2022 11:35 am Hello TassieBob! On 10 Jul 2022, TassieBob said the following... Ta> Tried that (but tried it again, just in case I pooched it up the first Ta> time). I didn't have any luck, but I'll do some more fiddling... OK! Ta> Has given me some pointers towards things to look at - muchly Ta> appreciated. You're very welcome! Hoping you'll be able to solve it. As a sidenote, when I think of it, my outbound has one primary subdirectory (fsxnet), and the others are adjacent to it: # NOTE: Specifying a matching (21 = 21) default zone will cause the outbound # directory to become /mnt/bbs/echomail/out/fsxnet in practice domain fsxnet /mnt/bbs/echomail/out/fsxnet 21 fsxnet.nz # NOTE: Specifying a non-matching (21 != 2) default zone will cause the # outbound directory to become /mnt/bbs/echomail/out/fidonet.002 in practice domain fidonet /mnt/bbs/echomail/out/fidonet 21 binkp.net (I'm in FidoNet zone 2.) So, I specify 21 as the default domain for all my FTN networks, and hence get . suffixes to the outbound directory names for all but fsxNet. Of course, having a subdirectory for each network eases things for binkd, but I think your setup with one outbound with all in it (right?) *should* work as well. As 3D setups do exist (for older software), and binkd *should* be able to find out from the outgoing packet filenames which node is the recipient... Best regards Zip --- Mystic BBS v1.12 A48 2022/07/07 (Linux/64) * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202) .