| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Interesting article for dazed and confused SysOps |
Hi Mark,
On Sat 2039-Feb-12 17:57, mark lewis (1:3634/12) wrote to Richard Webb:
RN> Although not quite the way it should. (-:[
RW> YEah, some things could be better improved, but they were
RW> starting to rear their ugly heads even back in the day with
RW> varying feed topologies, etc. Even back then getting routed
RW> netmail to/from some systems was an adventure as they almost never
RW> connected with an nc.
ml> that was one of the biggest problems and can still be today... one
ml> should, if possible, always connect with their NC specifically for
ml> routed netmail or they should make arrangements for their routed
ml> netmail that arrives at their NC's system be forwarded/delivered to
ml> another system who can provide it for them...
Indeed, and as long as those netmail routing maps such as
Ross does are updated occasionally, and accessible that can
work. tHe topology was logically designed, but the original designers
weren't taking into consideration such things as
ftp hubs, planetconnect, etc.
YOu and I have talked a few times about the adventures of
big nets where many were in state ld to their nc.
Regards,
Richard
--- timEd 1.10.y2k+
* Origin: (1:116/901)SEEN-BY: 3/0 633/267 640/954 712/0 313 550 620 848 @PATH: 116/901 3634/12 123/500 261/38 712/848 633/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™.