| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Testing.. sorry |
CL> I did a post on Carol's BBS to see if it would toss properly to me CL> and show up properly.. I apologize.. no need to apologize... there has been some crossing of traffic not intended for the 10th_amd echo that has appeared here... we're still trying to figure out where the crossover is happening and why... since you state that you specifically posted on 1:275/100 and the message appeared in 10th_amd, can you please tell what echo you actually posted that and this message to? if it is not 10th_amd, it may very well lead us to where the problem is... CL> Thanks and thank you! this is one of the few responses that i've had in this area concerning the problem... carol has responded to netmail about it but the available traffic and responses have not yet assisted in locating the problem with the apparent crossover of the posts that don't appear to be destined to the 10th_amd echo... ie: postings between a net coordinator and the regional coordinator concerning regional business... to be honest, i suspect a clash in the hash value generated for the actual echo area and this one... to explain further and to use my mail tosser as an example, when it is set to automatically create new areas, it does so by calculating a hash value of the echo area's TAG... it is possible that there is some mail tosser that is generating the same hash for 10th_amd as it does for the real destination echo area tag... since the two are the same, we end up with a cross linking of echo areas... hopefully that explains the possible root of the problem that we're hunting... )\/(ark* Origin: (1:3634/12) SEEN-BY: 3/0 633/267 712/0 313 550 620 848 @PATH: 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™.