Some crap messages generated in this echo at 2:221/360 due to
husky/sqpack crash. However, sqpack should have not run in this echo,
but due to the bug in husky/sqpack it was run.
Some crap messages generated in this echo at 2:221/360 due to
husky/sqpack crash. However, sqpack should have not run in this
echo, but due to the bug in husky/sqpack it was run.
Thanks for testing my tosser:
20:22:13.266 Processing jam area: WINDOWS
20:22:13.268 *** Encountered a problem during JAM base maintenance,
area WINDOWS
20:22:13.268 Updating reply chains: End
I've never seen that last error before.
I think there is room for improvement. Like not keep on tossing the contents of a pkt file when garbage is encountered... ;-)
--- FMail-lnx64 2.3.0.1-B20240319
I think there is room for improvement. Like not keep on
tossing the contents of a pkt file when garbage is
encountered... ;-)
Some AI needed to detect "crap" ;-)
I think there is room for improvement. Like not keep on
tossing the contents of a pkt file when garbage is
encountered... ;-)
Some AI needed to detect "crap" ;-)
Or.. simply not toss a pkt if at least the msg header is
malformed?
...
20:22:13.266 Processing jam area: WINDOWS
20:22:13.268 *** Encountered a problem during JAM base maintenance,
area WINDOWS
20:22:13.268 Updating reply chains: End
I've never seen that last error before.
Or.. simply not toss a pkt if at least the msg header is
malformed?
Yes. But some intelligence needed to detect garbage. :)
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 32:22:55 |
Calls: | 141 |
Files: | 5,058 |
Messages: | 220,694 |