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?
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!
Sysop: | Sarah |
---|---|
Location: | Portland, Oregon |
Users: | 57 |
Nodes: | 16 (0 / 16) |
Uptime: | 20:03:12 |
Calls: | 370 |
Calls today: | 370 |
Files: | 84,190 |
U/L today: |
44 files (5,578M bytes) |
D/L today: |
2,893 files (194M bytes) |
Messages: | 49,941 |
Posted today: | 29 |