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
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.
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.
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.
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?
\r and \n? Maybe it's in a spec somewhere?
\r and \n? Maybe it's in a spec somewhere?
Carriage return codes? What is \r vs \n ?
That came back correctly for me on WWIV.
\r and \n? Maybe it's in a spec somewhere?
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?
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.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,041 |
Nodes: | 15 (0 / 15) |
Uptime: | 244:50:29 |
Calls: | 500,341 |
Calls today: | 14 |
Files: | 95,205 |
D/L today: |
7,266 files (1,390M bytes) |
Messages: | 465,872 |