| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Fully connected to t |
Hi Dale, On 2015-05-21 23:07:00, you wrote to me: WVV>> SEEN+BY: 154/10 203/0 227/51 230/0 240/5832 249/303 261/38 280/464 WVV>> 5003 SEEN+BY: 280/5555 292/624 854 423/120 633/267 280 640/305 384 WVV>> 1384 690/682 SEEN+BY: 712/550 620 848 770/1 5020/545 @PATH: 292/854 WVV>> 123/500 320/119 203/0 640/384 712/848 280/464 DS> I don't see a problem in the Seen-bys. Ward's node is there, and so it DS> is not the sort of dupe loop he mentioned. This is how it ended up in my message base after being tossed. So of course it contains all the node numbers of my links, including Wards... But I see how this isn't helpfull, so I searched my inbound backup for the original .pkt file as it arrived here. This is what it contained: I notice the first 3 systems in the path are not in the seen-by's... Bye, Wilfred. --- FMail-W32-1.69.6.111-B20150521* Origin: FMail development HQ (2:280/464) $EEN-BY: 203/0 261/38 280/464 5555 633/267 280 640/305 384 1384 690/682 $EEN-BY: 712/550 620 848 770/1 @PATH: 292/854 123/500 320/119 203/0 640/384 712/848 |
|
| SOURCE: echomail via QWK@docsplace.org | |
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™.