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: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 1,048 |
Nodes: | 10 (0 / 10) |
Uptime: | 46:39:56 |
Calls: | 13,564 |
Calls today: | 1 |
Files: | 186,856 |
D/L today: |
2,600 files (866M bytes) |
Messages: | 3,398,468 |
Posted today: | 1 |