MSGID: 1:19/40 2DCB0C0B
PID: CyberBBS v1.0.10
Hi,
I just had a question about the MSGID used by Synchronet. Can you explain how sbbs creates the MSGID kludge?
MSGID: 1:19/40 182A4278
PID: CyberBBS v1.0.10
Thank you! I agree with your article and was actually wondering how
the MSGID 8 Char serial could even be assured to be unique with all of
the echomail floating around.
MSGID: 1:19/40 31718125
PID: CyberBBS v1.0.10
That's true. I wrote a routine that parsed your msgid before I knew what
it was composed of.
But, now that I know how you create it, I plan
on also creating my MSGIDs a very similar way.
MSGID: 1:19/40 0FFE4D11
PID: CyberBBS v1.0.10
Do you write the REPLY kludge the same was as the BBS ID or the traditional way as onlined in FTSC?
MSGID: 1:19/40 1C438055
PID: CyberBBS v1.0.10
Yea, I somehow removed the chr(1) character to the kludge. My next build will x that. I should clarify, I parsed msgid to obtain the node the msg came
from. Thats more for my own display in the bbs. Still a work in progress.
Thank you! I agree with your article and was actually wondering how
the MSGID 8 Char serial could even be assured to be unique with all of
the echomail floating around.
That's true. I wrote a routine that parsed your msgid before I knew
what it was composed of. But, now that I know how you create it, I
plan on also creating my MSGIDs a very similar way.
Something like:
msg_num.conf_identifier@node
Hi Chad,
On 2023-03-02 12:26:54, you wrote to Digital Man:
Thank you! I agree with your article and was actually wondering how
the MSGID 8 Char serial could even be assured to be unique with all of the echomail floating around.
To be precise: The combination of the 8 char serialno _plus_ the origaddr need to be unique! So since the originating system is in control of generating it, uniqueness can be assured!
Sysop: | Retros |
---|---|
Location: | Toronto, Canada |
Users: | 23 |
Nodes: | 8 (0 / 8) |
Uptime: | 143:30:48 |
Calls: | 1,087 |
Files: | 6 |
Messages: | 29,843 |