Hi,
This might be because I haven't upgraded yet, so please let me know if that is the case.

My first problem is that FIDO-REQ is generating hundreds of dupes in Aftershock and I have no idea why. Normally SBBSEcho handles dupes perfectly, but not for that echo.

That leads to the second problem. Deleting lots of dupes. I have the max for echos set to 300, so I am constantly sitting with 300 new messages in the Dupes area. The only way I know of to delete them is one by one which is a complete and utter waste of my time. Is there something obvious I'm missing?

All the best
JD
--- AfterShock/Android 1.6.8
* Origin: FireCat Mobile (4:920/1.1)

Hello John Dovey,

My first problem is that FIDO-REQ is generating hundreds of dupes in Aftershock and I have no idea why. Normally SBBSEcho handles dupes perfectly, but not for that echo.

What is FIDO-REQ? Regular echo? I need to subscribe to it for problem investigation. I do not see this echo in Areafix of Ward. Will ask him
if it possible to make this echo available for me.

With best regards.
--- AfterShock/Android 1.6.12
* Origin: Little Station BBS (2:292/854.180)

John,

My first problem is that FIDO-REQ is generating hundreds of dupes in Aftershock and I have no idea why. Normally SBBSEcho handles dupes perfectly, but not for that echo.

That echo seems to be so popular that no-one around here carries it or is able to get me a rescan.

Can you offer any guidance where I can find it for the Aftershock-developer?

\%/@rd

--- DB4 - 20220519
* Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)

On 23 Nov 2022 15:55 Ward Dossche wrote to John Dovey :

John,

My first problem is that FIDO-REQ is generating hundreds of dupes in
Aftershock and I have no idea why. Normally SBBSEcho handles dupes
perfectly, but not for that echo.

That echo seems to be so popular that no-one around here carries it or is able to get me a rescan.

Can you offer any guidance where I can find it for the Aftershock-developer?

You may talk to my areafix.

Tommi

--- AfterShock/Android 1.6.12
* Origin: ----. .---- .---- (2:221/1.911)

That echo seems to be so popular that no-one around here carries
it or is able to get me a rescan. Can you offer any guidance where
I can find it for the Aftershock-developer?

Angel and Tommi have the FIDO-REQ echo. I think you have links with them.

Be careful with the rescan. Thousands of robot postings...

--
Carlos
--- Hotdoged/2.13.5/Android
* Origin: cyberiada mobile point (2:341/234.12)

What is FIDO-REQ? Regular echo?

A file announcement echo.

--
Carlos
--- Hotdoged/2.13.5/Android
* Origin: cyberiada mobile point (2:341/234.12)

You may talk to my areafix.

As we speak.

\%/@rd

--- DB4 - 20220519
* Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)

My first problem is that FIDO-REQ is generating hundreds of dupes in
Aftershock and I have no idea why. Normally SBBSEcho handles dupes
perfectly, but not for that echo.

What is FIDO-REQ? Regular echo? I need to subscribe to it for problem investigation. I do not see this echo in Areafix of Ward. Will ask him
if it possible to make this echo available for me.

This is a bit complicated.

A node in Z1 is posting very big messages, over 400k. Those messages are tossing OK here but when they pass through some nodes that don't support messages over a certain size (64k, I think) they can get mangled. I see two mangled messages without correct header info or MSGID. For every good message I see here I see two mangled messages also. This issue will reveal itself differently at different nodes with different tossers.

If I read the situation correctly that nodes "New file Announcement" keeps growing every day because the already announced files are not being cleared so they get announced again day after day. The message size grows a little every day.

That node seems to be on auto pilot so that will keep on happening until he gets in front of his keyboard again.

His packets are valid, just quite large and growing every day.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

John,

My first problem is that FIDO-REQ is generating hundreds of dupes in
Aftershock and I have no idea why. Normally SBBSEcho handles dupes
perfectly, but not for that echo.

That echo seems to be so popular that no-one around here carries it or is able to get me a rescan.

Can you offer any guidance where I can find it for the Aftershock-developer?

\%/@rd

LOL.

I didn't expect to catch anyone without it, I thought it was a sort of standard "backbone" kind of echo.
Also, I was asking more about mass deletions rather than being too concerned with the dupe issue.

Oh well, more scrutiny is generally better than less in my experience.

All the best
JD
--- AfterShock/Android 1.6.8
* Origin: FireCat Mobile (4:920/1.1)

Hello John Dovey,

My first problem is that FIDO-REQ is generating hundreds of dupes in
Aftershock and I have no idea why. Normally SBBSEcho handles dupes
perfectly, but not for that echo.

What is FIDO-REQ? Regular echo? I need to subscribe to it for problem investigation. I do not see this echo in Areafix of Ward. Will ask him
if it possible to make this echo available for me.

With best regards.

Thank you for looking. It seems Ward is on the case...

As someone once said ... " The game is afoot" ;-)
--- AfterShock/Android 1.6.8
* Origin: FireCat Mobile (4:920/1.1)

My first problem is that FIDO-REQ is generating hundreds of dupes in
Aftershock and I have no idea why. Normally SBBSEcho handles dupes
perfectly, but not for that echo.

What is FIDO-REQ? Regular echo? I need to subscribe to it for problem
investigation. I do not see this echo in Areafix of Ward. Will ask him
if it possible to make this echo available for me.

This is a bit complicated.

A node in Z1 is posting very big messages, over 400k. Those messages are tossing OK here but when they pass through some nodes that don't support messages over a certain size (64k, I think) they can get mangled. I see two mangled messages without correct header info or MSGID. For every good message I see here I see two mangled messages also. This issue will reveal itself differently at different nodes with different tossers.

If I read the situation correctly that nodes "New file Announcement" keeps growing every day because the already announced files are not being cleared so they get announced again day after day. The message size grows a little every day.

That node seems to be on auto pilot so that will keep on happening until he gets in front of his keyboard again.

His packets are valid, just quite large and growing every day.

Thanks Alan. Yes, the dupes are from one particular node. I couldn't figure out why they weren't being picked up as dupes, but this would make sense.
Do you think it's something we should ask Digital Man to take a look at, or is it too specific?

JD
--- AfterShock/Android 1.6.8
* Origin: FireCat Mobile (4:920/1.1)

Hello John Dovey,

I didn't expect to catch anyone without it, I thought it was a sort of standard "backbone" kind of echo. Also, I was asking more about mass deletions rather than being too concerned with the dupe issue.

I've got the idea.

With best regards.
--- AfterShock/Android 1.6.12
* Origin: Little Station BBS (2:292/854.180)

His packets are valid, just quite large and growing every day.

Thanks Alan. Yes, the dupes are from one particular node. I couldn't figure out why they weren't being picked up as dupes, but this would make sense.
Do you think it's something we should ask Digital Man to take a look at, or is it too specific?

Are you seeing mangled messages without a MSGID? Without a MSGID only message bodies can be checked for dupes. I don't think it is a Synchronet or SBBSecho issue. Your tosser will toss incoming messages (as it should).

I don't think your node is creating dupes, they get created elsewhere.

I don't think Synchronet or SBBSecho are behaving badly.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

His packets are valid, just quite large and growing every day.

Thanks Alan. Yes, the dupes are from one particular node. I couldn't figure
out why they weren't being picked up as dupes, but this would make sense.
Do you think it's something we should ask Digital Man to take a look at, or
is it too specific?

Are you seeing mangled messages without a MSGID? Without a MSGID only message bodies can be checked for dupes. I don't think it is a Synchronet or SBBSecho issue. Your tosser will toss incoming messages (as it should).

I don't think your node is creating dupes, they get created elsewhere.

I don't think Synchronet or SBBSecho are behaving badly.

Yeah, I trust Synchronet, but I thought there might have been a specific issue that could be caught.

I forwarded one of the messages here, but it didn't display the kludges. There IS a MSGID.

JD
--- AfterShock/Android 1.6.8
* Origin: FireCat Mobile (4:920/1.1)

Hello, John Dovey.
On 22/11/22 20:20 you wrote:

That leads to the second problem. Deleting lots of dupes. I have
the max for echos set to 300, so I am constantly sitting with 300
new messages in the Dupes area. The only way I know of to delete
them is one by one which is a complete and utter waste of my time.
Is there something obvious I'm missing?

It would be interesting to have a setting to keep a maximum number of messages in the dupes folder. Or an option to delete them all.

In the meantime, I suppose you could use your favourite file manager, browse to /Android/data/com.avscorp.aftershock/files/dupemail and delete (or move) the *.msg files.
(Not tested)

--
Carlos
--- Hotdoged/2.13.5/Android
* Origin: cyberiada mobile point (2:341/234.12)

It would be interesting to have a setting to keep a maximum number of messages in the dupes folder.

Yes

Or an option to delete them all.

Please!

In the meantime, I suppose you could use your favourite file manager, browse to /Android/data/com.avscorp.aftershock/files/dupemail and delete (or move) the *.msg files.
(Not tested)

No thank you.

JD

--- AfterShock/Android 1.6.8
* Origin: FireCat Mobile (4:920/1.1)

25 nov 2022 13:45, John Dovey -> Carlos Navarro

In the meantime, I suppose you could use your favourite file manager,
browse to /Android/data/com.avscorp.aftershock/files/dupemail and delete
(or move) the *.msg files.
(Not tested)

No thank you.

:-)

Ok, I tested this myself with a bunch of dupes. Works fine, no issues (as I expected).

Carlos

--- AfterShock/Android 1.6.12
* Origin: cybShock (2:341/234.1234)

Hello, Carlos Navarro.
On 25/11/2022 18.21 you wrote:

It would be interesting to have a setting to keep a maximum number of messages in the dupes folder. Or an option to delete them all.
In the meantime, I suppose you could use your favourite file manager, browse to /Android/data/com.avscorp.aftershock/files/dupemail and delete (or move) the *.msg files.
(Not tested)

I dont have that folder in this Samsung A52. No SDCard.

Anywhere else to search? I see now one problematic .pkt with io error like August some time ago.

---
* Origin: nntp://news.fidonet.fi (2:221/6.0)

28 Nov 2022 20:16, you wrote to me:

It would be interesting to have a setting to keep a maximum
number of messages in the dupes folder. Or an option to delete
them all. In the meantime, I suppose you could use your favourite
file manager, browse to
/Android/data/com.avscorp.aftershock/files/dupemail and delete
(or move) the *.msg files. (Not tested)

I dont have that folder in this Samsung A52. No SDCard.

Anywhere else to search? I see now one problematic .pkt with io error
like August some time ago.

I have that Android/data/... folder in /storage/emulated/0

In AfterShock settings I have:
- Where to store files: External storage data directory

(despite this, it's in the internal storage, not in the SD card)

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada point (2:341/234.1)

On 28 Nov 2022 21:27 Carlos Navarro wrote to Tommi Koivula :

28 Nov 2022 20:16, you wrote to me:

It would be interesting to have a setting to keep a maximum
number of messages in the dupes folder. Or an option to delete
them all. In the meantime, I suppose you could use your favourite
file manager, browse to
/Android/data/com.avscorp.aftershock/files/dupemail and delete
(or move) the *.msg files. (Not tested)

I dont have that folder in this Samsung A52. No SDCard.

Anywhere else to search? I see now one problematic .pkt with io error
like August some time ago.

I have that Android/data/... folder in /storage/emulated/0

No aftershock files there in this phone.

In AfterShock settings I have:
- Where to store files: External storage data directory

I tried to move from internal to external and back but I cannot find aftershock files anywhere.

Seens to work but nags about one .pkt. I'd like to investigate that .pkt.

Tommi

--- AfterShock/Android 1.7.1
* Origin: ----. .---- .---- (2:221/1.911)

Hello, Tommi Koivula.
On 28/11/22 22:43 you wrote:

I have that Android/data/... folder in /storage/emulated/0

No aftershock files there in this phone.

Hmm... I suppose that you have also tried with several file manager apps, like Total Commander...

In AfterShock settings I have: - Where to store files: External
storage data directory

I tried to move from internal to external and back but I cannot
find aftershock files anywhere.

I have checked this, works for me. If I move to internal, I cannot access the files. If I move back to external, they are again in the com.avscorp.aftershock folder in Android/data. I use the Simple File Manager app.

--
Carlos
--- Hotdoged/2.13.5/Android
* Origin: cyberiada mobile point (2:341/234.12)