| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Routing Problem |
-=> On 12-28-07 21:24, Mvan Le <=-
-=> spoke to Dale Shipp about Re: Routing Problem <=-
Thanks for the responses.
ML> The only clue I have is that Argus is a GUI mailer. So somewhere on
ML> the screen it should give details on outbound packets. So check
ML> if there's any indication that Argus actually sees pending
ML> outbound packets after they're created by Squish, which
ML> would be a good sign.
It does see them. If I log onto that machine and open up Argus, I
can see the packet sitting unsent in the outbound queue, addressed to
the node which is the ultimate recipient --- but not to the node
where the mail should go according to the ROUTE.CFG file. I can
mannually go to that outbound packet, and "readdress" it to my normal
uplink and it then goes out and is routed on its way.
I have asked in the ARGUS echo about this problem also. Somehow
either SQUISH is not seeing the routing info, or it is getting
readdressed when Argus picks it up. I've tried a number of things,
none with success yet.
Dale Shipp
fido_261_1466 (at) comcast (dot) net
(1:261/1466)
... Shipwrecked on Hesperus in Columbia, Maryland. 23:07:29, 29 Dec 2007
___ Blue Wave/DOS v2.30
--- Maximus/NT 3.01
* Origin: Owl's Anchor (1:261/1466)SEEN-BY: 10/1 3 11/201 14/300 34/999 90/1 103/105 120/228 123/500 134/10 140/1 SEEN-BY: 222/2 226/0 249/303 261/20 38 100 1381 1404 1406 1418 266/1413 SEEN-BY: 280/1027 320/119 633/104 260 262 267 690/682 734 712/848 800/432 SEEN-BY: 801/161 189 2222/700 2320/100 105 200 303 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™.