| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | FTS-0501 |
> I haven't changed this. I checked FTS-0004, and it has a
> space after the tearline.
ac> Yeah, but if you treat the space as part of the data then
ac> it makes sense.
ac> How about ...
ac> o ---[]
Yes!! Excellent, documents the reality clearly.
ac>> Saying it should be a 4D address is your interpretation.
ac>> Certainly a 5D address is acceptable by the vast majority
ac>> of FidoNet mail processors and readers currently being
ac>> used.
> Which 5d format? I don't know too many that will parse
> fidonet#3:711/934.9.
ac> The format listed in FTS-6, eg. 3:635/727.4{at}fidonet.
I've also seen kludges with 3/2:1^FidoNet (and to make matters worse, some
things like 3:/2/1^User_Name)
> And I can't see a reason to allow this when FTS-4 doesn't
> even allow it. BFN. Paul.
ac> That's fine. I only mentioned that for academic purposes.
Footnote Time Paul :-)
...Alex.
(Pagan & Proud)
---
ac>> * Origin: Conference Mail System (Opus 1:222/333)* Origin: Elfwhere - the POINty eared POINt (3:640/450.2379) SEEN-BY: 640/103 305 306 450 458 711/809 934 712/610 @PATH: 640/450 305 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™.