| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Ping! |
Hello, Russell! RT>>> Route normal 5:7105/1.0 1:* 2:* 3:* 4:* 5:* RT>>> Not to sure about the 5:* on the end, but .... MS>> could u find out it? I need to know it exactly RT> If you only have 2:* you are only able to route mail for Zone2 ... , RT> so you need to be able to route mail for other Zones, unless you are RT> only corresponding to/with persons in Zone 2, what I am not certain RT> about is whether your default Zone needs to be specified or not, will RT> try with and without and see if "tparser" complains about any one, if RT> no wisdom is gained via that route, I will check what documentation I RT> have here, in this regard RT> ... correct me if i wrong. for example, if one point of your noda has in config Route normal 5:7105/1.0 5:* and then create message to address to zone 2, and send it to your noda then if your noda has in config Route normal 5:7105/1.0 1:* 2:* 3:* 4:* 5:* then this message route perfectly to destination? RT> I will test what ever changes you make, you do not need to have a RT> working connection anywhere, to use other Zone's nodenumbers. RT> You have no need for a point system for testing, just pick a node RT> number, from another Zone, and then examine the config files produced RT> ... , if the correct values for that point/node are in the config RT> files produced, then you are doing well ... RT> Just pick a node number at random from outside Zone 2, run the RT> configuration and then check that the "problems" I pointed out show RT> the correct value for the Zone you have chosen to use for testing RT> purpose. You need to check the values I pointed out to you ... RT> In BinkD.cfg RT> domain fidonet /home/fido/outbound 5 RT> This line is correct/valid for nodes in Zone 5, RT> domain fidonet /home/fido/outbound 1 RT> This line is correct/valid for nodes in Zone 1, RT> domain fidonet /home/fido/outbound 2 RT> This line is correct/valid for nodes in Zone 2, RT> That is, the digit at the end of the line, tells BinkD, which Zone it RT> is being used in ... , and which outbound is the default outbound for RT> that node ... RT> In FidoNet, valid values are either 1, 2, 3, 4, or 5 ... , currently RT> ... RT> Route normal 5:7105/1.0 2:* RT> This line as it stands, says to route all mail as "normal" versus RT> "crash" "hold" etc. for mail addressed to all nodes in Zone 2 via node RT> 5:7105/1.0. RT> No routing has been made for Zones 1, 3, 4, or 5 , so it would not be RT> possible for this system to route mail to nodes in these Zones, from a RT> node system. thnx for explaining, it seems that i understand... mostly L) RT> For a point system this may or may not be a problem ... , at this RT> stage, I don't know what the situation is for a point ... it'be nice to clear it kind regards, Maxim. ... играет:Grand Collection - fausto papetti - bossa for my lady --- GoldED+/LNX 1.1.5-b20080918* Origin: Кто наших истин не поймёт, тому их растолкует пулем (2:5020/828.777) SEEN-BY: 10/1 3 11/201 34/999 120/228 123/500 140/1 222/2 226/0 249/303 SEEN-BY: 250/306 261/20 38 100 1404 1406 1418 266/1413 280/1027 320/119 393/68 SEEN-BY: 396/45 633/104 260 267 285 712/848 800/432 801/161 189 2222/700 SEEN-BY: 2320/100 105 2905/0 @PATH: 5020/828 1042 140/1 261/38 633/260 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™.