Subj : Re: Dupe checking To : Johannes Beekhuizen From : Dale Shipp Date : Wed Apr 14 2004 02:37 am -=> On 04-13-04 08:52, Johannes Beekhuizen <=- -=> spoke to Dale Shipp about Re: Dupe checking <=- JB> Hallo Dale, JB> 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. JB> That's not how I understand it. Allow me to quote from the manual: Then you understand wrong. Read the very two last lines in what you quoted. It is quite explicit. JB> If EITHER the MSGID or the ^^^^^^ JB> header is duplicated, Squish will declare the message to JB> be a dupe. That means that you do *not* need both, either one will cause the message to be declared a dupe. IMO, it would be better if it declared the message to be a dupe only if both items said so, but that is not the case. JB> === import === JB> DupeCheck [<type>...] JB> The DupeCheck keyword controls the dupe-checking JB> algorithm used by Squish: JB> <type> can be either or both of "Header" or "MSGID". JB> "Header" instructs Squish to check the message header JB> to determine whether or not a message is a dupe. Squish JB> will hash the "To", "From" and "Subject" fields into a JB> 32-bit identifier. It will append the message date to JB> this, resulting in a 64-bit duplicate identifier. JB> "MSGID" instructs Squish to check the MSGID kludge to JB> determine whether or not a message is a dupe. Squish JB> will hash the text of the MSGID "address" field into a JB> 32-bit identifier. It will append the MSGID serial JB> number to this, resulting in a 64-bit duplicate JB> identifier. JB> If only one of the above settings is enabled, Squish JB> will only use that method when determining whether or JB> not a message is a dupe. JB> However, if both MSGID and Header are specified, Squish JB> will perform both checks. If EITHER the MSGID or the JB> header is duplicated, Squish will declare the message to JB> be a dupe. JB> === tropmi === JB> I read is as: If and only if both Header and MsgID are the same, the JB> message is a dupe. Which seems sensible to me. That, at least in the JB> last Linux release, it didn't work is a different matter. JB> Groetjes, JB> Hans. JB> -!- GoldED+/LNX 1.1.5cvs031202 JB> ! Origin: The Wizard uses MBSE/Linux (2:280/1018) .... Shipwrecked on Hesperus in Columbia, Maryland. 01:03:40, 14 Apr 2004 ___ Blue Wave/DOS v2.30 --- Maximus/NT 3.01 * Origin: Owl's Anchor (1:261/1466)