| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: January Echolist |
-=> On 01-31-08 23:04, Janis Kracht <=-
-=> spoke to Thom Lacosta about January Echolist <=-
JK> In your routing table you _could_ possibly be routing mail
JK> for Bo through my system, i.e., something like
JK> Route 2:236/100 1:261/38
JK> Route 1:* 2:* 3:* 4:* 5:* 6:* 1:123/500
JK> The above would say route 2:236/100 through 261/38, but
Actually I think the first one says to route mail for 261/38 through
2:236/100:-}} I.e., I think you have them reversed.
JK> route everything else through Ross at 123/500.
Not at all sure of the effect of this command, but it should have the
1:123/500 (the routed destination) first, then followed by the wild
cards. I recently replace my command with
route crash 1:123/500 World
Dale Shipp
fido_261_1466 (at) comcast (dot) net
(1:261/1466)
... Shipwrecked on Hesperus in Columbia, Maryland. 23:51:15, 01 Feb 2007
___ Blue Wave/DOS v2.30
--- Maximus/NT 3.01
* Origin: Owl's Anchor (1:261/1466)SEEN-BY: 10/1 3 14/300 34/999 90/1 106/1 114/635 120/228 123/500 134/10 140/1 SEEN-BY: 222/2 226/0 236/150 249/303 261/20 38 100 1381 1404 1406 1418 SEEN-BY: 266/1413 280/1027 320/119 393/68 633/260 262 267 285 712/848 800/432 SEEN-BY: 801/161 189 2222/700 2320/100 105 200 2905/0 @PATH: 261/1466 123/500 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™.