| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | An political question |
hs>> Mark please, I am not going to spent more than 10 seconds hs>> on this. I saw your message twice. It may be as you say, hs>> you edited later. Whatever. ML> then why tell me to fix my software (left quoted above> ? HS> Because you LET a DUPE get out!!! if i edited it or otherwise altered its MSGID, then it is not a dupe... only two messages with identical text bodies... you have offered no evidence, hector, to the contrary... all you did was to pounce upon me with a statement and nothing to back it up... i cannot find any dupes from me to others in my message base and you have offered no assistance other than telling me that YOU received a 'dupe' and to fix my software... maybe someone upstream from you had to retoss the PKT that that message was in? HS> As far as arugments is concern, I know I am RIGHT. and you KNOW I am HS> right. You can't admit it. You don't want to ADMIT it that you ARE HS> advocating the generation of BAD addressing into the NET. I can't HS> say that you are actually responsible because you don't author any HS> software, but you are telling "potential authors" reading this echo, HS> how to create illogical software. you may be 'right' as far as addressing is conerned but you are DEFINITELY =WRONG= when it comes to using FTS-0009 for addressing... you are also wrong about me not authoring any software... you don't know what i have out there ;) HS> I repeat: HS> I AM NOT SPITTING OUT BAD ADDRESSES INTO THE NET FOR THE NEXT HS> GUY TO SCREW UP WITH. then what FIDONET standard or proposal are you (going) to use for this?? FTS-0009 =PLAINLY= states what it is for... Message Identification and Message Linking... nothing else... HS> So along as that is the CASE, you and "your FRIENDS" can kiss my HS> ass, and be OVERWHELMING WRONG all you want. I will clearly make HS> sure that when a SYSOP bitches about mail being addressed wrong, I HS> will remind him to look at the possibility that his user replied to HS> a message created by one of of Mark's friends email software which HS> screwed up the addressing in the system. do what you want to, hector... you always do... however, i suggext that you also make them aware of what the standard you are butchering really says... if you don't, others will and once again, your software will come out looking on the bad side of things... you still haven't corrected your software to stop violating FSC-0046 and that's been over a year ago that you were specifically notified... HS> Hey, atleast YOU now know the same thing and will be able to address HS> it as well. If you DON'T, then you are hiding behind the truth. i'm not going to alter the way any of my software uses FTS-0009. HS> Preach putting bad addressing all you want. I will not be part of HS> it. HS> How far you do you want to take this Mark? the question is how far do you want to take it... you are wrong in your use of FTS-0009 and you are trying to justify it with this addressing argument... i suppose you tell the policeman that you are hungry and that that gives you the right to exceed the speed limit while going home, eh? it's the same argument... )\/(ark* Origin: (1:3634/12) SEEN-BY: 10/8 13/13 37/100 50/99 78/0 90/90 102/735 103/2 104/821 105/103 SEEN-BY: 107/411 123/1 129/11 138/146 153/800 920 157/586 161/55 167/92 SEEN-BY: 200/204 202/1207 203/15 512 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 801 282/1 SEEN-BY: 282/4073 283/657 292/876 320/119 325/118 328/104 332/1 334/201 SEEN-BY: 340/20 341/70 342/12 344/3 345/12 346/49 348/105 353/211 353 362/37 SEEN-BY: 367/1 369/110 380/25 385/100 387/31 396/1 403/150 405/0 406/100 SEEN-BY: 430/105 600/253 348 620/243 626/660 632/348 640/201 206 217 305 820 SEEN-BY: 640/821 822 823 690/660 700/101 711/409 410 413 430 808 809 934 SEEN-BY: 712/515 713/888 721/117 724/10 800/1 2430/1423 2433/225 2490/3001 SEEN-BY: 2604/104 2605/606 2613/5 2621/100 2624/306 3401/308 3412/1114 3615/7 SEEN-BY: 3615/50 3619/25 3653/777 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™.