Hello everybody.

I had recently an issue with a JAM area into my system that got corrupted beyond repair.

As this area belongs to a Portuguese-echoed area at Fido, I requested my RC a %RESCAN, but to my surprise I got only the messages from outside my system... All the old messages from my BBS got stuck into the DUPES area.

As my uplink uses FastEcho, is there a way to overcome this?

Flavio

... "Vou pedir uma Caipiroca" - Aranha, 1╖ Encontro UnionNet:
--- MacFidoIP 1.0 (OSX)
* Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)

As this area belongs to a Portuguese-echoed area at Fido,
I requested my RC a %RESCAN, but to my surprise I got only the
messages from outside my system... All the old messages from my
BBS got stuck into the DUPES area.

As my uplink uses FastEcho, is there a way to overcome
this?

But isn't this *your* system detecting them as dupes / already imported?




-joho

---
* Origin: reboot.defsol.com (2:20/4609)

Hi! Flavio,

On 09/27/2017 12:45 AM, you wrote to All:

As my uplink uses FastEcho, is there a way to overcome this?

Just the guy for a copy of his JAM files. :)

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)

On 2017 Sep 26 11:45:24, you wrote to All:

I had recently an issue with a JAM area into my system that got
corrupted beyond repair.

that can happen at times...

As this area belongs to a Portuguese-echoed area at Fido, I requested
my RC a %RESCAN, but to my surprise I got only the messages from
outside my system... All the old messages from my BBS got stuck into
the DUPES area.

yup! that's how it should be...

As my uplink uses FastEcho, is there a way to overcome this?

maybe delete your dupe database and %RESCAN again??

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... To eat or not to eat, the question is whom to eat!
---
* Origin: (1:3634/12.73)

Hi! Flavio,

On 09/27/2017 07:07 AM, I wrote:

As my uplink uses FastEcho, is there a way to overcome this?

Just the guy for a copy of his JAM files. :)

^^^
Oops, that's missing the word "ask". I think it got sucked up by a session file 'save' function made during this temporary OS boot (Puppy Linux on USB). Sorry.

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)

Hello Joaquim.

26 Sep 17 22:02, you wrote to me:

As my uplink uses FastEcho, is there a way to overcome
this?

But isn't this *your* system detecting them as dupes / already
imported?

Indeed. I was wondering if there were any way to "force" the rescan and
tell the messagebase to ignore the dupe setting.

Flavio

... "Cade o Oliveira???? " - VII Encontro UnionNet
--- MacFidoIP 1.0 (OSX)
* Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)

Hello mark.

26 Sep 17 17:17, you wrote to me:

As my uplink uses FastEcho, is there a way to overcome this?

maybe delete your dupe database and %RESCAN again??

You mean, deleting the DUPES area?

Flavio

... "Cuidado pq a escada e de sorvete e pode derreter!" -Cris
--- MacFidoIP 1.0 (OSX)
* Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)

On 2017 Sep 27 10:59:54, you wrote to me:

As my uplink uses FastEcho, is there a way to overcome this?

maybe delete your dupe database and %RESCAN again??

You mean, deleting the DUPES area?

no... that's just a message base where they are stored so you can review them if you want to make sure that no FPs slipped through...

i'm talking about deleting the %fecho%\FASTECHO.DUP file... that's where all the hashes are stored that FE uses to determine a dupe...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Give up, you'll only live till you die.
---
* Origin: (1:3634/12.73)

As my uplink uses FastEcho, is there a way to overcome
this?

But isn't this *your* system detecting them as dupes / already
imported?

Indeed. I was wondering if there were any way to "force"
the rescan and tell the messagebase to ignore the dupe setting.

You could probably move the FASTECHO.DUP file out of the way, do your tossing, and then put it back again.



-joho

---
* Origin: reboot.defsol.com (2:20/4609)