TID: FMail-lnx64 2.1.0.18-B20170815   
   RFC-X-No-Archive: Yes   
   TZUTC: 0200   
   CHRS: UTF-8 2   
   PID: GED+LNX 1.1.5-b20161221   
   MSGID: 2:280/464 6076aaf6   
   REPLY: 2:221/1.58@fidonet ef616eac   
   Hi August,   
      
   On 2021-04-13 17:02:00, you wrote to me:   
      
    WvV>> Well FMail's dupe checking works a little bit different.   
    WvV>> When there is a valid MSGID, it also uses the first   
    WvV>> letters of the From, To and Subject, for it's dupe   
    WvV>> checking. So if they differ, while the MSGID is the same   
    WvV>> it's not considered a dupe.   
      
    AA> Clever, that is!   
      
    AA> Is that a way to reduce the probability of collisions within a   
    AA> certain span of allotted time?   
      
   I don't know, it's how the original author of FMail implemented it. If that   
   was because of a detected collision event, or because he found it a good idea   
   before hand, when he developed the algorithm, I don't know...   
      
   But I think you are confusing the MSGID genererating side and the dupe   
   detecting on the other side of the fence. ;)   
      
   The MSGID generating side must try to prevent collisions. The dupe detecting   
   side can only respond to it by making the detecting algorithm as robust as   
   possible.   
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 1/123 18/200 90/1 105/81 120/340 123/131 124/5016 129/305   
   SEEN-BY: 154/10 203/0 221/0 226/30 227/114 229/101 424 426 452 664   
   SEEN-BY: 229/700 1016 1017 240/1120 2100 5138 5411 5824 5832 5853   
   SEEN-BY: 249/206 317 400 280/464 5003 282/1038 288/100 292/8125 301/1   
   SEEN-BY: 310/31 317/3 320/219 322/757 342/200 396/45 423/120 460/58   
   SEEN-BY: 633/280 770/1 2454/119   
   PATH: 280/464 240/5832 229/426