Subj : rescan
To   : deon
From : Oli
Date : Tue Mar 16 2021 10:07 am

deon wrote (2021-03-15):

 d>    Re: rescan
 d>    By: Oli to deon on Mon Mar 15 2021 11:46 am

 Ol>> It seems Mystic does not like the modified time of the rescanned
 Ol>> messages when it comes to dupe checking. Or is there another
 Ol>> explanation why I only received odd-second dupes?

 d> Hmm... Good question.

 d> So lets recap, so we are on the same page.

 d> * 2/1202 rescanned from 1/100 - I'm assuming it got 365 days worth of
 d> some messages (based on the age that my BBS discarded them). Although the
 d> numbers are low for a years worth, so some were stopped before they got
 d> to 2/116 and 3/100.

 d> * 2/1202 sent (some of) them to 2/100

Or all of them. My theory: 2/100 detected all messages with the correct and original time as dupes and forwarded the ones with the modified time. Which means all messages that had originally odd seconds in the datetime header field went through.

Do we know how Mystic's dupe detection work?

 d> * 2/116 received them (from 2/100) and discarded them:
 d> 2021-03-14 14:44:30 Duplicate:   84 detected in FSX_GEN
 d> 2021-03-14 14:44:30 Duplicate:   44 detected in FSX_MYS
 d> 2021-03-14 14:44:30 Duplicate:   28 detected in FSX_BBS
 d> 2021-03-14 14:44:30 Duplicate:    4 detected in FSX_ENG
 d> 2021-03-14 14:44:30 Duplicate:   78 detected in FSX_BOT
 d> 2021-03-14 14:44:30 Duplicate:  198 detected in FSX_DAT
 d> 2021-03-14 14:44:30 Duplicate:   54 detected in FSX_NET

 d> 490 messages. (none were imported).
 d> 1456 discarded due to age. (total 1946).

 d> * 3/100 received them (from 2/100), threw some into dupes and sent the
 d> rest on 4 14:44:19  Areas summary:
 d> 4 14:44:19  dupe area dupe - 447 msgs
 d> 4 14:44:19  echo area FSX_MYS - 254 msgs
 d> 4 14:44:19  echo area FSX_BBS - 224 msgs
 d> 4 14:44:19  echo area FSX_ENG - 96 msgs
 d> 4 14:44:19  echo area FSX_CRY - 257 msgs
 d> 4 14:44:19  echo area FSX_NET - 232 msgs

 d> 1510 messages. 1063 passed on.

 d> So based on what I know about the hpt jam/squish bug - rescans change the
 d> time - to an odd time? Hence why you got odd messages (since they all
 d> originated from 1/100).

It's processed internally as DOS time, which only has 2-second resolution. This is equivalent to set the least significant bit of a unix time to 0. The dupes I received had an even number of seconds, but when I compare them to the ones I originally received and have still in my message base, I see odd seconds.

modified message received as dupe:  20:05:22
in message base received last year: 20:05:23

I haven't checked every single dupe message, but I couldn't find any message with even seconds in my message base (from the ones I received as dupe). But I might be missing something.

---
 * Origin: . (21:3/102)

.