Hi Carlos,

BTW, I couldn't reply to this message of yours with Aftershock. It has no MSGID.

I just have checked other echomail send here from me into AfterShock and that i could reply on, so i'm shure somewhere the MSGID where stripped out of the echomails....

Greetings,
Rudi

--- DB4/Li March 03 2022
* Origin: Light Station (2:292/140)

Hi John,

Hi Carlos,

It doesn't have those ASCII 10 (LF) that Aftershock doesn't seem to
like.

Oh yes indeed ASCII 10 (LF) that dont like AfterShock add all there is no
support for that into AfterShock.....

Greetings,
Rudi

--- DB4/Li March 03 2022
* Origin: Light Station (2:292/140)
SEEN-BY: 80/1 92/1 103/705 154/10 218/700 221/1 6 240/1120 261/38 292/140
854 SEEN-BY: 292/8125 301/1 113 335/364 341/66 410/9 5020/1042 5058/104
92/1 920/1 SEEN-BY: 920/69 0 92/0
@PATH: 292/140 854 301/1 920/1

I had no problem replying to this message.

JD

Did it arrive to you with MSGID? You didn't quote kludges.

I've just installed latest 1.6.8 (instead of the 1.6.8 alpha5 version that Rudi gave me some time ago) in another device, and still cannot reply to messages without MSGID.

Can you reply to Jason Bock's message in FIDOTEST dated 9 Mar 22 00:54 ?

Carlos
--- AfterShock/Android 1.6.8
* Origin: old tablet test point (2:341/234.12345)

Hi John,

Hi Carlos,

It doesn't have those ASCII 10 (LF) that Aftershock doesn't seem to
like.

Oh yes indeed ASCII 10 (LF) that dont like AfterShock add all there is
no support for that into AfterShock.....

Greetings,
Rudi

--- DB4/Li March 03 2022
* Origin: Light Station (2:292/140)
SEEN-BY: 80/1 92/1 103/705 154/10 218/700 221/1 6 240/1120 261/38
292/140 854 SEEN-BY: 292/8125 301/1 113 335/364 341/66 410/9 5020/1042
5058/104 92/1 920/1 SEEN-BY: 920/69 0 92/0
@PATH: 292/140 854 301/1 920/1

I had no problem replying to this message.

JD

Did it arrive to you with MSGID? You didn't quote kludges.

I've just installed latest 1.6.8 (instead of the 1.6.8 alpha5 version that Rudi gave me some time ago) in another device, and still cannot reply to messages without MSGID.

Can you reply to Jason Bock's message in FIDOTEST dated 9 Mar 22 00:54 ?

Carlos

Just tried to reply to Jason's message and got the msgid error.

John
--- AfterShock/Android 1.6.8
* Origin: Firecat Mobile (4:920/69.1)

Hello Carlos Navarro!

** On Monday 07.03.22 - 20:54, Carlos Navarro wrote to Rudi Timmermans:

07 Mar 2022 20:19, I wrote to you:

No idea why this happens, it's weird.

Just checked some .PKTs and the difference I see is that those messages that Aftershock doesn't display properly have CRLF instead of just CR.

I guess that Tommi's system filters out those LF's...

I have now switched over to TRMB or this echo.

How does this one look and behave for the Aftershock users?

--
../|ug

--- OpenXP 5.0.51
* Origin: (2:221/1.58)

Hi August,

I have now switched over to TRMB or this echo.

How does this one look and behave for the Aftershock users?

It looks good here !

---
Best regards,
Rudi Timmermans.
--- AfterShock/Android 1.6.8
* Origin: Light Station (2:292/854.140)

Hi August,

I have now switched over to TRMB or this echo.

How does this one look and behave for the Aftershock users?

Ok, but...

--- OpenXP 5.0.51
* Origin: (2:221/1.58)

... it wasn't sent from TRMB.

Carlos
--- AfterShock/Android 1.6.8
* Origin: Costa Blanca, Spain (2:341/234.1234)

On 11.03.2022 16:42, Carlos Navarro wrote:

AA> I have now switched over to TRMB or this echo.

AA> How does this one look and behave for the Aftershock users?

Ok, but...

AA> --- OpenXP 5.0.51
AA> * Origin: (2:221/1.58)

.. it wasn't sent from TRMB.

The message went first to my badecho, August unsubscribed before sending. ;)

'Tommi

---
* Origin: rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)

Hello Carlos!

** On Friday 11.03.22 - 15:42, you wrote to me:

I have now switched over to TRMB or this echo. How does
this one look and behave for the Aftershock users?

Ok, but...

--- OpenXP 5.0.51
* Origin: (2:221/1.58)

... it wasn't sent from TRMB.

True.. that one slipped through before I actually switched.

But, meanwhile the REAL reason for the problem seems to have
shown itself, and nothing to do with OpenXP and/or which BBS my
messages come from, right?

--
../|ug

--- OpenXP 5.0.51
* Origin: My Westcoast Point (1:153/757.21)

11 Mar 2022 19:34, you wrote to me:

But, meanwhile the REAL reason for the problem seems to have
shown itself, and nothing to do with OpenXP and/or which BBS my
messages come from, right?

It's a bug in Aftershock, but it is somewhat related to OpenXP.

I've set up a test point with OpenXP. I see it does insert CRLF instead of CR only, not only in the message's visible text, but also in the kludge lines.

Aftershock has issues with:

- messages without MSGID
- messages with CRLF in kludges

If a message has CRLF in the kludges it is not displayed properly by Aftershock: it shows them in the visible body text and ignores them - it "thinks" it has no MSGID.

Aftershock doesn't let you reply a message without MSGID when you tap on it from the echo's message list. However, if the previous message you viewed did have MSGID, and then you move (swipe to) one without MSGID (without going back to the list), it "doesn't forget" the previous one's kludges and lets you reply to it (though it's not quoted properly, and the reply has no REPLY kludge)

If you have no issues replying from Aftershock to some message generated by OpenXP, it's because some node removed the LFs from its kludge lines. (As nowadays messages can take different paths, sometimes it happens, sometimes it doesn't.)

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234.1)

08 Mar 2022 21:57, you wrote to me:

It doesn't have those ASCII 10 (LF) that Aftershock doesn't seem
to like.

Oh yes indeed ASCII 10 (LF) that dont like AfterShock add all there is
no support for that into AfterShock.....

I hope that Anatoly can fix this. I don't know how Aftershock works, but it shouldn't be difficult to just ignore/remove all 0x0A characters from the text of imported messages when tossing them.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234.1)

09 Mar 2022 09:09, you wrote to me:

BTW, I couldn't reply to this message of yours with Aftershock. It
has no MSGID.

This is wierd as i dont change anything here still using Dbridge.... Sounds like a other system mebay strip the MSGID not shure about
this....

That's very weird, indeed.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234.1)

09 Mar 2022 12:35, you wrote to me:

BTW, I couldn't reply to this message of yours with Aftershock. It
has no MSGID.

I just have checked other echomail send here from me into AfterShock
and that i could reply on, so i'm shure somewhere the MSGID where
stripped out of the echomails....

Do you have backups of your outbound PKTs? Just to make sure it didn't happen in your system.

This is the path for that message from your system to mine:
292/140 854 335/364 221/6 341/66 234

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234.1)

Hi Carlos,

Do you have backups of your outbound PKTs? Just to make sure it didn't happen in your system.

This is the path for that message from your system to mine:
292/140 854 335/364 221/6 341/66 234

I have test this with my hub i have on my AfterShock a point number so i send it to my hub and then i poll with my AfterShock point number so i'm shur it dont happens here or on my hub system... i dont have any backup sorry...

Greetings,
Rudi

--- DB4/Li March 10 2022
* Origin: Light Station (2:292/140)

Do you have backups of your outbound PKTs? Just to make sure it
didn't happen in your system. This is the path for that message
from your system to mine: 292/140 854 335/364 221/6 341/66 234

I have test this with my hub i have on my AfterShock a point
number so i send it to my hub and then i poll with my AfterShock
point number so i'm shur it dont happens here or on my hub
system... i dont have any backup sorry...

Anyway I haven't seen it happen again. All your messages after that one have their MSGID...


--
Carlos
--- Hotdoged/2.13.5/Android
* Origin: Costa Blanca, Spain (2:341/234.12)

Hi Carlos,

Anyway I haven't seen it happen again. All your messages after that one have their MSGID...

Ok good, about this fix i'm talking with Anatoly to fix that, but we dont know when it would be fixed yet. I keep everyone posted here...

Greetings,
Rudi

--- DB4/Li March 10 2022
* Origin: Light Station (2:292/140)

13 Mar 2022 09:56, I wrote to you:

If you have no issues replying from Aftershock to some message
generated by OpenXP, it's because some node removed the LFs from its kludge lines. (As nowadays messages can take different paths,
sometimes it happens, sometimes it doesn't.)

I have received confirmation that the HPT tosser strips those LF chars.

Another mystery solved ':-)

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234)

I have received confirmation that the HPT tosser strips those LF chars.

Another mystery solved ':-)

Awesome. Thanks Carlos

--- AfterShock/Android 1.6.8
* Origin: Firecat Mobile (4:920/69.1)