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 6075fd4c
REPLY: 2:280/464.113 6075a20d
Hi Maurice,

On 2021-04-13 13:52:13, you wrote to me:

 MK> For the record we repeated the test on a local echoarea that all
 MK> concerned have access to and it 'failed' again which is exactly what
 MK> was suspected. Therefore we all concluded that dupe checking is ONLY
 MK> based on MSGIDs given all were original and compliant MSGs.

 MK> If you want I could repeat the third test here just to see how far your
 MK> dupe checking goes when encountering a duped MSGID.  I think it was
 MK> worthwhile.  Also the EuroPoint uses the 32-bit hex unixtime for it's
 MK> serial numbers instead of the random 8 character [:alnum:] regex one but
 MK> that shouldn't matter.  What will matter is your dupe checker's abilities
 MK> to differentiate between a real dupe and one where only the MSGID is
duped.

Well FMail's dupe checking works a little bit different. When there is a valid
MSGID, it also uses the first letters of the From, To and Subject, for it's
dupe checking. So if they differ, while the MSGID is the same it's not
considered a dupe.

 MK> Let me know and I'll make it so.

You are welcome to test it, but I already know how it works. ;)

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