Hey John..

This one is processed via my boss who is using BBBS.

Does R)eply cooperate?




--
../|ug

--- OpenXP 5.0.51
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

Re: an aftershock test for JD
By: August Abolins to John Dovey on Sun Mar 06 2022 17:25:00

Hey John..

This one is processed via my boss who is using BBBS.
Does R)eply cooperate?

Replying from within SBBS works perfectly.

JD

John Dovey
===
* El Gato de Fuego (The Fire Cat) 4:920/69 * Pedasi, Panama

... I predict that today will be remembered until tomorrow!
--- SBBSecho 3.14-Win32
* Origin: The Cat of Fire aka El Gato de Fuego II (4:920/69)

Glad to see you, August!

Hey John..
This one is processed via my boss who is using BBBS.
Does R)eply cooperate?
--
../|ug

Hi August.
This one gives the problem that we were looking for in Aftershock. No problem replying in TG.Hi August.This one gives the problem that we were looking for in Aftershock. No problem replying in TG.
File: photo_2022-03-06_17-33-36.jpg.
Error: 500 read timeout

*** [Netmail-to-Telegram address: 474405162@2:460/256]

... Tag, you are IT!
--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

@MSGID: 2:460/256 00000ac2

@REPLY: 1:153/757.21@fidonet fa2dfae7

@PID: tg_BBS_v0.7.1

@TZUTC: 0300

@CHRS: cp866 2

@TGUID: 474405162

@REPLYTO: 2:460/256 474405162

@RealName: John Dovey 4:920/1

Glad to see you, August!

Hey John..
This one is processed via my boss who is using BBBS.
Does R)eply cooperate?
--
../|ug

Hi August.
This one gives the problem that we were looking for in Aftershock. No problem replying in TG.Hi August.This one gives the problem that we were looking for in Aftershock. No problem replying in TG. File: photo_2022-03-06_17-33-36.jpg. Error: 500 read timeout

*** [Netmail-to-Telegram address: 474405162@2:460/256]

... Tag, you are IT!
--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)
SEEN-BY: 30/0 80/1 92/1 103/705 154/10 218/700 221/1 6 229/426 240/1120 SEEN-BY: 280/464 5555 301/1 113 123 221 812 341/66 460/58 256 1124 5858 SEEN-BY: 712/848 4600/140 5020/1042 5054/30 5058/104 153/757 90/1 92/1 920/1 SEEN-BY: 920/69 0 92/0
@PATH: 460/256 58 301/1 920/1

OK, this is odd. It duplicated my message and gave a "Error 500* message...

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

Hi All...

Maybe aftershock doesn't like seeing a point address in the MSGID?

Ciao!
/|ug (https://t.me/aabolins)

--- Want fido for iOS/MacOS/Android/Win/Linux? Info=https://shrtco.de/tpJ9yV
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

06 Mar 2022 17:25, you wrote to John Dovey:

Hey John..

This one is processed via my boss who is using BBBS.

Does R)eply cooperate?

Your message has newlines as CRLF instead of just CR. That may be what is confusing Aftershock.

Carlos

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

Hello Carlos!

** On Monday 07.03.22 - 20:50, you wrote to me:

Does R)eply cooperate?

Your message has newlines as CRLF instead of just CR. That
may be what is confusing Aftershock.

HERE is another test message. What does this one do?

--
../|ug

--- OpenXP 5.0.51
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

07 Mar 2022 18:19, you wrote to me:

Does R)eply cooperate?

Your message has newlines as CRLF instead of just CR. That
may be what is confusing Aftershock.

HERE is another test message. What does this one do?

It doesn't cooperate.

This message also had CR+LF at the end of every line including kludges. Aftershock should ignore LF chars (ASCII 10), but it doesn't and gets confused, displaying the kludges in the body text (and ignoring the MSGID)

Carlos

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

07 Mar 2022 18:19, you wrote to me:

Does R)eply cooperate?

Your message has newlines as CRLF instead of just CR. That
may be what is confusing Aftershock.

HERE is another test message. What does this one do?

It doesn't cooperate.

This message also had CR+LF at the end of every line including kludges. Aftershock should ignore LF chars (ASCII 10), but it doesn't and gets confused, displaying the kludges in the body text (and ignoring the MSGID)

Carlos

Hi Carlos,
I see Rudi has undertaken to get Aftershock to ignore the Chr$(10)
While it's not my business,it would probably be a good idea to track down the condition that made the characters get inserted in the first place?

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

I see Rudi has undertaken to get Aftershock to ignore the Chr$(10)
While it's not my business,it would probably be a good idea to track down the condition that made the characters get inserted in the first place?

Yes, messages should not change in transit. If they begin with CRLF they should stay that way. It creates issues when message change in transit.

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