Why don't you give us YOUR example of what FTS-0009's "^AMSGID:
Take a look at your own for an example:
@MSGID: 2:221/1.58@fidonet e53bb3cb
origadr is a 3d/4d/5d Fidonet address.
Why don't you give us YOUR example of what FTS-0009's "^AMSGID:
Take a look at your own for an example:Sweet. That's what I thought. But I think Rob Swindell's approach introduces better uniqueness, which is the whole point of the matter.
@MSGID: 2:221/1.58@fidonet e53bb3cb
origadr is a 3d/4d/5d Fidonet address.
If 3d/4d/5d was the expectation, then the fts doc should have stated exactly that.
I understand why he did it. But it still is not standards
conform. [...] but it definitely is not standards conform.
If 3d/4d/5d was the expectation, then the fts doc should have
stated exactly that.
They stated originating addr. (Address does not include Name in
Fido) OK: 2:2/2 2:2/2.2 2:2/2.2@fidonet
NOK: name@2:2/2 name@2:2/2@fidonet
They stated originating addr. (Address does not include Name in
Fido) OK: 2:2/2 2:2/2.2 2:2/2.2@fidonet
NOK: name@2:2/2 name@2:2/2@fidonet
GREAT. More confusion for the masses. In internet usage, an address is
a complete name@whatever.tld. But in fidonet it's just the numbers.
This whole argument could have been laid to rest by saying that
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 370 |
Nodes: | 16 (2 / 14) |
Uptime: | 126:20:26 |
Calls: | 7,905 |
Calls today: | 1 |
Files: | 12,972 |
Messages: | 5,792,852 |