Hello, I have an interesting issue. This has happened with more than one FTN so far. Not sure if I have a setting set incorrectly somewhere.

When I join a new FTN, and send areafix a %RESCAN and I end up with thousands of new messages I obviously go to set a newscan date.

The problem is, I still randomly end up with some echo bases not actually updating with the newscan date and still have 1000+ unread in one base.

I assumed maybe this was just a fluke the first time. So, I did it again, same results for that single FTN. Since then, I have seen it with two other FTN's that I have setup.

Any ideas?

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Hello, I have an interesting issue. This has happened with more than one FTN so far. Not sure if I have a setting set incorrectly somewhere.

When I join a new FTN, and send areafix a %RESCAN and I end up with thousands of new messages I obviously go to set a newscan date.

The problem is, I still randomly end up with some echo bases not actually updating with the newscan date and still have 1000+ unread in one base.

FTN and AreaFix and RESCANs are all related. But your new scan date on a BBS has nothing to do with FTN. I am not sure I am understanding your situation here.

... I'm not a complete idiot... Several parts are missing!

--- Mystic BBS v1.12 A47 2021/08/22 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

On Tuesday, August 24, 2021 at 8:20:26 AM UTC-5, g00r00 wrote:

Hello, I have an interesting issue. This has happened with more than one FTN so far. Not sure if I have a setting set incorrectly somewhere.

When I join a new FTN, and send areafix a %RESCAN and I end up with thousands of new messages I obviously go to set a newscan date.

The problem is, I still randomly end up with some echo bases not actually
updating with the newscan date and still have 1000+ unread in one base.

FTN and AreaFix and RESCANs are all related. But your new scan date on a BBS has nothing to do with FTN. I am not sure I am understanding your situation here.

... I'm not a complete idiot... Several parts are missing!

My appologies, I will try and explain better. Basically when I join a new FTN and request a %RESCAN to areafix from the hub to download all previous echonet messages let's say it download 20k messages. That is all fine and well, the problem is it shows
20k new messages, and when selecting 'Set Newscan Date' as a user in the Messages menu of the BBS, and select lets say todays date. Then, I go open the Indexed MSG Reader, and the majority of message bases still show New with messages much older than the
date selected.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

My appologies, I will try and explain better. Basically when I join a
new FTN and request a %RESCAN to areafix from the hub to download all previous echonet messages let's say it download 20k messages. That is
all fine and well, the problem is it shows
20k new messages, and when selecting 'Set Newscan Date' as a user in the Messages menu of the BBS, and select lets say todays date. Then, I go
open the Indexed MSG Reader, and the majority of message bases still
show New with messages much older than the
date selected.

When you do a rescan with the intent of building a starting point for a message base, the intent is that your message base is empty. If you rescan and add older messages after newer messages, then they will show up the way you describe and I'll explain why:

Message last read pointers are stored by message number not date and time. When you reset your last read pointers by date, Mystic is going to set the starting message to the first message that meets the date that you requested...

In other words if you have messages posted on August 15, 2021 before messages posted January 1st 2021 because you did a rescan with existing messages, then Mystic must set the starting message to the August 15th message which technically is a lower message number than the January 1st date.

... As a matter of fact, it IS a banana in my pocket!

--- Mystic BBS v1.12 A47 2021/08/22 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello Kevin,

On Mon Aug 23 2021 10:58:02, you wrote to All:

Hello, I have an interesting issue. This has happened with more than
one FTN so far. Not sure if I have a setting set incorrectly
somewhere.

When I join a new FTN, and send areafix a %RESCAN and I end up with thousands of new messages I obviously go to set a newscan date.

The problem is, I still randomly end up with some echo bases not
actually updating with the newscan date and still have 1000+ unread in
one base.

I assumed maybe this was just a fluke the first time. So, I did it
again, same results for that single FTN. Since then, I have seen it
with two other FTN's that I have setup.

Any ideas?

I'm going to guess that newscan dates (specifically to echomail) is based on when the messages arrive on your system. So rescanned messages would all be considered arriving on your system the same day/time you do the rescan.

During the rescan, you would have to specify how far back to rescan messages in your netmail to the hub, with the rescan options provided from Areafix. (ie: 30 days, etc).

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20210705
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)