| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | ^ASOT, ^AEOT |
ac>> 1. Why was this posted in NET_DEV? > Because I know Paul and his SOT/EOT proposal are active in this echo. Perhaps netmail would've been more appropriate. ac>> 2. You claim to be conforming to Paul's SOT/EOT proposal. If ac>> this is correct, where are the SOT/EOT kludges? > They get lost due to limitations of JAM. What 'limitations' are they? In what way are they 'lost'? Please be more specific. ac>> Also, your origin line violates Requirement 11 of the proposal. > Explain... I'll let the proposal explain itself: 11. The Origin line will contain a 4D address in brackets at the end (ie 5D is not allowed). There will be nothing except the address in the brackets. ac>> 3. The data between the brackets in your origin line does not ac>> constitute a valid network address. I believe this is in ac>> violation of FTS-4. > I've explained this to you more than once, Andrew. I mentioned this in another network. I pointed out, as above, that it may violate FTS-4. You acknowledged this, yet you have chosen to continue using it. You have not adequately explained your decision. andrew --- Msgedsq/2 3.10> * Origin: = FMail Support Australia = 053 31-8706 = (FidoNet 3:637/106) * Origin: Blizzard of Ozz, Melbourne, Australia (3:633/267.1{at}fidonet) SEEN-BY: 50/99 209/720 620/243 632/103 341 348 998 633/246 252 253 260 267 SEEN-BY: 633/371 373 634/384 635/502 503 727 639/100 640/201 206 217 305 531 SEEN-BY: 640/820 821 822 823 690/660 711/409 410 413 430 431 807 808 809 816 SEEN-BY: 711/934 712/515 713/888 800/1 7877/2809 @PATH: 633/267 252 371 635/503 632/348 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™.