| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | fsc-xxxx.000 |
MS> The way I read it, this proposal isn't compatible with the way in MS> which messages are currently stored. I mean if I generate the SOT MS> and EOT but shove 'wrong' stuff inbetween like origin and SEEN+BY MS> lines, then mail processors will barf on it. Doesn't every editor MS> and mail processor have to generate the SOT and EOT before it can MS> actually be used? PE> Well that is an existing problem which has to be lived with. With PE> SOT/EOT you can at least be sure that if you start at the bottom, PE> and work your way up, your algorithm is mostly secure. Umm, Paul, just how is that any different the use of MSGID without utter certainty about no reuse in 3years ? |-) --- PQWK202* Origin: afswlw rjfilepwq (3:711/934.2) SEEN-BY: 690/718 711/809 934 @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™.