*** Answering a msg posted in area DUPE (DUPE).

On Sunday February 18 2024, Michael Selhof said the following...

@AREA:FIDOTEST
Hi Mike

Got it!

Greetings

Also a Mike :-)

On 18.02.2024 13:58, Mike Powell wrote to All:

@TZUTC: -0500
@MSGID: 1.fidotest@1:2320/905 2a378818
@PID: Synchronet 3.19c-Linux master/cb76b1463 Feb 18 2024 GCC

12.2.0 -> @TID: SBBSecho 3.14-Linux master/cb76b1463 Feb 18 2024 GCC 12.2.0 -> @COLS: 80 -> @BBSID: CAPTEST -> @CHRS: ASCII 1 -> @NOTE: Synchronet msgeditor master/cb76b1463 -> Testing out the test system.

--- SBBSecho 3.14-Linux -> * Origin: Capitol City Test System

(1:2320/905)

--- Platinum Xpress/Win/WINServer v7.0
* Origin: Transfered from GLOBAL CHAOS BBS (2:240/8050)
SEEN-BY: 1/19 15/0 16/0 19/37 40 30/0 90/1 103/705 105/81 106/201
SEEN-BY: 123/130 124/5016 128/260 135/225 142/104 799 153/757 7715 SEEN-BY: 154/10 30 203/0 218/700 221/0 1 226/30 227/114 229/110 112 SEEN-BY: 229/113 200 206 275 307 317 400 426 428 470 550 664 700
240/1120
SEEN-BY: 240/1634 5411 5824 5832 5853 5890 8002 8005 8050 266/512
SEEN-BY: 280/464 5003 5555 282/1038 291/111 292/854 8125 301/1 310/31 SEEN-BY: 313/41 320/119 219 319 2119 322/757 325/304 335/364 341/66 SEEN-BY: 341/234 342/19 200 371/0 382/147 396/45 423/120 460/58
467/888
SEEN-BY: 492/0 530/204 550/278 633/280 712/848 770/1 3634/12 5020/400 SEEN-BY: 5075/35
@PATH: 240/8050 1120 280/464 240/5832 320/219 229/426

Hi All,

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?


Jay

... Well, well, well if it isn't three holes in the ground
--- GoldED+/LNX 1.1.5-b20240209
* Origin: Northern Realms (1:229/664)

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)

Hi Jay.

18 Feb 24 16:50, you wrote to All:

*** Answering a msg posted in area DUPE (DUPE).

Here's what I have in my config:

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.

=== cut ===
@TID: PX/Win v7.0 PX36-1282M
@TZUTC: 0100
Got it in Germany, too.

Seems to work!

.....

--- Platinum Xpress/Win/WINServer v7.0
* Origin: Transfered from GLOBAL CHAOS BBS (2:240/8050)
@PATH: 240/8050 1120 280/464
=== cut ===

'Tommi

--- GoldED+/LNX 1.1.5-b20240209
* Origin: nntps://news.fidonet.fi (2:221/6)

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)