I'm using the Linux version of Squish 1.11 and have a problem wioth
dupe checking. According to me the following two messages should not
be marked as dupes because they have different MsgIDs. At the moment
I'm using "DupeCheck MsgID", but I also tried "DupeCheck Header
MsgID". And I have "DupeLongHeader" in my config, although that
should, I believe, not make any difference in this case.
Could somebody please tell me what's wrong?
I'm using the Linux version of Squish 1.11 and have a problem wioth
dupe checking. According to me the following two messages should not
be marked as dupes because they have different MsgIDs.
I'm using the Linux version of Squish 1.11 and have a problem wiothIt appears that both of the messages you posted info for were the ones that Squish placed in the DUPE area. That means that each of these two has a twin that already lives in the target area,
dupe checking.
not that these two are twins of each other. You would need to have received triplets in order to end up with twins in the DUPE
area.<g>
I'm using the Linux version of Squish 1.11 and have a problem wiothWe did have some major problems with dupechecking and the 3.03b release of maximus, they are fixed in the CVS version.
dupe checking.
1. Use the CVS version
2. Only do dupechecking on Header. In squish.cfg
Unfortionally can't I send you a patch because Bob Jones did correct the problem, and I can't remember what was wrong (properly some collition of 32- and 16 bit integers).
If you have other problems with Squish feel free to report them.
But I soon found out these weren't real dupes.
I'm using the Linux version of Squish 1.11 and have a problem wioth
dupe checking. According to me the following two messages should not
be marked as dupes because they have different MsgIDs.
It appears that both of the messages you posted info for were the
ones that Squish placed in the DUPE area. That means that each of
these two has a twin that already lives in the target area, not
that these two are twins of each other. You would need to have
received triplets in order to end up with twins in the DUPE
area.<g>
Hallo Bo,
I'm using the Linux version of Squish 1.11 and have a problem wioth
dupe checking.
We did have some major problems with dupechecking and the 3.03b
release of
maximus, they are fixed in the CVS version.
Aha :))
1. Use the CVS version
I just installed it, so will find out tomorrow morning if this
problem has been solved.
2. Only do dupechecking on Header. In squish.cfg
Except for the date, the headers in these messages are all the
same. Would it work then?
Unfortionally can't I send you a patch because Bob Jones did
correct the
problem, and I can't remember what was wrong (properly some
collition of
32- and 16 bit integers).
That's no problem. I have ADSL so don't have to worry about those
nasty ticks in the telephone :)
If you have other problems with Squish feel free to report them.
Of course I will :)) But don't expect too much from me: I only set
up this point system to help one of my points who is interested in
reading his Fido messages under Linux, instead of in a Dos-box
under Windows.
For myself I'm happy with mbse [a Linux-native
all-in-one package] and GoldED+.
They got different MSGID so squish wouldn't juge it as dupe
normally, but there is a bug with dupe detection in the current
release.
On 04-08-04 18:34, Bo Simonsen <=-
spoke to Mike Tripp about Dupe checking <=-
They got different MSGID so squish wouldn't juge it as dupe
normally, but there is a bug with dupe detection in the
current release.
We did have some major problems with dupechecking and the 3.03b
release of maximus, they are fixed in the CVS version.
Aha :))We are about to release a more stable version of maximus/squish/sqafix.
1. Use the CVS version
I just installed it, so will find out tomorrow morning if thisOkay, I'm 99% sure it's. :) Squish is so stable, so I've fixed all compiler warnings in it! ;)
problem has been solved.
2. Only do dupechecking on Header. In squish.cfg
Except for the date, the headers in these messages are all theI'm not sure, I didn't get mutch dupe by running Squish without msgid check, and right now there are still people which is using Software which seems to be buyed at antique-market, which doesn't set @MSGID. So Squish will only do dupechecking on Header, and it's not caused any dupes to me.
same. Would it work then?
Unfortionally can't I send you a patch
That's no problem. I have ADSL so don't have to worry about thoseOkay. :) I've cable but it's the same princip.
nasty ticks in the telephone :)
For myself I'm happy with mbse [a Linux-nativeI see. :) I know MBSE it's good software, but there is some things I doesn't like about it.
all-in-one package] and GoldED+.
And if I ran software made by others, I can't figure out what to
program on. ;)
@PID: timEd/Linux 1.11.b1
They got different MSGID so squish wouldn't juge it as dupeJust trying to make sure he was looking for a total of 4 messages across at least 2 areas and not just comparing the info from 2 that he posted from his dup area with each other.
Not so. Squish has the ability to use two different sorts of
duplicate checking. One is based on MSGID.
The other is based on
the header info (TO, FROM, SUBJ and DATE). If *either* of these
two
things is a match, then Squish calls the message a dupe.
They got different MSGID so squish wouldn't juge it as dupe
normally, but there is a bug with dupe detection in the
current release.
Not so. Squish has the ability to use two different sorts of duplicate checking. One is based on MSGID. The other is based on
the header info (TO, FROM, SUBJ and DATE). If *either* of these
two things is a match, then Squish calls the message a dupe.
Hence if someone happens to send a bunch of messages to the same
person, all with the same subject and the same date/time stamp
then squish will call all but the first a dupe if that option is
set. Since some systems do Y2K protection by inserting the
date/time of upload, this can cause a problem.
We did have some major problems with dupechecking and the 3.03b
release of maximus, they are fixed in the CVS version.
Aha :))
We are about to release a more stable version of maximus/squish/sqafix.
That's good :))
1. Use the CVS version
I just installed it, so will find out tomorrow morning if this
problem has been solved.
Okay, I'm 99% sure it's. :) Squish is so stable, so I've fixed all
compiler warnings in it! ;)
Of course, there were no new file announcements today... I'lllet
you know as soom as I know something more, be it good or bad.
2. Only do dupechecking on Header. In squish.cfg
Except for the date, the headers in these messages are all the
same. Would it work then?
I'm not sure, I didn't get mutch dupe by running Squish without msgid
check, and right now there are still people which is using
Software which
seems to be buyed at antique-market, which doesn't set @MSGID.
So Squish
will only do dupechecking on Header, and it's not caused any
dupes to me.
Well, I think yhat question is academic now that the problem is
solved.
Unfortionally can't I send you a patch
That's no problem. I have ADSL so don't have to worry about those
nasty ticks in the telephone :)
Okay. :) I've cable but it's the same princip.
ADSL came first in this village. I moved to it when my ISDN card
died about 2.5 years ago.
For myself I'm happy with mbse [a Linux-native
all-in-one package] and GoldED+.
I see. :) I know MBSE it's good software, but there is some things I
doesn't like about it.
It's still changing every day. Enhancements and bug fixes. The
author is very keen. Usually when you report a bug it will be
fixed within a couple of days. When I started playing with Linux
and thinking about Fido software for it, I could not find anything
I liked until I met mbse.
There were a lot of problems with it
then! I got a reward for reporting the most bugs :)) But I had
been running Maximus and Squish under MS-Dos since March 1992!
And if I ran software made by others, I can't figure out what to
program on. ;)
I Seem not to get to do much "private" programming these days. And anyway, I am anCbete, so would not be a great help. My main
languages are Fortran, Pascal, COBOL and Abal.
@PID: timEd/Linux 1.11.b1
Ah, yes, Gerards programs have been ported to Linux as well... I
was appointed as beta tester [three volunteers: you, you and
you...] but could never get really used to it.
Too much used to
GoldED already :) But NetMgr and WIMM fully earned their place on
my disk!
On 04-10-04 22:35, Bo Simonsen <=-
spoke to Dale Shipp about Dupe checking <=-
duplicate checking. One is based on MSGID. The other is based on
the header info (TO, FROM, SUBJ and DATE). If *either* of these
two things is a match, then Squish calls the message a dupe.
Yes you may be right, I've not looked specifically in the code of that area.
One is based on MSGID. The other is based on the header info (TO,
FROM, SUBJ and DATE). If *either* of these two things is a match,
then Squish calls the message a dupe.
duplicate checking. One is based on MSGID. The other is based
on
the header info (TO, FROM, SUBJ and DATE). If *either* of
these two things is a match, then Squish calls the message a
dupe.
Yes you may be right, I've not looked specifically in the code of
that area.
Nor have I -- that was quoting from the manual.
Because of the fact that the header checking can lead to false
duplicate detection, I have long ago turned that off and only use
MSGID checking. Of course, there are a few BBSes out there that do
not use MSGIDs.
On 04-13-04 08:52, Johannes Beekhuizen <=-
spoke to Dale Shipp about Re: Dupe checking <=-
Hallo Dale,
Op 09 Apr 04 schreef Dale Shipp aan Bo Simonsen:
One is based on MSGID. The other is based on the header info (TO,
FROM, SUBJ and DATE). If *either* of these two things is a match,
then Squish calls the message a dupe.
That's not how I understand it. Allow me to quote from the manual:
If EITHER the MSGID or the^^^^^^
header is duplicated, Squish will declare the message to
be a dupe.
=== import ===
DupeCheck [<type>...]
The DupeCheck keyword controls the dupe-checking
algorithm used by Squish:
<type> can be either or both of "Header" or "MSGID".
"Header" instructs Squish to check the message header
to determine whether or not a message is a dupe. Squish
will hash the "To", "From" and "Subject" fields into a
32-bit identifier. It will append the message date to
this, resulting in a 64-bit duplicate identifier.
"MSGID" instructs Squish to check the MSGID kludge to
determine whether or not a message is a dupe. Squish
will hash the text of the MSGID "address" field into a
32-bit identifier. It will append the MSGID serial
number to this, resulting in a 64-bit duplicate
identifier.
If only one of the above settings is enabled, Squish
will only use that method when determining whether or
not a message is a dupe.
However, if both MSGID and Header are specified, Squish
will perform both checks. If EITHER the MSGID or the
header is duplicated, Squish will declare the message to
be a dupe.
=== tropmi ===
I read is as: If and only if both Header and MsgID are the same, the message is a dupe. Which seems sensible to me. That, at least in the last Linux release, it didn't work is a different matter.
Groetjes,
Hans.
-!- GoldED+/LNX 1.1.5cvs031202
! Origin: The Wizard uses MBSE/Linux (2:280/1018)
perform both checks. If EITHER the MSGID or the header is
duplicated, Squish will declare the message to be a dupe.
=== tropmi ===
I read is as: If and only if both Header and MsgID are the same, the message is a dupe.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,044 |
Nodes: | 15 (0 / 15) |
Uptime: | 00:26:03 |
Calls: | 500,299 |
Calls today: | 17 |
Files: | 95,204 |
U/L today: |
1 files (1,581K bytes) |
D/L today: |
2,575 files (614M bytes) |
Messages: | 465,287 |
Posted today: | 13 |