I finally found at least part of the bug in the dupe checker in the port of
Squish to Linux.  I'm now testing the fix, but I'm not properly catching
dupes yet.  This should solve the problem of calling a number of messages
duplicates when they were not.  Basically, the MSGID read on importing
messages was not reading the full 8 hex digits of the unique message id. 
:( 

Now that I've found this one, I expect there will be a few other data
errors that I haven't caught yet dealing with reading and/or writing
hexidecimal strings.  If this message has an invalid Message ID string,
then that points to the same type of problem in another part of the
code.....

I'll post again once I've checked in the needed changes to the sourceforge
CVS server.  The changes will be available from the public sourceforge CVS
server 24 hours after the changes are checked in on the sourceforge
development server.  

Note:  I believe existing dupe information for existing databases are in
error if you have used any of the Squish / Unix ports to date.  So, when
you update to the corrected code, you probably should delete any existing
files containing the dupe check hash values....

Take care.....

Bob Jones, 1:343/41


--- Maximus/UNIX 3.03b