a few chars<star> origin: a text line
So I had a message (in another echo), that I went to reply to, but I couldnt quote the message.
It was long these lines:
###
a few chars<star> origin: a text line
message paragraph that ran over several lines
<triple dash> and a text line
<star> Origin: normal origin line.
###
You can translate <star> to * and <triple dash> as appropriate.
The first <star> origin was on the boundary (ie: no space before the *), and the quote text only let me quote "> a few chars", not "message paragraph...". (Infact "message paragraph" was not in the quote window at all.
While I know that <star> Origin should be the last thing on the message, in this case it was not proceeded with a space, and there was more text lines after it before the triple dash.
I tested both slyedit and fseditor and both exhibited the same.
I'm wondering if you can do some more validation that the first <star> origin is not the end of the text?
The separator used while importing message text is the tear-line: "<NL>--- " or "<NL>---<NL>" where <NL> is CR, LF, or CRLF.
Take a look at the original message using smbutil or the 'H' operator command from the "Reading" prompt. How many data fields (aka dfields) are listed and what are their lengths?
"body". You can only quote the *body* text of a message.
"body". You can only quote the *body* text of a message.
That I thought - my point being, for this message, the body of the
message ended up in the tail. I thought because of the "asterisk
Origin" beginning on new line.
smbutil r19 tqw_sug shows this:
###
Date : Thu Nov 21 2019 09:14 am UTC-5:00
2 (Linux/64)
X Origin: Stellar Darkness BBS, Toronto, Canada (1337:3/118)
The separator used while importing message text is the tear-line:
"<NL>--- " or "<NL>---<NL>" where <NL> is CR, LF, or CRLF.
remember, too, that in FTN tear lines are optional... the spec does
not say they are mandatory... in fact, all posts from my BBS were
without tearlines since the '90s at least ;)
---
Synchronet The SouthEast Star Mail HUB - SESTAR
On 11-21-19 19:05, Rampage wrote to Digital Man <=-
remember, too, that in FTN tear lines are optional... the spec does not say they are mandatory... in fact, all posts from my BBS were without tearlines since the '90s at least ;)
)\/(ark^^^
---
Re: Message Editor
By: Digital Man to Alterego on Thu Nov 21 2019 14:14:45
The separator used while importing message text is the tear-line: "<NL>--- " or "<NL>---<NL>" where <NL> is CR, LF, or CRLF.
remember, too, that in FTN tear lines are optional... the spec does not say they are mandatory... in fact, all posts from my BBS were without tearlines since the '90s at least ;)
Re: Message Editor
By: Digital Man to Alterego on Thu Nov 21 2019 02:14 pm
Take a look at the original message using smbutil or the 'H' operator command from the "Reading" prompt. How many data fields (aka dfields) are listed and what are their lengths?
header offset 002420h
header length 385
number 19
thread_id 19
thread_first 20
data offset 007000h
data field[0] TEXT_BODY, offset 0, length 17
data field[1] TEXT_TAIL, offset 17, length 438
IE: "Tail" is 438 bytes...
"body". You can only quote the *body* text of a message.
That I thought - my point being, for this message, the body of the message ended up in the tail. I thought because of the "asterisk Origin" beginning on new line.
smbutil r19 tqw_sug shows this:
###
Date : Thu Nov 21 2019 09:14 am UTC-5:00
2 (Linux/64)
X Origin: Stellar Darkness BBS, Toronto, Canada (1337:3/118)
anyone would be agreeable towards creating an area for virtualization related ...
YYY Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
X Origin: Stellar Darkness BBS, Toronto, Canada (1337:3/118)
###
(I've changed asterisk to "X", and dash to "Y" so that nothing messes with this
message. "..." indicates I've truncated the middle of the message.)
The separator used while importing message text is the tear-line:
"<NL>--- " or "<NL>---<NL>" where <NL> is CR, LF, or CRLF.
remember, too, that in FTN tear lines are optional... the spec does
not say they are mandatory... in fact, all posts from my BBS were
without tearlines since the '90s at least ;)
---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR
Since when do tear lines look like this in Fidonet?
The "--- " is not the
same as the "-- \n" in Internet emails.
Put the signature before the tear line or ommit the tear line
altogether.
2. Tear Line
This line is near the end of a message and consists of three
dashes (---) followed by an optional program specifier.
This is used to show the first program used to add Echomail
compatible control information to the message. The tear line
generated by Conference Mail looks like:
--- <a small product-specific banner>
http://ftsc.org/docs/fts-0004.001
remember, too, that in FTN tear lines are optional... the spec does
not say they are mandatory... in fact, all posts from my BBS were
without tearlines since the '90s at least ;)
)\/(ark
---^^^
Hmm, looks like a tearline to me. :P
remember, too, that in FTN tear lines are optional... the spec does
not say they are mandatory... in fact, all posts from my BBS were
without tearlines since the '90s at least ;)
Sure and SBBSecho supports that too.
Was there a space before the start ("X") on that first Origin line? If os, then that's a malformed echomail message. It should not have multiple origin lines.
On 2019 Nov 22 09:31:42, you wrote to Rampage:
remember, too, that in FTN tear lines are optional... the spec does
not say they are mandatory... in fact, all posts from my BBS were
without tearlines since the '90s at least ;)
Sure and SBBSecho supports that too.
supports no tearlines when processing inbound messages or supports removing tearlines and their contents completely from local messages being scanned out?
Re: Message Editor
By: Digital Man to Alterego on Fri Nov 22 2019 09:35 am
Was there a space before the start ("X") on that first Origin line? If os, then that's a malformed echomail message. It should not have multiple origin lines.
No there wasnt, that's why I posted this, thinking their may be a bug somewhere..
Although that makes me think - if somebody wants to mess with SBBS, do they just type asterisk, space, "Origin: " on a new line and that will mess with SBBSecho?
SBBSecho). Perhaps it's just a display issue? Maybe look closer at the message using smbutil r?
However, I'm wondering why it was imported with "most of the message"
in the TAIL instead of being in the BODY.
On 11-22-19 14:16, mark lewis wrote to Tony Langdon <=-
---^^^
Hmm, looks like a tearline to me. :P
note the use of the phrase" "were without"... plus this is not my old FD/RA/FE system... this is sbbs...
also note that i've not (yet?) hacked sbbsecho to remove tearlines and their contents when it scans messages out ;) ;) ;)
Re: Message Editor
By: Digital Man to Alterego on Fri Nov 22 2019 05:02 pm
SBBSecho). Perhaps it's just a display issue? Maybe look closer at the message using smbutil r?
Yes, I do look at it with smbutil.
So back to the original item I posted, the message renders fine - however when I quote it to reply, I can only quote what was before the asterisk "Origin:" line text.
On that original message, I agree, it was not a proper origin line, since there was no space between NL and asterisk.
However, I'm wondering why it was imported with "most of the message" in the TAIL instead of being in the BODY.
Anyay, I posted this, in case this might be something you want to diagnose... ...ëîå*
Was the message in question imported via SBBSecho or some other means? I
Re: Message Editor
By: Digital Man to Alterego on Mon Nov 25 2019 12:14 pm
Was the message in question imported via SBBSecho or some other means? I
Yes, I only use SBBS now.
I showed the smbutil output that showed the TEXT_TAIL was 438 bytes long (and the BODY was only 17 bytes).
Yeah, that implies that there was an origin line 17 bytes into the message text.
Re: Message Editor
By: Digital Man to Alterego on Mon Nov 25 2019 08:30 pm
Yeah, that implies that there was an origin line 17 bytes into the message text.
But there wasnt ?
The original line did NOT have a 'space asterisk Origin:' on a new line, it had 'asterisk Origin:' on a new line (with the appropriate space before and after the text "Origin:").
I thought the origin line was supposed to be "space asterisk Origin:" to be a valid origin line?
| Sysop: | MCMLXXIX |
|---|---|
| Location: | Prospect, CT |
| Users: | 325 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 12:57:09 |
| Calls: | 508 |
| Messages: | 219963 |