TIP: Click on subject to list as thread! ANSI
echo: fidosoft.husky
to: Alan Ianson
from: mark lewis
date: 2016-08-15 07:40:00
subject: Dupebasetype

14 Aug 16 17:24, you wrote to me:

 AI>>> I'm getting dupes in my dupes are that are caused by duplicate
 AI>>> msgid's. The message content is different though, so I wonder if I
 AI>>> need to add any keywords to my config so that hpt will use both
 AI>>> msged and the crc of the message.

 ml>> if

 ml>>   1. the MSGID is the same but the content is different
 ml>>   2. they're all coming from the same system
 ml>>   3. they're all within a three year period

 ml>> then

 ml>>   the system posting them is using flawed software...

 AI> Yes, it is Mystic.

ouch :(

 AI>  James just added MSGID support when posting via QWK but
 AI> it seems to be using the same MSGID more than once.

why doesn't he use the same MSGID routine already being used by the rest of the
 system?? that's been working just fine for a while, hasn't it? oh but wait...
importing QWK posts is like posting a lot of text files as messages... yeah, i
can see how it may be that he's generating the same serial number in such a
short time... especially if he's relying only on clock time and not also having
 a number that's incremented serially and stored in a data file so that other
parts of the system can get the last number used before they increment it for
their post...

 AI> I think we can solve that if indeed that is what is happening.. I'm
 AI> try to get as much good info about what is happening and pass it on to
 AI> him.

i think i shared some MSGID code with him some time back... it is what i use
here in my utilities and allows for something like 8000 messages per node per
day... it ws live tested for three years to ensure that it didn't generate
dupes within that three year period like the spec calls for...

 ml>> there's little you can do to correct it... passing them on to other
 ml>> systems will cause those other systems the same problem you are
 ml>> seeing... the best thing to do is to let the originating system know
 mltm> ;)

 AI> Yes, we want that problem solved and I'll pass on what I see to James.

hehehe...

 AI> But I am thinking that hpt should not consider those msgs as dupes
 AI> because the content is different in all those msgs?

no... not when the MSGID is used as the dupe detector... better would be to not
 have a MSGID at all instead of having duplicates...

 AI> In the case of those mails I am a leaf node.. so no harm done. But...

not yet but consider what happens if your feed needs to do a rescan from you to
 rebuild their system... feeds are two way and your feed has areafix access on
your system the same way you have areafix access on theirs ;)

)\/(ark

Always Mount a Scratch Monkey

... We are everywhere!  Unfortunately, so are they.
---
* Origin: (1:3634/12.73)
SEEN-BY: 3/50 57/0 130/505 153/250 226/20 100 280/464 317/2 393/68 633/267 280
SEEN-BY: 640/384 712/550 848 770/0 1 100 340 772/0 1 100
@PATH: 3634/12 123/500 153/757 250 770/1 712/848 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.