| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Latest version for linux? |
>it wasn't being gated properly... if it were, there would have been two origin >lines and other control lines to enable netmail replies across the zone boundr >to work... No, No, No, because it wasn't being gated at all. The whole dang problem was caused because IREX would only pass mail to a "host" system with a full net node, not a point. When I switched my systems around and couldn't get IREX to work under linux, I got stuck. The fake zone was a temporary work around until I got it working (impossible because it is hard-wired to some old, old dependencies) or until I got a full node number for what is really just "half" of the BBS. Basically, it was getting "gated" from one part of my bbs to another, but it wasn't going anywhere else. And I still don't understand how we are able to have a multi-zone net if all of our software has so many issues with zone boundaries. I see messages from Zones 2 and 3 all the time that are not "gated" into Zone 1. Unless there is also some restrictions on what net #s each zone can use (which, IMHO, makes zones really, really pointless), it does not make any sense to me why it matters if the node is in Zone 1, 2, 3, or 123. :) Mike --- * SLMR 2.1a * A restless eye across a weary room... --- GTMail 1.26* Origin: CCO BBS * 502/875-8938 * capcity2.synchro.net (1:2320/105.1) SEEN-BY: 34/999 90/1 116/18 120/331 123/140 128/187 140/1 218/700 222/2 SEEN-BY: 230/150 240/1120 249/303 250/1 261/38 100 1466 266/404 267/155 SEEN-BY: 280/1027 282/1031 1056 292/908 320/119 219 340/400 393/68 396/45 SEEN-BY: 633/267 280 640/384 712/620 848 770/1 801/161 189 2320/100 105 SEEN-BY: 3634/12 @PATH: 2320/105 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™.