Subj : Re: HPT To : TassieBob From : Zip Date : Sun Jul 10 2022 03:08 pm Hello TassieBob! On 10 Jul 2022, TassieBob said the following... Ta> Good news is YOU NAILED IT! I can send netmail for both zones now. That's great news! Ta> Using "the wrong" zone number on the subsequent entry is very Ta> unintuitive, and seems to go against the examples further down in the Yes, I also think it is very counterintuitive... When I think about it, domains can probably simply be seen as yet another layer of addressing, allowing for different FTNs to use the same zone numbers without colliding. Or some kind of separation mechanism in general. Given that, the default domain of a "domain" keyword is really only valid in practice if the outbound directories -- with or without zone numbers -- have unique names, identifying the FTNs (the domains). So "Example 2" kind of nullifies one of the needs for domains in that respect... At least they could have some kind of "NULL" keyword if one doesn't want a "default domain" for a domain (meaning that it should always create . suffixes on the outbound directories)... Ta> THANKYOU! You're very welcome! :-D It might also have been possible to add the "d" (direct) flavor to the node line, meaning that it should not send packets for that node through any other system. But in general that should not be needed; anything that should not be routed through another system should be marked as direct already by the tosser, by it (the tosser) assigning the flow files "*.d??" filenames. Which of course is common for flow files for polling ("*.dlo"). Anyway, glad that you got it working! :) Best regards Zip --- Mystic BBS v1.12 A48 2022/07/07 (Linux/64) * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202) .