Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 133  |
|  Wilfred van Velzen to Oliver Thuns  |
|  Re: Squish on Linux (compile errors)  |
|  21 Nov 19 20:44:25  |
 TID: FMail-lnx64 2.1.0.18-B20170815 RFC-X-No-Archive: Yes TZUTC: 0100 CHRS: UTF-8 2 PID: GED+LNX 1.1.5-b20161221 MSGID: 2:280/464 5dd6ea30 REPLY: 2:280/464.47@fidonet 5dd6d92d Hi Oliver, On 2019-11-21 18:23:14, you wrote to Alan Ianson: OT> There was problem with rescanned echoareas I received from my uplink. OT> Because todays computers and drives are so much faster, all .pkt files OT> had the same timestamp. Squish tries to toss .pkt files OT> chronologically, but fails misserably in that case and tosses the .pkt OT> files in random order. There's also the problem that the squish message base stores date/time stamps with a resolution of 2 seconds. That has been causing problems in the past where a squish system forwarded messages to its other links with the date/times changed from the original, and so causing undetected dupes on some systems. This is of course only a problem if you have more than 1 link to an echomail area. Which is never (or shouldn't) be the case for a point system. ;) Bye, Wilfred. --- FMail-lnx64 2.1.0.18-B20170815 * Origin: FMail development HQ (2:280/464) SEEN-BY: 1/123 15/2 18/200 90/1 103/705 203/0 221/0 227/114 229/354 SEEN-BY: 229/426 452 1014 240/5832 249/206 317 400 280/464 5003 292/854 SEEN-BY: 317/3 322/757 342/200 396/45 423/120 633/280 712/848 770/1 SEEN-BY: 2452/250 PATH: 280/464 229/426 |
[ << oldest | < older | list | newer > | newest >> ]