TIP: Click on subject to list as thread! ANSI
echo: net_dev
to: MARK LEWIS
from: HECTOR SANTOS
date: 1996-03-06 04:48:00
subject: An political question

HS>> THATS FOR A NORMAL REPLY!!!!!!!!!!!!!!!!   You are NOT doing a
HS>> normal reply when you do a "REPLY to the OTHER GUY"

ML> bullshit, hec... a reply is a reply is a reply is a reply [ad 
ML> nausum]... if it is so different, then why do you use the term 'reply' 
ML> in your option "REPLY to the other guy" ??

For lack of a better terminology to allow the lamen to understand,
"replying to receipient" is the more proper wording.

No, its not the same thing. Do a NETMAIL CROSSPORT to the receipient of the
an echo message and see what address you come up with with your editor?

You will see how different it is.

ML> the above is an example from TimED's screen... it shows that the 
ML> current message is a reply to #142... it shows that there are two 
ML> replies to *this* current message, #153 and #158... it also shows that 
ML> there is ANOTHER reply to the _original_ message...

Which breaks with a OFF-LINE reader, any one of them, especially QWK.
Silver Xpress will support MSGID/REPLY being imported into JAM.

ML> FTS-0009 is not ambigious WRT MSGID/REPLY generation... its been being
ML> done like this for years! i know that RemoteAccess has been doing it
ML> like this ever since FTS-0009 support was implemented...

We are talking about "Replying to a receipient" of a message which is what
steering this debate.

FTS-9 is perfect when you do a normal reply to the originator of the
message. There is no question about that.

Try doing a netmail cross post with the editors you use to the "Other Guy".
See what happens.
--- Platinum Xpress/386/Wildcat! v1.2f
* Origin: Xpress Tech Support BBS * 305-248-7815 (1:135/382)
SEEN-BY: 10/8 13/13 50/99 78/0 90/90 102/735 103/2 104/821 105/103 107/411
SEEN-BY: 123/1 129/11 138/146 147/76 153/800 920 157/586 161/55 167/92
SEEN-BY: 200/204 202/1207 203/15 206/2711 209/720 218/801 239/1 245/6910
SEEN-BY: 251/12 261/1137 267/200 270/101 102 103 104 272/82 280/1 282/1 4073
SEEN-BY: 283/657 292/876 320/119 325/118 328/104 332/1 334/201 340/20 341/70
SEEN-BY: 342/12 345/12 346/49 348/105 353/211 353 362/37 367/1 369/110 380/25
SEEN-BY: 385/100 387/31 396/1 403/150 405/0 406/100 430/105 600/253 348
SEEN-BY: 620/243 626/660 632/348 640/201 206 217 305 820 821 822 823 690/660
SEEN-BY: 700/101 711/409 410 413 430 808 809 934 712/515 713/888 721/117
SEEN-BY: 724/10 800/1 2430/1423 2433/225 2490/3001 2604/104 2605/606 2613/5
SEEN-BY: 2621/100 2624/306 3401/308 3412/1114 3615/7 50 3619/25 3653/777
SEEN-BY: 3805/3 7104/2 7877/2809
@PATH: 135/382 292 992 3615/50 396/1 270/101 209/720 640/820 711/409 808 809
@PATH: 711/934

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™.