It seems to be a problem for WinPoint when building a
reply message. The REPLYID seems to result in 00000000.
So that is the first discovered problem. There are probably more. And
probably harder to discover...
I may have to spin up my Winpoint to see for myself. But apparently Winpoint is getting new life in development and the
uber msgid could be accomodated. :D
AREA:ASIAN_LINK
@RESCANNED 2:240/1120
@REPLY: 2:221/1.58@fidonet ef616eac
@MSGID: 1:153/7001 sTW6u3OA
@CHRS: UTF-8 4
-={ 2021-04-13 21:15:41.032014984+00:00 }=-
Test reply to see if WP now handles those invalid MSGID values
nicer ;)
Sysop: | StingRay |
---|---|
Location: | Woodstock, GA |
Users: | 63 |
Nodes: | 15 (0 / 15) |
Uptime: | 67:16:51 |
Calls: | 762 |
Calls today: | 4 |
Files: | 1,194 |
D/L today: |
7 files (1,846K bytes) |
Messages: | 248,615 |