| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | talking to myself |
ml>> in what way is the SBBS MSGID flawed??
MK> Have you looked at them? I don't have one handy but basically
MK> it looks like the following;
MK> {at}MSGID: 1:3634/12{at}fidonet 188f2e98 1:3634/12{at}fidonet 188F2E98
actually, here's one from this very echo...
{at}MSGID: 75.fido_perl{at}1:3613/47 06776802
MK> I am not sure I got that EXACTLY right but that is a close
MK> enough approximation. I just cut the above one from your
MK> message and editted it accordingly to what I recall about SBBS
MK> MSGID specs.
i still, see nothing wrong with it... the specs state that the first part
is to be the address of the originating system... i'm not sure about the
"75" but fido_perl{at}1:3613/47 is more definitive as it points to
the actual message base on that system...
basically, the term "address" is somewhat ambiguous... many have
argued that it means FTN addresses only... others have argued that it is
not that restrictive and that i'net style addresses are also ok as well as
PCRelay/RIME addresses and even WWIVnet addresses...
)\/(ark
* Origin: (1:3634/12)SEEN-BY: 633/267 270 @PATH: 3634/12 106/2000 633/267 |
|
| 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™.