Subj : HPT
To   : Zip
From : TassieBob
Date : Sun Jul 10 2022 07:44 pm



 Zi> As a sidenote, when I think of it, my outbound has one primary
 Zi> subdirectory
 Zi> (fsxnet), and the others are adjacent to it:

 Zi> # NOTE: Specifying a matching (21 = 21) default zone will cause the
 Zi> outbound # directory to become /mnt/bbs/echomail/out/fsxnet in
 Zi> practice domain fsxnet /mnt/bbs/echomail/out/fsxnet 21 fsxnet.nz

 Zi> # NOTE: Specifying a non-matching (21 != 2) default zone will cause the
 Zi> # outbound directory to become /mnt/bbs/echomail/out/fidonet.002 in
 Zi> practice domain fidonet /mnt/bbs/echomail/out/fidonet 21 binkp.net

When I was first cutting the config for binkd I did configure it this way but I couldn't find the required HPT directives to make HPT use the separate outbound directories.  The documentation suggested it only supported Binkley-style outbound directories (so a base directory for the primary zone, and .xxx hex encoded subdirectories for other zones).

 Zi> So, I specify 21 as the default domain for all my FTN networks, and
 Zi> hence
 Zi> get .<number> suffixes to the outbound directory names for all but fsxNet.

What I have now is both fsx & tqw using a common outbound path, with fsx using the path as-is (it's primary), and tqw using <path>.539/ (hex encoded 1337).

Even though the outbound packets is in <path>.539/, binkd still thinks it needs to place an outbound call to 1337:2/100@fsxnet, which I have no node line for because, well, it should be 1337:2/100@tqwnet (which I do have a node line for).

 Zi> but I think your setup with one outbound with all in it (right?)

Basically as described above, but for the avoidance of doubt/confusion:

drwxrwxr-x 3 bbs bbs 4096 Jul 10 19:47 outbound      <- fsxnet
drwxr-xr-x 3 bbs bbs 4096 Jul 10 19:52 outbound.539  <- tqwnet

With binkd configured:

domain fsxnet /home/bbs/ftn/outbound 21
domain tqwnet /home/bbs/ftn/outbound 1337

I don't have any specific HPT config for this - it seems smart enough to put mail for my primary/first listed address in outbound, and for zone 1337 into outbound.539

There was a comment earlier that maybe my GoldED config might be the issue, so I tried sending a zone 1337 netmail from Mystic and had the same result.  Possible they're both wrong of course, but I'm leaning towards thinking they're both OK and the problem is with either HPT or binkd - the latter feels more likely from what I'm seeing...

--- GoldED+/LNX 1.1.5-b20220504
 * Origin: TassieBob's BBS (21:3/169)

.