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

 AA> But, meanwhile the REAL reason for the problem seems to have
 AA> shown itself, and nothing to do with OpenXP and/or which BBS my
 AA> 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