I tried sending an areafix with

%LIST
%HELP

and only the first command is fulfilled, the second returns unknown echo.

altere reported the problem with 21:1/100 so I thought I'd try it out on 21:2/100 and we're both having the same issue.

Even if I leave a blank link, that line also reports unknwon echo.

Obviously this is a problem if someone wants to subscribe to a subset of
echoes since they'd only be able to do one at a time.

We're both running synchronet, would be interesting to see if the problem exists sending areafix from a Mystic board.

Thanks,
--- SBBSecho 3.11-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

On 26 Oct 2020 at 09:54p, Nigel Reed pondered and said...

I tried sending an areafix with

%LIST
%HELP

and only the first command is fulfilled, the second returns unknown echo.

We're both running synchronet, would be interesting to see if the problem exists sending areafix from a Mystic board.

It's working OK for Mystic to Mystic I think. I tested from 1/101 to 1/100

[snip]

From: AREAFIX
To: Paul Hayton
Subj: AREAFIX response
Date: 10/27/20 16:19
Base: Netmail (fsxNet)

Your AREAFIX request has been processed

Command: %LIST
Result: List of all areas:
FSX_GEN General Chat
FSX_MYS Mystic BBS Support/Dev
FSX_BOT fsxNet BOTS
FSX_CRY Cryptographics
FSX_BBS BBS Support/Dev
FSX_DAT InterBBS Data
FSX_MAG Magicka BBS Support/Dev
FSX_ENG ENiGMA 1/2 BBS Support/Dev
FSX_HAM Amateur Radio
FSX_ESP Espanol General Chat
FSX_NET fsxNet Network Ops/Planning
FSX_TST fsxNet Test Arena
FSX_ADS BBS and NETwork Ads
FSX_STA Echomail + Network Stats
FSX_FIL File Announcements

Command: %HELP
Result: Help included at end of message

.------------------------.
| fsxNet - AreaFix Help |----------------------------------------------------- `------------------------'


What is AreaFix?
----------------

AreaFix is a automated response system which provides echomail nodes the

[snip]

To get those errors Mystic is seeing something else in the text you are
sending that may exist prior to the command you're putting on line 2,3 etc.?

Just a guess..

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

It's working OK for Mystic to Mystic I think. I tested from 1/101 to 1/100

To get those errors Mystic is seeing something else in the text you are sending that may exist prior to the command you're putting on line 2,3 etc.?

I'm wondering if a WWIV or other non-synchronet/non-mystic bbs node can test this and let us know as well. I'd just like to know who to officially report it to for a fix as my fido hub works as expected which is neither synch or mystic.

-altere
--- SBBSecho 3.11-Linux
* Origin: Athelstan - athelstan.org (21:1/113)

On 26 Oct 2020 at 11:01p, Altere pondered and said...

I'm wondering if a WWIV or other non-synchronet/non-mystic bbs node can test this and let us know as well. I'd just like to know who to
officially report it to for a fix as my fido hub works as expected which is neither synch or mystic.

Fair enough... someone about should be able to I think. I know Apam is
playing with WWIV and so is Doug.. :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

RE: Re: Bug with mystic areafix processor
BY: Avon(21:1/101)

Fair enough... someone about should be able to I think. I know Apam is playing with WWIV and so is Doug.. :)

Areafix worked last time I did it, though testing with:

%LIST
%HELP

To be sure.

What message editor is being used that it fails on? My guess would be it's sending \r\n line endings, and mystic is expecting just \r leaving \n at the start of the next line... but that's a wild stab in the dark.

Andrew


--- WWIV 5.5.0.development
* Origin: The Barbed Hook - telnet://barbedhook.ddns.net:2323/ (21:1/182)

Re: Re: Bug with mystic areafix processor
By: Apam to Avon on Tue Oct 27 2020 02:57 pm

Yup, it seems mystic is broken...

I sent an areafix to 21:2/100, with
%LIST
%UNLINKED
%HELP
### (three dashes)


and got this back:

Command: %UNLINKED
Result: Unknown echo area

Command: %HELP
Result: Unknown echo area

Command: ---
Result: Unknown echo area

...δεσ∩

... An idea that is dangerous is unworthy of being called an idea at all.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

RE: Re: Bug with mystic areafix processor
BY: Apam #1 @1

Areafix worked last time I did it, though testing with:

%LIST
%HELP

To be sure.

That came back correctly for me on WWIV.

Andrew

--- WWIV 5.5.0.development
* Origin: The Barbed Hook - telnet://barbedhook.ddns.net:2323/ (21:1/182)

Apam wrote:

RE: Re: Bug with mystic areafix processor
BY: Avon(21:1/101)

Fair enough... someone about should be able to I think. I know Apam is playing with WWIV and so is Doug.. :)

Areafix worked last time I did it, though testing with:

%LIST
%HELP

To be sure.

What message editor is being used that it fails on? My guess would be it's sending \r\n line endings, and mystic is expecting just \r leaving \n at the start of the next line... but that's a wild stab in the dark.

No, that doesn't appear to be the case.

bbs@bbs:/sbbs/bin$ hexdump -C /sbbs/temp/mail.out
00000000 25 4c 49 4e 4b 45 44 0a 25 48 45 4c 50 0a |%LINKED.%HELP.|


I have a script that is sending the areafix messages so I tried with \r\n and then with \r and no joy. Also \n for S&G.

Must be something else going on. Maybe someone can send a hexdump of a pre packaged areafix message or something?
--- SBBSecho 3.11-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

Nigel wrote:

bbs@bbs:/sbbs/bin$ hexdump -C /sbbs/temp/mail.out
00000000 25 4c 49 4e 4b 45 44 0a 25 48 45 4c 50 0a |%LINKED.%HELP.|

My bad, I had my 0a and 0d switched around. Now it's sending just \r and
works, but I feel that's still a bug. I'm pretty sure it should recognize both \r and \n? Maybe it's in a spec somewhere?
--- SBBSecho 3.11-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

RE: Re: Bug with mystic areafix processor
BY: Nigel Reed(21:2/101)

My bad, I had my 0a and 0d switched around. Now it's sending just \r and works, but I feel that's still a bug. I'm pretty sure it should
recognize both
\r and \n? Maybe it's in a spec somewhere?

Yeah, it's probably a bug. I was just taking a stab at what might have been wrong, guess I was pretty close :P

I don't know that there is a spec or not, FTN tends to use '\r' for line endings, but it can't hurt to be accomodating.

Andrew

--- WWIV 5.5.0.development
* Origin: The Barbed Hook - telnet://barbedhook.ddns.net:2323/ (21:1/182)

On 27 Oct 2020 at 05:39p, Apam pondered and said...

\r and \n? Maybe it's in a spec somewhere?

Carriage return codes? What is \r vs \n ?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

RE: Re: Bug with mystic areafix processor
BY: Avon(21:1/101)

\r and \n? Maybe it's in a spec somewhere?

Carriage return codes? What is \r vs \n ?

\r is a Carriage return, technically it moves the cursor to the start of the line

\n is a new line it moves the cursor down one.

Andrew


--- WWIV 5.5.0.development
* Origin: The Barbed Hook - telnet://barbedhook.ddns.net:2323/ (21:1/182)

BY: Apam(21:1/182)

That came back correctly for me on WWIV.

Glad to hear it. WWIV uses "\r\n" internally and jumps through hoops to make sure it sends it as just \r or \x8d\x0a for wrapped lines.



--- WWIV 5.6.0.development
* Origin: Mystic Rhythms BBS (21:2/115)

BY: Apam(21:1/182)

\r and \n? Maybe it's in a spec somewhere?

http://ftsc.org/docs/fts-0001.016 was what I used.



--- WWIV 5.6.0.development
* Origin: Mystic Rhythms BBS (21:2/115)

Re: Re: Bug with mystic areafix processor
By: Nigel Reed to Nigel Reed on Tue Oct 27 2020 01:02 am

Nigel wrote:

bbs@bbs:/sbbs/bin$ hexdump -C /sbbs/temp/mail.out
00000000 25 4c 49 4e 4b 45 44 0a 25 48 45 4c 50 0a
|%LINKED.%HELP.|

My bad, I had my 0a and 0d switched around. Now it's sending just \r and works, but I feel that's still a bug. I'm pretty sure it should recognize both \r and \n? Maybe it's in a spec somewhere?

The FidoNet specs say message paragraphs should end with a CR (\r) and linefeeds (\n) should be ignored. So the CR is required the LF is optional/superfluous.
--
digital man

Rush quote #37:
Ignorance and prejudice and fear go hand in hand
Norco, CA WX: 76.2°F, 13.0% humidity, 2 mph SE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

Digital wrote:

Re: Re: Bug with mystic areafix processor
By: Nigel Reed to Nigel Reed on Tue Oct 27 2020 01:02 am

Nigel wrote:

bbs@bbs:/sbbs/bin$ hexdump -C /sbbs/temp/mail.out
00000000 25 4c 49 4e 4b 45 44 0a 25 48 45 4c 50 0a
|%LINKED.%HELP.|

My bad, I had my 0a and 0d switched around. Now it's sending just \r and works, but I feel that's still a bug. I'm pretty sure it should recognize both \r and \n? Maybe it's in a spec somewhere?

The FidoNet specs say message paragraphs should end with a CR (\r) and linefeeds (\n) should be ignored. So the CR is required the LF is optional/superfluous.

This is one that needs to be fixed in Mystic then.
--- SBBSecho 3.11-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)