| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | 1-- 35 - 70 |
DC> Now to figure out why message threading works but does DC> not get passed back to other systems! if you are talking about MSGID/REPLY threading, that depends on several factors... the last of which is the BBS mail door software... its well known that wildcat stuff doesn't generate REPLY lines but does generate MSGID lines... i participated in that "discussion" with hector santos and many others several times quite a few years ago... his stance was that the spec was ambiguous on somethings and no one was able to get him to see the light... things like "originating system" were misconstrued to possibly mean "enduser's system"... totally lost was the fact that this was a fidonet spec written for fidonet and that the fidonet system was the system being specified... that was at least one of the "arguments" made... many of us just wish that he had followed along with what everyone else was doing and didn't implement the halfassed portion that he did... i can't recall directly or locate the messages in my archives but it seems to me that he did the current implementation on purpose to show how things were messed up and to try to force a change in the spec to get it better clarified or some such... )\/(ark* Origin: (1:3634/12) SEEN-BY: 633/267 270 @PATH: 3634/12 106/2000 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™.