Hello Marc!

17 Nov 02 22:44, Marc Lewis wrote to All:

 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.

That's broken.

 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.

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

 ML> Do you think disabling the MSGID check would help any?

If you want to pass bad MSGIDs...yes.  I have had to do this also, due to a
downlink's autoposter using the same MSGID as if it were it's own PID,
daily.

 ML> Or has anyone done any updating on Squish to improve this
 ML> performance; or perhaps some sort of workaround like an external
 ML> dupe detector?

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

 ML> In fact, can dupe detection be completely disabled in Squish?

Certainly hope not.  The CRC's for dupe detection are stored in the .SQB
for the area in question.  You could delete these and Squish would forget
about the ones it tossed on prior runs, but this won't help with a batch in
the same PKT.

For those, you could post-process the messages that ended up in your Dupe
area if you're configured to keep them.  You also might be able to con a
message mover util (NetMgr, SQTool, etc) to shuffle them with different/no
dupechecking.

.\\ike

--- GoldED 2.50+