MSGID: 1:104/57.0 4ec959f0   
   PID: ViaMAIL! v2.00 90-0001   
   -> JM> My mailer/tosser uses a combined approach.  If the message contai   
   -> JM> MSGID then use its value, otherwise CRC the header and message   
   -> body JM> including control lines but never the SEEN-BY/PATH lines   
   -> (considering JM> they change all the time).   
   ->   
   -> sounds similar to what my MSGID code does... i've shared that   
   -> information with several folks... not sure if you were one of those   
   -> or not... i still have the original 1994 (i think) post that   
   -> described it, too :)   
      
   Don't recall for sure.   
      
   -> JM> mechanism (user configurable) that will purge CRC entries after a   
   -> JM> amount of time (ie: 2 weeks but not more than 30 days).  So   
   -> while it's JM> efficient catching dupes in that time period, if   
   -> someone does a rescan JM> and dumps everything back into the echo a   
   -> month later, it won't catch JM> them. It's a trade off, but back in   
   -> the day when we had 40mb drives and JM> 8088/80286 processors, it   
   -> was extremely important.   
   ->   
   -> yeah and that's gonna likely be a problem since the spec states three   
   -> in this day in time, retaining three years worth of dupe detection da   
   -> be a small drop in the bucket of available drive space and processing   
   -> needed to perform a lookup...   
      
   Fortunately, for today's systems, I can easily kick that number up   
   without much fear.  If I need to, I will.  In the mean time, I'll keep   
   an eye out.   
      
   The nice part is that I have released a new version just a few weeks   
   back and as such, everything is all up to date and ready to go should I   
   need to release a new version.  I even went so far as to write a custom   
   builder application that provides UI to define a application,   
   its associated executables, help files and so on which will compile the   
   programs and create a ZIP file out of them and even put the correct time   
   stamps on them.  So the hard part of updates is no longer an issue.   
      
   -> JM> Yeah this is and always will be an issue.   
   ->   
   -> not if the message body is not CRC'd ;)   
      
   The issue is with reformatting.  I can see the software that replies to   
   the message and the tosser that places the message in the message base   
   doing reformatting, but not the tosser reformatting a message and   
   then 'forwarding' it up/down stream. In my mind, that's taboo --   
   just wrong on so many levels, can you say tampering...   
      
   -> JM> It would seem to me, (me mind you) that if you're moderating an   
   -> echo, JM> your software "should" be able to generate a MSGID to   
   -> prevent this issue JM> entirely.  But hey...   
   ->   
   -> that depends on the software used... some text file posting tools are   
   -> old and do not have any concept of MSGID... i'm thinking of the old H   
   -> Robot in at least one case...   
      
   I know, but being a moderator implies many things and running outdated   
   software shouldn't be one of them.  My two cents anyway.   
      
   -> you're welcome... i hope that you've also seen the other two posts ab   
   -> and intermail which should also be added to the above list...   
      
   I did, thanks.   
      
   Joe Martin   
      
   --- ViaMAIL!/WC v2.00   
    * Origin: ViaSoft Support BBS - Back online at 303-953-0568  (1:104/57)   
   SEEN-BY: 1/19 123 15/0 2 16/0 19/36 34/999 90/1 103/705 104/57 106/201   
   SEEN-BY: 116/18 120/331 544 123/130 131 140 153/7715 203/0 218/700   
   SEEN-BY: 221/0 1 6 242 360 222/2 227/114 229/354 426 1014 230/150   
   SEEN-BY: 230/152 240/5832 249/206 317 250/1 261/38 100 266/512 267/155   
   SEEN-BY: 275/100 280/464 282/1031 1056 291/1 111 317/3 320/119 219   
   SEEN-BY: 322/0 757 340/400 342/13 200 396/45 633/280 712/848 801/161   
   SEEN-BY: 801/189 2320/700 3634/12 5020/1042   
   PATH: 104/57 261/38 320/219 221/1 280/464 229/426