On 2018 Dec 10 17:35:54, you wrote to me:

 CS>>> When it was written, the FTSC meant is there was an address on IBN,
 CS>>> it would priority over the INA address. If no address on IBN, it
 CS>>> would use INA.  If only a port on IBN, use INA but the port on IBN.

 ML>> and if there is INA and IBN both with domains, use the IBN domain
 ML>> first and then the INA one... if the IBN contains a port number, use
 ML>> it for both...

 CS> I belive the intent was for 2 different domains in that scenerio (like
 CS> mine).

yes, exactly... mine will be like that shortly, too... then i'll be dropping
back to just one after the first of the year...

 CS> I suspect if IBN had a port number and INA didn't then the port number
 CS> should only be used with that domain.

INA can't have a port number anyway ;)

 CS> I need to go back and read the relevant documents to see how that was
 CS> handled and if it was clear.

i think the main thing is the example only shows two INA together and two IBN
together... they can also be mixed... convertors should only be limited by the
capabilities of the mailer they are converting for... if the
argus/radius/taurus family can't handle multiple domains, then that one
convertor should not put in multiple domains... we already know that binkd can
work with them and the binkd_nodelister script is the base convertor used for
the binkd.txt distributed node list...

 ML>> PS: i've just sent you a direct netmail from this point. i watched it
 ML>> get delivered and am writing this just as a "head's up! please check
 ML>> your netmail or unsecure inbound."... it is a message forwarded from
 ML>> the mystic echo that was written back in july 2018...

 CS> Ok, will look for it.    THats just before I joined zone21 where I get
 CS> most of my mystic information.

did you find it?

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Don't tell me how the clock works, just what time it is.
---