@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
@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: 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
@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: 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
It seems to happen with your openxp points that have a bossnode using
BBBS?
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...
No idea why this happens, it's weird.
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.
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...
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
@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?
--
../|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
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?
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?
like this.
-+- AfterShock/Android 1.6.8
+ Origin: ................................. (2:221/6.60)
I have now switched over to TRMB or this echo.
Or.. maybe Al @TRMB fixed something in the meantime?
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?
I was having that same issue as JD in my Aftershock test point.
Can you post again in FIDOTEST with your TRMB point?
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.
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! :/
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
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
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
your latest test message in FidoTest gives the problem again. obviously, I cannot reply there and have sent you a screenshot via Telegrams
I've copied the message here.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.
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.
Hi John,Fantastic, thanks Rudi!
I'm now talking about this with Anatoly, as soon i have more news i let you know...
Greetings,
Rudi
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..
It doesn't have those ASCII 10 (LF) that Aftershock doesn't seem to like.
[...]
Can you post again in FIDOTEST with your TRMB point?
After this message is posted, there will be one in FIDOTEST
too! ;)
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.....
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
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?
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. :/
BTW, I couldn't reply to this message of yours with Aftershock. It has no MSGID.
BTW, I couldn't reply to this message of yours with Aftershock. It has no MSGID.
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
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
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?
I have received confirmation that the HPT tosser strips those LF chars.
Another mystery solved ':-)
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 44:57:24 |
Calls: | 209 |
Calls today: | 1 |
Files: | 5,441 |
Messages: | 224,018 |