Subj : Bug report To : Joe Delahaye From : Roy Witt Date : Sun Mar 25 2012 06:11:53 23 Mar 12 16:06, Joe Delahaye wrote to Roy Witt: >> JD> I h ave been running 2.31 for quite a while now. No problems >> that I >> JD> have found. I may have missed some though What I find >> JD> irritating about Irex is the fact that it will NOT do a nodelist >> JD> lookup if I send to a specific node, not in its own nodelist. >> >> I came across that when setting up Irex to act more like a hub...I >> found a fix for it, but don't remember what it was. At any rate, Rex >> will use the nodelist to send mail, at least it does here. JD> Wish you could remember that :( Make sure you have the proper compiled nodelist path entered correctly, make sure that it is a compiled nodelist that is the same as what you have Irex 'set up frontend' set to use. I use Front Door up to 2.2 as my front end and a GoldEd nodelist compiler (Irex is compatible with both). >> JD> I seem to recall that it was supposed to do so >> >> If all else fails, Rex will also use your route.rex file to send mail >> to a non-Rex configured system listed there as crash-to. i.e. I have >> crash-to the Z1 Fnews editor in the route.rex file and no Irex node >> configuration entered for the 1:1/1 nodelisting. You may or may not >> have noticed that in the very first config section of Rex, you can >> choose to send mail to 'nodelisted systems only' or send mail to >> unlisted systems. Check that setting and you may have solved your >> nodelist usage problem. >> JD> If you mean, Send to Unknown Nodes, I have that set to YES JD> I see no other setting for that I have all of the settings in that config window as Yes, except for one, 'keep rexfix messages'. 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) .