| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Unpacking insecure arcmail |
Hi Mark! Mar 17 07:10 2015, mark lewis wrote to Markus Reschke: MR>> What is the correct term for the process of echomail leaving a node MR>> in one zone and entering a node in another zone? ml> it isn't zone gating... there is no term for it unless the echomail ml->agoranet) which is ml> plain simple gating as far as i can remember right now at 0700 with ml> no c0ffee... echomail crossing between zones in the same FTN is ml> simply echomail crossing between zones... there's nothing special ml> about it... It seems that I'm not the only one talking about echomail zone gating ;) FSC-0093 (Reduced seen-by lines): PATH considerations ------------------- There are 2 problems with the PATH kludge as specified in FTS-0004: First like in the FSB the addresses in the PATH are 2D, and having the same 2D address in different zones is possible. Therefore zone gates are required to use the TSB algorithm. FSC-0068 (A Proposed Replacement For FTS-0004): Current practice is to strip SEEN-BYs at zone and domain gates since their 2-D nature make them useless for duplicate message checking beyond a given zone. The hpt documentation has a section about zone gating under "4 Advanced Concepts in HPT". Just saying :) Regards, Markus ---* Origin: *** theca tabellaria *** (2:240/1661) SEEN-BY: 11/201 34/999 90/1 116/18 120/331 123/500 1406 128/187 135/364 140/1 SEEN-BY: 218/700 222/2 226/0 160 230/150 240/1120 249/303 250/1 261/38 100 SEEN-BY: 266/404 1413 267/155 280/464 1027 282/1031 1056 292/907 908 311/2 SEEN-BY: 320/119 340/400 393/68 396/45 633/267 280 640/384 712/101 550 848 SEEN-BY: 770/1 801/161 @PATH: 240/1661 1120 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™.