MSGID: 1:104/57.0 4ec959e8   
   PID: ViaMAIL! v2.00 90-0001   
   -> JM> Just out of curiousity, what's the recommended way of dupe checki   
   -> JM> these days, MSGID, TID/PID, CRC, combination there of (including   
   -> JM> Header)?   
   ->   
   -> MSGID is the main way but older software doesn't generate MSGID so   
   -> other methods need to be used...   
      
   My mailer/tosser uses a combined approach.  If the message contains a   
   MSGID then use its value, otherwise CRC the header and message body   
   including control lines but never the SEEN-BY/PATH lines (considering   
   they change all the time).  The tosser never duplicates an MSGID either   
   as it maintains a file with the last used value seeded upon creation by   
   the current date/time.  This prevents issues should that file get   
   deleted.   
      
   To provide speed and limit disk space, I also have an expiration   
   mechanism (user configurable) that will purge CRC entries after a given   
   amount of time (ie: 2 weeks but not more than 30 days).  So while it's   
   efficient catching dupes in that time period, if someone does a rescan   
   and dumps everything back into the echo a month later, it won't catch   
   them. It's a trade off, but back in the day when we had 40mb drives and   
   8088/80286 processors, it was extremely important.   
      
   -> instead of CRC... the problem then comes from those systems that   
   -> mistakenly reformat the messages as they process them and write the   
   -> reformatted messages to new PKTs... now the message body is   
      
   Yeah this is and always will be an issue.   
      
   -> is apparent on systems that only get, for example, one posting of an   
   -> echos rules each month and only accept new postings of those rules   
      
   It would seem to me, (me mind you) that if you're moderating an echo,   
   your software "should" be able to generate a MSGID to prevent this issue   
   entirely.  But hey...   
      
   -> what i would do would be to ask other tosser devs what they use in   
   -> their code...   
   ->   
   -> listed in no particular order:   
   ->   
   -> tobias burchhardt  - fastecho   
   -> rob swindell       - sbbsecho   
   -> nick andre         - d'bridge   
   -> vince coen         - mbse's tosser   
   -> kim heino          - bbbs' tosser   
   -> wilfred van velzen - fmail   
   -> james coyle        - mystic   
      
   Thanks Mark...   
      
   --- ViaMAIL!/WC v2.00   
    * Origin: ViaSoft Support BBS - Back online at 303-953-0568  (1:104/57)   
   SEEN-BY: 1/123 10/0 1 15/0 2 19/36 34/999 90/1 102/401 103/705 104/57   
   SEEN-BY: 106/201 116/18 120/331 123/140 153/7715 203/0 218/0 1 109   
   SEEN-BY: 218/210 215 401 410 520 601 700 720 802 221/0 222/2 227/114   
   SEEN-BY: 229/354 426 1014 230/150 152 240/5832 249/206 317 250/1 261/38   
   SEEN-BY: 261/100 266/512 267/155 275/100 280/464 282/1031 1056 291/1   
   SEEN-BY: 291/111 317/3 320/119 219 322/757 340/400 342/13 200 396/45   
   SEEN-BY: 633/280 712/848 801/161 189 2320/700 3634/12 5020/1042   
   PATH: 104/57 261/38 218/700 103/705 280/464 229/426