Subj : Re: Dupe checking
To   : Dale Shipp
From : Johannes Beekhuizen
Date : Tue Apr 13 2004 09:52 am

Hallo Dale,

Op 09 Apr 04 schreef Dale Shipp aan Bo Simonsen:

DS> One is based on MSGID.  The other is based on the header info (TO,
DS> FROM, SUBJ and DATE).  If *either* of these two things is a match,
DS> then Squish calls the message a dupe.

That's not how I understand it.  Allow me to quote from the manual:

=== 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)