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


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 01 Apr 24 01:17:44, всего сообщений: 7124
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 4023 из 7124 ====================================== FTSC_PUBLIC =
От   : Michiel van der Vlist            2:280/5555         06 Dec 18 00:38:36
Кому : Carol Shenkenberger                                 06 Dec 18 00:38:36
Тема : Candidates vision request
FGHI : area://FTSC_PUBLIC?msgid=2:280/5555+5c0865ed
На   : area://FTSC_PUBLIC?msgid=6837.ftsc_pub@1:275/100+206c8cb5
= Кодировка сообщения определена как: CP850 ==================================
Ответ: area://FTSC_PUBLIC?msgid=1:132/174+5c0907ac
Ответ: area://FTSC_PUBLIC?msgid=6864.ftsc_pub@1:275/100+206f1ae5
Ответ: area://FTSC_PUBLIC?msgid=1:3634/12.73+5c0d424e
==============================================================================
Hello Carol,

On Tuesday December 04 2018 21:46, you wrote to me:

MV>> ,100,Shenks_Express,Virginia_Beach_VA,Carol_Shenkenberger,-Unpubl
MV>> ished-, 300,XX,CM,INA:shenks.synchro.net,IBN:shenks.dyndns.org

MV>> Can you tell us according to what part(s) of which FTSC
MV>> standard(s) this nodelist entry contains information that is
MV>> never used by a properly configured mailer?

FAIL.

From FTS-5001.006:

  INA           This flag sets a default server address used
                 for any Internet Protocol Flag that does not
                 specify its own.

So, a properly configured binkp mailer will see that the IBN flag carries a server address. It will use that and nothing alse to connect. A binkp mailer will NOT look at the INA flag since that is to be used for any other protocol who's flag has no server address of its own. But there are no other IP protocol flags. So no mailer will ever use the server address from the INA flag. The INA flag is dead wood. It is "unreachable code".

CS> What standards do you show to represent when a site has 2 resolving
CS> addresses, one preferred for IBN but the other for everything?  Z1
CS> practical resolution, yet another thing not documented.

It /IS/ documented. FTS-5001.006:

  Multihomed systems
  ------------------

  Multihomed systems or systems that are otherwise reacheable by more
  than one address, may - instead of adding another A or AAAA record
  to the DNS zone of the host name - repeat the flag(s) carrying the
  address with another address.

  Example: IBN:host1.example1.tld,IBN:host2.example2.tld
  Or:      INA:host1.example1.tld,INA:host2.example2.tld,IBN


This was discussed by the FTSC members in the Private FTSC area in 2017. You are an FTSC member, you were there. Apparently you did not pay attention.

CS> The world is not black and white.

Some things ARE black and white. A woman is either pregnant or she is not. One can not be a little bit pregnant.

FTS-5001 is clear. Sorry Carol, the listing for 1: 275/100 is not FTSC complient. And you failed to see why. You failed the test.



Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

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