From HECTOR SANTOS · 1996-03-31 23:48 · #72995 in FREE25
In reply to An political question by HECTOR SANTOS
TOPIC: FTS-9 After further checking with Silver Xpress, you are right. It is not doing it as "I intended" for ECHO MAIL responses. It is however, doing exactly what I am saying for cross posted NETMAIL responses. This was an oversight and will be correcting SX to make do exactly what it suppose to be doing and that is NOT spit out bad addresses. That is the bottom line. However, I will add internal options to use the OLD style for the FTS-9 thread chaining prundits. Sure, my heritage is spanish (cuban) but there is no excuse for my english. I was borned here, I am american, highly corporate trained professional and engineer. My problem is I don't double check my writings most of the time. Pure and Simple. Due to the volume of mail I write, I normally go with the first draft of whatever I write. I am a fast typer, fast thinker and sometimes my neurons are WAY ahead of my typing :-) As far the SX documentation, the semantics of "original author" has been played out with SX supporters. That is what people understand. But you're right, it needs to be clearer. As far as the tear line, as I said, the action I took was in direct response to GECHO and others starting to tamper with mail to "HIGHLIGHT" the problems of email tampering. You know that is the case. The fact that I began to do it ONLY for the END-USER, the READER was to a) lessen the impact, and b) not effect the network whatsoever while at the same time, illustrate the problem. Although, this did indeed brought on many discussions over the years, it only serve one thing - to show no really cares and that people were going to HIDE from strippers simply by using fake tear lines. It was unfortunate that the majority of discussions were with ME and end-users (users and sysops) and not ME and DEVELOPERS or DEVELOPERS and end-users. Sysops just love the idea of having some "control" over the tear line. I admitted that it was a wrong approach because in the end result, people only understood what they saw, not the reasons for it. I also admitted that two wrongs do not make a right. I also admitted that it was a mistake to use USERS to try to illustrate the problem. Ironically, when that didn't work, and I went to the MAIL DOOR. I expected a bigger impact but that turned out to be more ACCEPTABLE by the sysop community. It was a very strange behavior and my sales increased. Very strange. So in summary, I apologize for not seeing that SX was NOT doing correctly and I thank you for pointing it out. I havn't been using the SX reader lately and when all this came out, I knew I was using the REPLY for addressing so it was definitely an oversight that I didn't carry it over in the ECHOS as well. My point remains. ADDRESSING is more important given the LACK of ADDRESSING in the mail headers for the majority of BBSes. It is important that we use the BEST currently available mechanism (FTS-9) to satisfy this need when it WORKS nearly 99% of the time except for a "FOLLOW UP" concept. There is no need to introduce another KLUDGE just for this and there is no reason to introduce BAD addressing just for threading. We already have it. I will be making the correction to SX and in addition, add logic to PX sysop editor to handle "follow up" mail. Hector Santos/Santronics Software ... Silver Xpress....Pioneering Off-line Mail Technology! --- Via Silver Xpress V4.3dP [Reg] * Origin: Xpress Tech Support BBS * 305-248-7815 (1:135/382)