TIP: Click on subject to list as thread! ANSI
echo: irex
to: Michiel van der Vlist
from: Roy Witt
date: 2012-03-30 07:20:36
subject: Bug report

30 Mar 12 10:29, Michiel van der Vlist wrote to Roy Witt:

 RW>> Dunno what to tell you, Joe. I've been using it for that long too
 RW>> and have no problem with Irex finding AND using the nodelist. When I
 RW>> enter a new node in the Node Manager, it always wants to use the
 RW>> nodelist entry to config the node entry in Irex. Unfortunately, it
 RW>> always enters the fzn.fidonet.org (?) crappola. Which is basically
 RW>> useless.

 MvdV> Joe was originally referring to the situation where a node is not
 MvdV> configured in Irex's node manager.

 MvdV> According to the manual, if a message has the crash bit set, Irex
 MvdV> will do a nodelist lookup and if the destination supports one of
 MvdV> Irex's protocols, sent the message directly to the destination.

 MvdV> That however does not work.

That situation can be changed by adding such a node to the node manager.
With a registered Irex 50 node limit, easily done.


                R\%/itt


  ... Only those who will risk going too far can possibly
  ... find out how far one can go ~ TS Eliot


--- Twit(t) Filter v2.1 (C) 2000-10
* Origin: Roiz Flying \A/ Service * South Texas * USA * (1:387/22)
SEEN-BY: 3/0 633/267 640/954 712/0 313 550 620 848 953
@PATH: 387/22 123/500 261/38 712/848 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.