Hello Allen,

On 17 Nov 16 23:31, Allen Prunty wrote to Nicholas Boel:

 NB>> Very true. I was simply pointing out that we can't blame Mystic
 NB>> for this one. Since it was the first and only software you
 NB>> mentioned on this thread. :)

 AP> If you read my messages in the threads I initially didn't until Paul
 AP> Hayton figured out it's modifying mail passing through it... The thing
 AP> we have to do now is look at the pathways of any :00 messages and take
 AP> the time to see what tosser each node is using and try to track where
 AP> they are getting mungeled.

While this may still be on topic from our discussion in another echo, these
specific dupes (actually there was only one) pointed out by Wilfred in this
echo have been verified to NOT pass through a Mystic system in the path they
took to get to Wilfred. In other words, there is yet another software (besides
Mystic) that is changing timestamps. Whether or not seconds are being dropped
from the modified timestamp has not been verified, as the one that arrived on
Wilfred's system could indeed have just been processed on the 00 seconds of
said minute/hour.

 AP> I'm really committed to help in what capacity I can.  Here's the dups
 AP> that I caught of yours Nicholas.  This is the -last- of many dup
 AP> checks that happen when mail is recvied by Winserver.  The server
 AP> itself will check the Echotag / From/to/sub/date and msgid to
 AP> determine a dup.  if it all matches it stops it. But by changing the
 AP> date by one second it's read as a new message even if the msgid is the
 AP> same.

The only reason you're getting dupes from my system is because we are connected
to many of the same Fidoweb systems. This is normal operation of the Fidoweb
model. I receive many dupes here from your system as well. It all depends on
the path it takes to get here. They are being caught as dupes, which is exactly
what we want to happen.

The original message by Joseph had an original broken timestamp of "Jan 31
1980" or some such (forgive me if I'm off by a little bit on the date, as I'm
in an external editor right now and can't look back at the message, either
way.. the month and year is spot on). It passed through my system with the same
date (which also made me realize I don't have the -tooOld switch set in my
config.. but hell, we wouldn't have seen this error if I did have it set). It
passed through a few other systems and by the time it got to Wilfred it
actually had a valid timestamp. So some non-Mystic system out there also seems
to be correcting bad times.

I do know both Tommi and Bob have pretty extensive setups, with netmail
trackers and whatnot. I wonder if either one of them are running that pktdate
program to fix timestamps of messages. That is the only thing I can think of.

 AP> Mystic has another proven bug that everyone is well aware of that has
 AP> not really caused much of a problem since no one hardly ever uses
 AP> offline mail anymore.  It's QWK door uses the same MSGID on all .rep
 AP> packet uploaded messages on every BBS.  It's a static MSGID.  But the
 AP> date/time/subject from/two are differen so my system lets it in as a
 AP> unique message.

Thanks for the heads up, although this specific case does not seem to be a
Mystic issue.

 AP> I hope this is helpful If I can loop some packets through my system so
 AP> you can see what they are doing let me know I'll create a binkd
 AP> account for you and set you up.  Let's find a solution to this... and
 AP> cooperate.

 AP> ! ECHO: WCServer AddMessage Error (2000001D) DUPLICATE_RECORD
 AP>  -    PKT MSG# : 1
 AP>  -    ECHO TAG : FIDOTEST
 AP>  -    FROMWHOM : Nicholas Boel
 AP>  -    TOWHOM   : Ignatius
 AP>  -    SUBJECT  : Re: Testing date stamp.
 AP>  -    DATE     : 17 Nov 16  21:13:02
 AP>  -    MSGID    : 1:154/10 582e71d5
 AP> ! ECHO: WCServer AddMessage Error (2000001D) DUPLICATE_RECORD
 AP>  -    PKT MSG# : 2
 AP>  -    ECHO TAG : FIDOTEST
 AP>  -    FROMWHOM : Nicholas Boel
 AP>  -    TOWHOM   : Ignatius
 AP>  -    SUBJECT  : Re: Testing date stamp.
 AP>  -    DATE     : 17 Nov 16  21:13:26
 AP>  -    MSGID    : 1:154/10 582e71ef
 AP> --- Platinum Xpress/Win/WINServer v3.0pr5
 AP> (1:2320/100)
 AP> SEEN-BY: 109/500 116/116 120/544 123/5 52 111 140 400 500 789 1970
 AP> 6502
 AP> SEEN-BY: 124/5013 5014 129/215 135/300 140/1 142/799 153/757 154/10 30
 AP> 700
 AP> SEEN-BY: 203/0 221/6 226/600 227/201 229/310 426 261/38 280/464
 AP> 320/119
 AP> SEEN-BY: 322/759 340/800 342/11 806 2320/100 3634/12
 AP> @PATH: 2320/100 123/500 154/10

Again, this is normal Fidoweb operation. You probably received my first message
from Björn or Wilfred, and the second one came via the path of Ross (whichever
is slower to get to you at the time). I see these all the time as well, but
they are not "bad" messages. Just normal fidoweb dupes. The more common links
we have to the same areas, the more dupes you will see.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20160827