| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Routing problem. |
Hello,
I live in a house with several students and a few days ago one of them
asked me if I could arange a fidonet-point-adres for him. Ofcourse this was
not so much a problem and now we both have a pointnumber with the same boss
(2:283/708). To spare telephone costs I wanted to route his mail through my
system and I wanted to make sure that he could connect echoarea's by me
instead of our boss and route his netmail through my system. All seems to
work fine now except one little thing. When he sends a message to a node
(x:yy/zz.0) it arrives at my system for routing to our boss and when I look
at the message during tossing the destination adress changes from x:yy/zz.0
to x:yy/zz.my_pointnumber. When he simply adresses a message to a
pointnumber different from 0 everything is allright and everything gets
routed through my system, but when he wants to send it to a node everything
gets messed up. Does anyone have an idea what is doing this?
By the way: I use Squish ofcourse but he uses gecho because I thought this
is a nice very easy starters-pack. If this is the problem then I can make
sure he uses squish to but I don't thing the problem is at his side. Or it
must be that GEcho doesn't insert the TOPT kludge when he makes a message
to a node with point number 0. But as far as I know Squish doesn't this
either.
Greetings, //PGPServer running -2CD069ED-
Jan Hugo Prins //Internet: jhaprins{at}etc.cybercomm.nl
---
* Origin: King Aragorn Says goodbye (2:283/312.18)SEEN-BY: 13/13 37/100 50/99 90/90 102/735 103/2 104/821 105/103 330 107/411 SEEN-BY: 119/88 129/11 138/146 147/135 153/800 920 157/586 161/55 167/90 SEEN-BY: 200/204 201/505 203/992 204/200 206/2711 209/720 233/7 234/100 SEEN-BY: 245/6910 249/99 100 104 106 112 125 139 200 201 254/1 260/10 801 SEEN-BY: 261/1137 267/200 270/101 102 103 104 211 273/909 278/304 280/1 801 SEEN-BY: 282/1 283/121 657 292/876 320/119 321/1 332/1 341/70 344/3 348/105 SEEN-BY: 355/2 362/37 369/110 385/100 387/31 396/1 600/253 348 641 620/243 SEEN-BY: 623/630 625/100 626/660 632/348 640/205 206 230 297 305 702 820 821 SEEN-BY: 640/822 823 649/312 690/660 700/101 711/409 413 430 808 809 934 949 SEEN-BY: 711/955 712/515 713/888 714/906 724/10 750/2 800/1 2250/50 2430/1423 SEEN-BY: 2433/225 2604/104 2613/5 2615/20 2624/306 3401/308 3412/1 3550/500 SEEN-BY: 3615/7 3619/25 3637/1 3805/3 7104/2 7107/9 @PATH: 283/35 1 512 280/801 270/101 249/100 99 106 640/206 820 711/409 808 @PATH: 711/934 |
|
| 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™.