= Сообщение: 4091 из 7124 ====================================== FTSC_PUBLIC = От : mark lewis 1:3634/12.73 09 Dec 18 11:57:00 Кому : Michiel van der Vlist 09 Dec 18 11:57:00 Тема : FTS-5001 FGHI : area://FTSC_PUBLIC?msgid=1:3634/12.73+5c0d4b4a На : area://FTSC_PUBLIC?msgid=2:280/5555+5c09889c = Кодировка сообщения определена как: CP437 ================================== Ответ: area://FTSC_PUBLIC?msgid=2:240/1661+5bfd8f7f ============================================================================== On 2018 Dec 06 21:22:06, you wrote to Fred Riccio:
MV> With the Schwartz interpretation, how does one signal, that fido.vlist.eu MV> is to be used for ITN and IVM and fido.vlist.eu for IBN but fido.vlist.net MV> is NOT to be used for IBN?
take off the INA and move the domain to those two flags... the "system name" field and the INA flag signal the default domain to use... in your example IBN is not supported on the default domain so you cannot use a default domain entry in the "system name" field or the INA flag... you have to list the domain on the flags for the protocols... the question then is "are both ITN and IVM supported on fido.vlist.net as well as fido.vlist.eu?"... since your IBN knocks out the ability to use the default domain, you would list two ITN and two IVM flags with the two domains... i fail to see how this is any sort of alternate interpretation or understanding of the documentation...
FR>> To quote a past FTSC chair, "If you do it this way, it will work".
MV> But if one does NOT do it this way and makes something else, it may not MV> work. Having two conflicting interpretations of the same flag does not MV> work.
i don't understand what conflicting interpretations of which flag there are...
)\/(ark
Always Mount a Scratch Monkey Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong... ... Disclaimer: We've no idea how the hell this happened (hee hee titter). --- * Origin: (1:3634/12.73)
