TIP: Click on subject to list as thread! ANSI
echo: net_dev
to: HECTOR SANTOS
from: mark lewis
date: 1996-03-10 11:04:44
subject: An political question

ML> proper usage of those control lines is what is better... you are trying
ML> to use them for something that they are NOT DESIGNED to do...

HS> You are completely NOT making any sense whatsoever.  Your
HS> intepretation simply without a DOUBT breaks the addressing sequence

i am not intrepreting anything in FTS-0009 ... you are and you are doing
it erroneously... the spec says that the REPLY line is an exact copy of
the MSGID line that the message is a reply to...

HS> and with that ILL logic of not properly using the REPLY, the NEXT
HS> guy in the system reading the MAIL loses the functionality of
HS> contacting either person.   Hey the fact is, NO ONE uses threads and
HS> ADDRESSING is more important.  We can't go back to the FIRST message
HS> of this thread using the REPLY/MSGID system even if you wanted too.

another two incorrect assumptions...

 1. many people use true threading via MSGID lines... JAM is only one...
    SQUISH can, TBBS does, almost all internet news readers... what more
    do you want?

 2. =*I*= can go back to the FIRST message of this thread using the
    MSGID/REPLY linking... the only thing stopping me at this time is
    that i only hold 10000 messages max or 30 days max in this base... i
    went back to _this_ message quite easily...

=====
Date : Thu Feb 08, 16:11      >8287 8318 (8330)
From : Mats Wallin                                2:270/19.11
To   : HECTOR SANTOS
Subj : An political question
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
 hs> Who said making a netmail reply was a mandatory feature? That
 hs> is why the MSGID and REPLYID is used.  With our reader, you
 hs> can do:

 hs>     Netmail Reply to Receipient:  (Check for REPLYID)

The REPLYID does _not_ contain the address of the recipient of a message. It
does only contain the address of the sender of another message.

In many cases, this just happens to be the same person, but there is not a
guarantee that this is true. Just check the next message for instance.

        Mats
        mw{at}findata.se

___
 - Origin: Absolute APX (2:270/19.11)
=====

HS> But if I wanted to do a netmail reply to either party, I can do it. 
HS> SX will do it correct 100%. But thats only TRUE until you do a
HS> FOLLOW UP with this ILL logic of yours. At reach point, all NORMAL
HS> REPLIES will be completely off and eventually, the addressing will
HS> be the same! 

HS> You guys are doing it all wrong.

no... you are interpreting when you are supposed to be reading... the
FTSC made the statement a long time ago that the removed the
'addressing' part from FTS-0009 before they accepted it... READ the
spec... do NOT interpret it... if you can't do that, write your own...
but please DO NOT break existing (and proper) implementations of the
spec...

)\/(ark

* Origin: (1:3634/12)
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 344/3 345/12 346/49 348/105 353/353 362/37 367/1 369/110
SEEN-BY: 380/25 385/100 387/31 396/1 403/150 405/0 406/100 430/105 600/253
SEEN-BY: 600/348 620/243 626/660 632/348 640/201 206 217 305 820 821 822 823
SEEN-BY: 690/660 700/101 711/409 410 413 430 808 809 934 712/515 713/888
SEEN-BY: 721/117 724/10 800/1 2430/1423 2433/225 2490/3001 2604/104 2605/606
SEEN-BY: 2613/5 2621/100 2624/306 3401/308 3412/1114 3615/7 50 3619/25
SEEN-BY: 3653/777 3805/3 7104/2 7877/2809
@PATH: 3634/12 170/400 396/1 270/101 209/720 640/820 711/409 808 809 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™.