Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.
FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции FTSC_PUBLIC
Введите FGHI ссылку:


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 01 Apr 24 01:17:44, всего сообщений: 7124
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 4147 из 7124 ====================================== FTSC_PUBLIC =
От   : Carol Shenkenberger              1:275/100          11 Dec 18 17:42:26
Кому : mark lewis                                          11 Dec 18 17:42:26
Тема : What would YOU do?
FGHI : area://FTSC_PUBLIC?msgid=6964.ftsc_pub@1:275/100+20758e86
На   : area://FTSC_PUBLIC?msgid=1:3634/12.73+5c0fd953
= Кодировка сообщения определена как: ASCII ==================================
Ответ: area://FTSC_PUBLIC?msgid=1:3634/12.73+5c11aa38
==============================================================================
  Re: What would YOU do?
  By: mark lewis to Carol Shenkenberger on Tue Dec 11 2018 10:31 am

CS>>>> When it was written, the FTSC meant is there was an address on
CS>>>> IBN, it would priority over the INA address. If no address on IBN,
CS>>>> it would use INA.  If only a port on IBN, use INA but the port on
CS>>>> 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,
ML>>> use it for both...

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

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

I recall looking at examples and asking some questions.  I've been what I call
'dual-homed' like that for a decade or so now but I don't recall when I
actually added it to my listing.  Only that I added it later.

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

ML> INA can't have a port number anyway ;)

Lol well I did say I needed to brush up on that set again.  I guess because
it's not really tied to a specific so that went only on the IBN, ITN etc spots.

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

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

Yes.  I believe my old FAQ (long gone) also showed the pattern I use based off
the Binkd system.

Since I don't connect to any systems set like mine, I can't see if it cycles
through or not.  My ARGUS may well predate that.  Had a node in my Battlenet
league though who did exactly that and would alert me if one seemed down.  He'd
send me a log snippet showing the offender's issues then the other working
flawlessly.  Not a common problem but for 55$ a year, my folks have an option.
I mean really, less than 5$ a month.  I'm good with that.

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


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

ML> did you find it?

Yup!  You addressed it to xxcarol (snicker).  My system doesn't know who that
is so it wasn't obvious.  Thanks though!  I'm pending netmail or email back
from Leslie now.  He's been polling me so there wasn't any backlog to alert me.

  xxcarol
--- SBBSecho 2.12-Win32
* Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)

К главной странице гейта
Powered by NoSFeRaTU`s FGHIGate
Открытие страницы: 0.038165 секунды