On 18.02.2024 23:50, Jay Harris wrote:

This message ended up in my DUPE base. I just checked the FIDOTEST echo
and this message isn't already in there.

Here's what I have in my config:

DupeBaseType HashDupesWMsgId
EchoAreaDefaults -dupecheck move -dupehistory 14

I did notice this message doesn't have a MSGID kludge, assuming that's
the reason it ended up there. What can I adjust to make sure these
messages don't end up in dupe quarantine?

Confirmed here too.

The message in my dupebase has no kludges at all.

'Tommi

---
* Origin: jamnntpd/lnx (2:221/1.0)

On 23 Feb 2024, Tommi Koivula said the following...

DupeBaseType HashDupesWMsgId

I've set this to "HashDupes", and now there is one message in FIDOTEST from this same system that was processed just fine without MSGID.

Seems to work!

Thank you sir, I've adjusted that and will keep an eye out.


Jay

... I put my phone on airplane mode and now it's delayed by 45 minutes

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (1:229/664)