TID: FMail-W32 2.0.1.4
TZUTC: 0100
CHRS: UTF-8 4
MSGID: 2:341/234.1 622db1d9
REPLY: 1:153/757.21@fidonet fa5646df
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
 * Origin: Costa Blanca, Spain (2:341/234.1)
SEEN-BY: 1/123 15/0 90/1 105/81 106/201 114/705 120/340 123/120 131
SEEN-BY: 129/305 330 331 153/250 757 7715 154/10 218/700 840 220/70
SEEN-BY: 221/1 6 226/17 30 227/114 229/110 206 317 424 426 428 550
SEEN-BY: 229/664 700 240/5832 250/5 8 266/512 267/800 282/1038 298/25
SEEN-BY: 301/1 305/3 317/3 320/219 322/757 335/364 341/66 200 234
SEEN-BY: 342/200 396/45 633/280 712/848 770/1 4500/1
PATH: 341/234 66 221/6 218/840 770/1 317/3 229/426