Subj : MSGID
To : All
From : Carlos Navarro
Date : Mon Apr 21 2025 11:16 am
12 Feb 2022 21:42, I wrote to "All":
CN> 03 Feb 2022 07:25, I asked:
CN>> Is there any software that has issues with messages having a
CN>> MSGID like
CN>> string@z:r/n.p serialno
CN>> ?
CN> So far I have only been told about:
CN> - SemPoint
CN> - NetMgr (*netmail only)
CN> 1. Looks like no one uses SemPoint nowadays.
CN> 2. NetMgr only has trouble with netmails. As I've been pointed out,
CN> this was reported and discussed in the TUB echo (Dec 2020). I've seen
CN> that SBBSecho was changed and currently uses 3D/4D (no "string@"
CN> prefix) in MSGIDs for netmails.
CN> So it seems that using this type of origaddr's in echomail does not
CN> break anything.
It seems that even SemPoint (at least the latest version) does not have issues when reading or replying to messages with that kind of MSGIDs. I've seen this message in the POINTS echo:
Shawn Highfield -> Dan Clough - 25 Feb 2025 17:10
@MSGID: 1:229/452 00030687
@REPLY: 1152.fido_points@1:135/115 2c237265
@PID: SemPoint 2.26
So, there is no known software that has trouble with using "string@z:n/f.p"-type origaddr's in MSGIDs in echomail.
