Hi John,

And this one is going through Tommi's system.

Is the R)eply problem occurring now?



--
../|ug

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

@MSGID: 2:221/1.58@fidonet fa2dfaf3

@PID: OpenXP/5.0.51 (Win32)

@CHRS: ASCII 1

@TZUTC: -0500

Hi John,

And this one is going through Tommi's system.

Is the R)eply problem occurring now?

--
../|ug

--- OpenXP 5.0.51
* Origin: (2:221/1.58)
SEEN-BY: 92/1 103/705 154/10 218/700 221/1 6 360 229/426 230/0 240/1120 SEEN-BY: 280/5003 292/854 301/1 113 335/364 341/66 423/81 5020/1042 5058/104 SEEN-BY: 92/1 920/1 69 0 92/0
@PATH: 221/1 301/1 920/1

This one there was no problem. The message you just sent to FidoTest gave the error

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

@MSGID: 2:221/1.58@fidonet fa2dfaf3

@PID: OpenXP/5.0.51 (Win32)

@CHRS: ASCII 1

@TZUTC: -0500

Hi John,

And this one is going through Tommi's system.

Is the R)eply problem occurring now?

R)eplying with visible kludges.

--
../|ug

--- OpenXP 5.0.51
* Origin: (2:221/1.58)
SEEN-BY: 221/1 6 360 230/0 240/1120 280/5003 292/854 301/1 335/364 341/66 SEEN-BY: 423/81 4500/1
@PATH: 221/1 6

'Tommi

--- AfterShock/Android 1.6.8
* Origin: ................................. (2:221/6.60)

Hi August,

@MSGID: 2:221/1.58@fidonet fa2dfaf3

@PID: OpenXP/5.0.51 (Win32)

@CHRS: ASCII 1

@TZUTC: -0500

Hi John,

And this one is going through Tommi's system.

Is the R)eply problem occurring now?

No, this one is ok.

It seems to happen with your openxp points that have a bossnode using BBBS?

--
../|ug

--- OpenXP 5.0.51
* Origin: (2:221/1.58)
SEEN-BY: 221/1 6 360 230/0 240/1120 280/5003 292/854 301/1 335/364 341/66 SEEN-BY: 341/200 234 423/81 4500/1
@PATH: 221/1 6 341/66 234

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

Hi Carlos,

It seems to happen with your openxp points that have a bossnode using
BBBS?

With BBBS this should be no problem this would be tested into the past...otherway would be a mis config into his BBBS settings mebay...

Greetings,
Rudi

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

07 Mar 2022 10:11, you wrote to me:

It seems to happen with your openxp points that have a bossnode
using BBBS?

With BBBS this should be no problem this would be tested into the past...otherway would be a mis config into his BBBS settings mebay...

I was just wondering. I don't mean it's BBBS's or TRMB's fault. No idea why this happens, it's weird.

Carlos

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

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...

Carlos

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

Hello Carlos Navarro!

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

07 Mar 2022 10:11, you wrote to me:

It seems to happen with your openxp points that have a bossnode
using BBBS?

With BBBS this should be no problem this would be tested into the
past...otherway would be a mis config into his BBBS settings mebay...

I was just wondering. I don't mean it's BBBS's or TRMB's fault. No idea why this happens, it's weird.

I post to TRMB in a few other echos. Can you tell if the same
problem persists for them?

Or.. I can temporarily switch over to TRMB for *this* echo and
see if the problem persists.

YES.. I will do THAT. Then, I will announce a test message
here for that purpose.


--
../|ug

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

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: My Westcoast Point (1:153/757.21)

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 find it hard to believe that HPT would tamper intransit mail..

Carlos

'Tommi

--- AfterShock/Android 1.6.8
* Origin: ................................. (2:221/6.60)

@MSGID: 1:153/757.21@fidonet fa360cf0

@REPLY: 2:341/234 62266309

@PID: OpenXP/5.0.51 (Win32)

@CHRS: ASCII 1

@TZUTC: -0500

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?

like this.

--
../|ug

--- OpenXP 5.0.51
* Origin: My Westcoast Point (1:153/757.21)
SEEN-BY: 134/100 153/0 105 135 757 7715 154/10 218/840 221/1 6 301/1 335/364 SEEN-BY: 341/66 4500/1
@PATH: 153/757 221/6

'Tommi

--- AfterShock/Android 1.6.8
* Origin: ................................. (2:221/6.60)

Hi August,

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?

This one is ok.

It does not have LF's (Ascii 10)

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

I have now switched over to TRMB or this echo.

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

This one is ok.

It does not have LF's (Ascii 10)

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

Hmmmm.. then why was one other Aftershock user getting that
"unable to reply ..due to missing MSGID" error?

At that time, it seemed to only occur with areas served with
TRMB.

Or.. maybe Al @TRMB made an adjustment in the meantime?

--
../|ug

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

I have now switched over to TRMB or this echo.

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

like this.

[...]

-+- AfterShock/Android 1.6.8
+ Origin: ................................. (2:221/6.60)

Hmmm.. then how come JD was having that "unable to reply, due
to missing MSGID" problem?

Or.. maybe Al @TRMB fixed something in the meantime?


--
../|ug

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

I have now switched over to TRMB or this echo.

Or.. maybe Al @TRMB fixed something in the meantime?

No, I am unsure of the issue being talked about here or if there is anything I should or might do about it.

BTW, I see a dupelicate message here with a different (slightly) MSGID.

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

07 Mar 2022 15:30, you wrote to me:

Hmmmm.. then why was one other Aftershock user getting that
"unable to reply ..due to missing MSGID" error?

I was having that same issue as JD in my Aftershock test point.

At that time, it seemed to only occur with areas served with
TRMB.

Or.. maybe Al @TRMB made an adjustment in the meantime?

No idea. Now there are no LF's and it's working ok. Did you change anything in your OpenXP?

Can you post again in FIDOTEST with your TRMB point?

Carlos

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

I was having that same issue as JD in my Aftershock test point.

[...]

Can you post again in FIDOTEST with your TRMB point?

After this message is posted, there will be one in FIDOTEST
too! ;)

--
../|ug

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

Hello Alan!

Or.. maybe Al @TRMB fixed something in the meantime?

No, I am unsure of the issue being talked about here or if there is anything I should or might do about it.

At least one person was detecting a problem that Aftershock was
having when replying to messages by me that have been sent to
your (boss) system. But it wasn't happening when my messages
when through another boss system (Tommi's).

BTW, I see a dupelicate message here with a different (slightly) MSGID.

Dunno about that! :/
--
../|ug

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

No, I am unsure of the issue being talked about here or if there is
anything I should or might do about it.

At least one person was detecting a problem that Aftershock was
having when replying to messages by me that have been sent to
your (boss) system. But it wasn't happening when my messages
when through another boss system (Tommi's).

That is unexpected. Let me know if there is something I can do to test and find out if the problem was caused here.

There have been no issues here that I am aware of.

BTW, I see a dupelicate message here with a different (slightly) MSGID.

Dunno about that! :/

It's a harmless dupe. I will reply quoting the kludges in a minute.

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

I have now switched over to TRMB or this echo.

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

This one is ok.

It does not have LF's (Ascii 10)

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

Hmmmm.. then why was one other Aftershock user getting that
"unable to reply ..due to missing MSGID" error?

At that time, it seemed to only occur with areas served with
TRMB.

Or.. maybe Al @TRMB made an adjustment in the meantime?

--
../|ug

@SEEN-BY: 153/757 0
@PATH: 153/757
@MSGID: 1:153/757.21@fidonet fa360db9
@REPLY: 2:341/234.1234 622668a4
@PID: OpenXP/5.0.51 (Win32)
@CHRS: ASCII 1
@TZUTC: -0500

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

I have now switched over to TRMB or this echo.

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

like this.

[...]

-+- AfterShock/Android 1.6.8
+ Origin: ................................. (2:221/6.60)

Hmmm.. then how come JD was having that "unable to reply, due
to missing MSGID" problem?

Or.. maybe Al @TRMB fixed something in the meantime?

--
../|ug

@SEEN-BY: 153/757 0
@PATH: 153/757
@MSGID: 1:153/757.21@fidonet fa360dc9
@REPLY: 2:221/6.60 62266907
@PID: OpenXP/5.0.51 (Win32)
@CHRS: ASCII 1
@TZUTC: -0500

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

Hello Alan!

Or.. maybe Al @TRMB fixed something in the meantime?

No, I am unsure of the issue being talked about here or if there is
anything I should or might do about it.

At least one person was detecting a problem that Aftershock was
having when replying to messages by me that have been sent to
your (boss) system. But it wasn't happening when my messages
when through another boss system (Tommi's).

BTW, I see a dupelicate message here with a different (slightly) MSGID.

Dunno about that! :/
--
../|ug

August,
your latest test message in FidoTest gives the problem again. obviously, I cannot reply there and have sent you a screenshot via Telegrams

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

your latest test message in FidoTest gives the problem again. obviously, I cannot reply there and have sent you a screenshot via Telegrams

You cannot reply to the message at all?

If you can reply to the problematic message with kludges it may help to determine the issue.

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

your latest test message in FidoTest gives the problem again. obviously, I
cannot reply there and have sent you a screenshot via Telegrams

You cannot reply to the message at all?

If you can reply to the problematic message with kludges it may help to determine the issue.

I've copied the message here.

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

Hello Alan!

BTW, I see a dupelicate message here with a different (slightly) MSGID.

Dunno about that! :/

It's a harmless dupe. I will reply quoting the kludges in a minute.

Thanks. Saw those. Each does look similar, but the body
contained a slightly different (re-edited) message. One
version went to your boss system, and the other went to Tommi's
system.

--
../|ug

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

Hi John,

I'm now talking about this with Anatoly, as soon i have more news i let you know...

Greetings,
Rudi

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

Hi John,

I'm now talking about this with Anatoly, as soon i have more news i let you know...

Greetings,
Rudi

Fantastic, thanks Rudi!


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

Hi August,

[...]

Can you post again in FIDOTEST with your TRMB point?

After this message is posted, there will be one in FIDOTEST
too! ;)

The one in FIDOTEST didn't arrive well for Aftershock.

However this one I'm replying to is ok.

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

Do you have different configurations in openxp for these two echo? Or did you entered these messages in a different way?

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

07 Mar 2022 22:16, you wrote to me:

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 find it hard to believe that HPT would tamper intransit mail..

You're right, it may be August's OpenXP or something.
Some of his messages posted through Al's system have LF's in the body (including kludges), but others don't :-S

Anyway, I think that this should be fixed in Aftershock - it should ignore ASCII 10 chars, as per FTS-1.

Carlos

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

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)

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.....

Ok, thanks for confirming this. I hope Anatoly can fix it.

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

Carlos

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

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
--- AfterShock/Android 1.6.8
* Origin: Firecat Mobile (4:920/69.1)

Hello Carlos Navarro!

** On Tuesday 08.03.22 - 21:12, Carlos Navarro wrote to August Abolins:

The one in FIDOTEST didn't arrive well for Aftershock.

However this one I'm replying to is ok.

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

Weird.

Do you have different configurations in openxp for these two echo? Or did you entered these messages in a different way?

No and no.

I might "reflow" the quoted part of a message that I am
replying to , but sometimes not. Usually, OpenXP auto wraps a
line like in this paragraph.
--
../|ug

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

Hello John Dovey!

** On Tuesday 08.03.22 - 17:29, John Dovey wrote to Rudi Timmermans:

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)

I had no problem replying to this message.

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

There is some odd inconsistent behaviour happening between
Aftershock users. :/

--
../|ug

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

There is some odd inconsistent behaviour happening between
Aftershock users. :/

Just to be clear, after all the to and fro it is now apparent that it is not Aftershock that is causing the problem, but that a mod will be made to Aftershock to deal with the problem that other software creates.

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

Hi Carlos,

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....

Greetings,
Rudi

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

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)

13 mar 2022 09:56, Carlos Navarro -> August Abolins

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.

...

I just checked that this issue has been fixed in 1.6.10.

Carlos

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