Subj : Re: Crap
To   : Tommi Koivula
From : Wilfred van Velzen
Date : Sat Mar 23 2024 12:18:54

Hi Tommi,

On 2024-03-23 12:51:48, you wrote to All:

 TK> Some crap messages generated in this echo at 2:221/360 due to
 TK> husky/sqpack crash. However, sqpack should have not run in this echo,
 TK> but due to the bug in husky/sqpack it was run.

Thanks for testing my tosser:

------------  Fri 2024-03-22, FMail-lnx64-2.3.0.1-Beta20240319
20:21:12.541  Toss
20:21:12.544  Processing 6b0c7778.pkt from 2:221/0 to 2:280/464
20:21:12.544  Pkt info: HPT 1.9, Type 2+, 1620, 2024-03-22 20:20:44, Pwd, Sec
20:21:12.544  Skipping garbage in PKT file...
20:21:12.548  Skipping garbage in PKT file...
....
20:21:12.582  Netmail: 0,  Personal: 0,  Hudson: 1,  JAMbase: 1
20:21:12.582  Msgbase net: 0, echo: 1, dup: 0, bad: 1


------------  Fri 2024-03-22, FMail-lnx64-2.3.0.1-Beta20240319
20:22:13.235  Toss
20:22:13.239  Processing 6b0c7781.pkt from 2:221/0 to 2:280/464
20:22:13.239  Pkt info: HPT 1.9, Type 2+, 1320, 2024-03-22 20:22:02, Pwd, Sec
....
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... ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.0.1-B20240319
 * Origin: FMail development HQ (2:280/464)

.