MSGID: 2:280/464.47 6007e760
PID: JamNNTPd/Linux 1
CHRS: LATIN-1 2
TZUTC: 0100
TID: CrashMail II/Linux 1.7
Is there a known bug with the SQUISH LINK command? Message linking doesn't
work properly on my Linux armv7 build. It seems to link every message to the
previous and the next, but only if there is a REPLY kludge. Looks like this in
Golded:

Umsgid         : 2





























                                                                              
#
Reply          : 2





























                                                                              
#
See            : 22, 0, 0, 0, 0, 0, 0, 0, 0

And this happens when I run "squish link":

[...]
Linking areas:

Linking area BINKD                           0x340L25k 0---- 25---
Linking area FIDONEWS                              0x245k 0-------
Linking area FIDOSOFT.HUSKY                           - L0x2 0----
Linking area FILE_ANNOUNCE_AMY                        - L0xc 0----
Linking area FSX_BBS                                  - L0xb 0----
Linking area FSX_GEN                   0x535 50L25k 0----e50 25---
Linking area FSX_HAM                                  - L0x2 0----
Linking area FSX_MYS                                  - L0xe 0----
Linking area FSX_NET                                  - L0x7 0----
Linking area MYSTIC                                   - L0xb 0----
Linking area SYNCHRONET                      0x380L25k 0---- 25---
[...]

Any ideas? Does this happen on DOS, OS/2 or Windows too or is it a Linux
specific bug?

---
 * Origin: this message must NOT be gated to Telegram (2:280/464.47)
SEEN-BY: 1/123 18/200 90/1 105/81 120/340 123/131 124/5016 129/305
SEEN-BY: 203/0 221/0 226/30 227/114 702 229/101 424 426 550 664 1016
SEEN-BY: 229/1017 240/2100 5138 5411 5832 5853 249/206 317 400 280/464
SEEN-BY: 280/5003 292/854 8125 317/3 322/757 342/200 396/45 633/280
SEEN-BY: 2432/390 2454/119
PATH: 280/464 240/5832 229/426