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


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 15 Nov 24 00:30:01, всего сообщений: 7128
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 762 из 7128 ======================================= FTSC_PUBLIC =
От   : Henri Derksen                                       09 Dec 13 05:23:00
Кому : Mark Lewis                                          09 Dec 13 05:23:00
Тема : Dispute from ZCC.
FGHI : area://FTSC_PUBLIC?msgid=2:280/1208@FidoNet+ab1468be
На   : area://FTSC_PUBLIC?msgid=1:3634/12.71+2a0a8d73
= Кодировка сообщения определена как: CP866 ==================================
Ответ: area://FTSC_PUBLIC?msgid=1:3634/12.71+2a5d94d1
==============================================================================
Hello Mark,

HD> That means there is a BBS too!
RW> Not really.
HD> Yes, almost ALLWAYS!
HD> If there is no BBS, the node should be listed with an MO flag.

ML> should be but they are not always listed as mail only...

That's why I used the words "almost" and "should".

HD> Or the system is not well configurated,
HD> or the nodelist entry is wrong.

ML> that depends on one's perspective(s)...

That's the wrong practise.
FTSC documents and NodeList epilogue are very clear about this item.

ML> not everyone in fidonet thinks the same way ;)

Not listing a MO flag, and rejecting BBScallers is Annoying Behavior.
Because it costs POTS BBS-callers money for nothing; CONNECT, No Carrier...
A BBScaller can ask a *C to correct the listing when needed.

HD> No MO-Flag, there should be a BBS, and a mailer, both! period.
HD> MO flag, than BBS-users have no access, only mailers.

RW> The CM flag indicates that the node is in Continuous Mail mode.

HD> You are confused.
HD> That's CM flag is to indicate the node is 24 h online and always
HD> accept mail, also outside ZMH.

ML> true...

Not only that,
it has nothing to do with the absents of the MO flag I started talking
about, to prove that a Nodenumber is not always only the SysOp behind
the mails from that AKA,
but also could be one of the BBS-users ((Co-)SysOp inclusive).

HD> First there were BBSes, then they were connected to exchange mail too.
HD> And later on many are Mail Only withouth a BBS, hence the MO-flag.
HD> The CM flag does not indicate there a BBS or not, i.e. irrelevant.
HD> The MO flag does wat it tells you, Mail Only, so No BBS.

ML> true for the most part...
ML> MO was also implemented when there were a lot of BBS callers using the
ML> nodelist to locate BBSes they wanted to call and visit...
ML> adding the MO flag helped to indicate to them that there was
ML> no BBS available...

I knew.

ML> however, it didn't stop all callers...

Indeed, and then there came the private nodes ;-).
I.e. the Private keyword plus "Unplublished" in the phone field.
That combination already started very many discussions,
but that is another (not finished) thread, MakeNL comes to mind ;-).

ML> plus MO doesn't mean that there is not a BBS, either...
ML> perhaps it is a private BBS that is not advertised to the public? ;)

I Agree.
But my main argument was the opposit, i.e.
No MO-flag listed, then there must be a BBS besides the mailer,
otherwise the *C should place a MO flag.
So when no BBS is available, the MO flag is mandatory.

ML> Not only is the Universe stranger than we think,
ML> it is stranger than we can think. - Werner Heisenberg

Not only that, also FidoNet does have many strange birds flying around ;-).

Henri.

---
* Origin: Naugthy dog, do not bite the cable... NO TERRIER.

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