Hello Mike.



 ML> coming from mailing lists gated into echo format.  Sometimes a whole
 ML> group of messages arrives at once and all end up with the same MSGID.

 MT> That's broken.

I agree, and short of using GSAR to alter the lines in squish.cfg before
those messages get tossed, there's not a whole lot I can do w/o manual
intervention.

 ML> Needless to say, Squish traps all but the first one.  It doesn't
 ML> seem to make _any_ difference enabling the 'DupeLongHeader' with
 ML> 'DupeCheck Header MSGID' - it seems to ignore the header info.

 MT> If you enable both tests, the message must pass both tests.

I also have a problem with that.  I post messages to the Vatican and the
Intelec IN_Catholic echos with a batch file (using MsgPost/TE) that waits 8
seconds between each post, guaranteeing a distinct MSGID for every message.
 

At this end (at my point) I have ONLY MSGID enabled in the squish.cfg.  It
tosses the Vatican messages and traps the identical messages (with
different MSGID's) that should post to the IN_Catholic echo. (Which is in a
different Zone as well.)  _That_ is broken.  In addition to the different
MSGID's, the messages have the same text in the Subj: area, but spaced and
punctuated differently in 4 variations, just to break things up.  That
makes no difference either.

 ML> performance; or perhaps some sort of workaround like an external
 ML> dupe detector?

 MT> It is the messages that are broken...not the tosser.  If you want a
 MT> hack, hack the messages into compliance, so that Squish will pass
 MT> them. 

I will differ with you on this in this particular scenario, Mike.  I
sincerely believe there *is* a logic defect in Squish's dupe detection
routines.   Hopefully someone will find it and correct it some day.

Best regards,
Marc

--- timEd/2 1.10.y2k+