Subj : Re: SIO/SIO2K
To   : Phoobar
From : Vk3jed
Date : Wed May 06 2020 16:50:00

-=> On 05-05-20 05:51, Phoobar wrote to Vk3jed <=-

 Vk>  Ph> put down what I have & what it should be...I would give you a GIANT h
 Vk>  Ph> when it starts working.
 Vk> The domains...  Maybe post it again. :)

 Ph> # Number @ end is the root zone
 Ph> domain fidonet     d:\\fe\\outbound 1
 Ph> domain fsxnet      d:\\fe\\outbound 21
 Ph> domain wwivftn     d:\\fe\\outbound 11
 Ph> domain scinet      d:\\fe\\outbound 77
 Ph> domain spooknet    d:\\fe\\outbound 700
 Ph> domain micronet    d:\\fe\\outbound 618
 Ph> domain vkradio     d:\\fe\\outbound 432
 Ph> domain amiganet    d:\\fe\\outbound 39

 Ph> Believe I have it set up correctly.

Hmm, looks like a 4D setup, but normally the same default zone applies to all
domains - in other words, all of those entries should be followed by a "1". 
That's how my Binkley config worked in the 90s with 4D tossers (except I had a
3 instead of 1, because I'm in Fidonet z3). :)  The way you have it, there's no
real way for the mailer to know where a packet is meant to be sent, because
they'll all be in the same outbound, and the most likely result (going by
experience) binkd will attempt to poll *:nnn/fff - in other words, every zone
with the matching net/node!

If the default zone is the same for all domains, then the otherzones will have
an outbound.nnn directory, where nnn is the zone number in hex, and binkd will
know what zone mail in the outbounds is for.

 Vk>  Ph> True. Got it stopped by REM'ing out the SIO2K lines...rebooting & goi
 Vk>  Ph> back in there. One time it will boot...next time...it throws up the
 Vk>  Ph> error message.
 Vk> Hmm, OK.  Annoying.

 Ph> Rebooted a couple of times & no issues.

*whew*. :)


.... Paradox: We have more degrees but less sense.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
 * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

.