Where I can find in the FTSC docs the meanings of the message attributes and the expected behaviour of the tosser when it has to process them?
Where I can find in the FTSC docs the meanings of the messageTry 'ftsc.org'
attributes and the expected behaviour of the tosser when it has
to process them?
Ok, before I missed the magic "Doc Search" field, and now I fond two documents,Where I can find in the FTSC docs the meanings of the message
attributes and the expected behaviour of the tosser when it has
to process them?
Try 'ftsc.org':/ I've looked in ftsc.org but I haven't found the right article,
so I'm asking here about the right one. :) Or do I have to bribe
someone with a pack of pink toilet paper? :P
But I still don't understand what a mail processor or tosser has to do when a message has the MSGLOCAL attribute set. :)
Hi! Fabio, On 03/22/2020 12:15 AM,you wrote to Ward Dossche:Thank you Paul, I'll do some tests! :)
But I still don't understand what a mail processor or tosser hasFrom experience I have found that _a_ tosser would -not- export a
to do when a message has the MSGLOCAL attribute set. :)
message without the LOC attribute being set. I now recall that I
was experimenting with the MPost utility... many moons ago. In
short: the LOC attribute must be _set_ in order to send the
subject message. NB. Do not confuse it with the LOCK attribute. Different beast. :)
But I still don't understand what a mail processor or tosser has
to do when a message has the MSGLOCAL attribute set. :)
But I still don't understand what a mail processor or tosser has
to do when a message has the MSGLOCAL attribute set. :)
From experience I have found that _a_ tosser would -not- export a
message without the LOC attribute being set. I now recall that I was experimenting with the MPost utility... many moons ago.
In short: the LOC attribute must be _set_ in order to send the subject message.
message toIn short: the LOC attribute must be _set_ in order to send the subject message.
It is rather strange. The Loc attribute is set on a locally created
differentiate it from a message received from another system. So what isthe
point of sending a message with the Loc attrubute set? The systemreceiving the
message will consider the message is created locally.
generally speaking, a message has the LOCAL attribute when the message[...]
From experience I have found that _a_ tosser would -not- export a
message without the LOC attribute being set. I now recall that I
was experimenting with the MPost utility... many moons ago.
In short: the LOC attribute must be _set_ in order to send the
subject message.
It is rather strange. The Loc attribute is set on a locally created message to differentiate it from a message received from another
system. So what is the point of sending a message with the Loc
attrubute set? The system receiving the message will consider the
message is created locally.
Interesting point: With checking the stored message format and theattributes
definition there in FTSC 0001 the Local attribute is NOT zeroed on export.Hmm.
I would have guessed, it's a local created message, but the attribute ispurged
on export. Interesting point. In this case the tosser should ignore itwhile
tossing, but even there it is not noted as a need-not-be-recognizedattribute.
In short: the LOC attribute must be _set_ in order to send the
subject message.
It is rather strange. The Loc attribute is set on a locally
created message to differentiate it from a message received from
another system. So what is the point of sending a message with
the Loc attrubute set? The system receiving the message will
consider the message is created locally.
Interesting point: With checking the stored message format and the attributes definition there in FTSC 0001 the Local attribute is NOT
zeroed on export.
Hmm. I would have guessed, it's a local created
message, but the attribute is purged on export.
It is rather strange. The Loc attribute is set on a locally
created message to differentiate it from a message received from
another system. So what is the point of sending a message with
the Loc attrubute set? The system receiving the message will
consider the message is created locally.
Interesting point: With checking the stored message format and
the attributes definition there in FTSC 0001 the Local attribute
is NOT zeroed on export.
Michael
Hello All!
I don't know if this is the right conference (I looked at the rules but I didin't understand if this is the right echo), if it isn't, my apologies.
Where I can find in the FTSC docs the meanings of the message attributes and the expected behaviour of the tosser when it has to process them?
I have some doubts expecially on the LOCal attribute.
Hello, Ward Dossche.
On 21/03/20 23:57 you wrote:
Ok, before I missed the magic "Doc Search" field, and now I fond two documents, the fsc-0036.001 and the fsc-0053.002.Where I can find in the FTSC docs the meanings of the message
attributes and the expected behaviour of the tosser when it has
to process them?
Try 'ftsc.org':/ I've looked in ftsc.org but I haven't found the right article,
so I'm asking here about the right one. :) Or do I have to bribe someone with a pack of pink toilet paper? :P
But I still don't understand what a mail processor or tosser has to do when a message has the MSGLOCAL attribute set. :)
The type 2 packet format (along with the attributes field) is defined[...]
I have some doubts expecially on the LOCal attribute.
When you say "doubts", do you mean "questions"?
But I still don't understand what a mail processor or tosser has to
do when a message has the MSGLOCAL attribute set. :)
The answer is, most likely: nothing.
SBBSecho (the echomail program, "tosser", that I have developed and supported for 25+ years) sets the "LOCAL" attribute on exported
echomail messages and strips it from imported echomail messages.
The only the types of files that SBBSecho actually checks/cares about
the LOCAL attribute are NetMail "stored message files" (*.msg).
SBBSecho (the echomail program, "tosser", that I have developed and
supported for 25+ years) sets the "LOCAL" attribute on exported
echomail messages and strips it from imported echomail messages.
This sounds strange, The LOCal attribuste shoudn't identify the local originated messages like the one we write with our editor in our msgbase?
Once exported in a mail packet the LOCal attribute shouldn't be trimmed
to zero?
rob is speaking of how sbbsecho exports from a proprietary message
format to standard FTN MSG format... at that point is where sbbsecho
works with FTN standards... the proprietary message base format that
sbbs uses has other means of identifying locally and non-locally
written messages...
plus, he's not spoken of packing netmails or echomail into packets... that's another part of the process...
Hello Rob!
21 Mar 20 13:18, you wrote to me:
The type 2 packet format (along with the attributes field) is defined[...]
Thank you! :)
I have some doubts expecially on the LOCal attribute.
When you say "doubts", do you mean "questions"?
I'm a bit confused now. :)
How do you say when you're not sure about a thing?
Hello Rob!
21 Mar 20 16:28, you wrote to me:
But I still don't understand what a mail processor or tosser has to
do when a message has the MSGLOCAL attribute set. :)
The answer is, most likely: nothing.
:O
SBBSecho (the echomail program, "tosser", that I have developed and supported for 25+ years) sets the "LOCAL" attribute on exported echomail messages and strips it from imported echomail messages.
This sounds strange, The LOCal attribuste shoudn't identify the local originated messages like the one we write with our editor in our msgbase?
Once exported in a mail packet the LOCal attribute shouldn't be trimmed to zero?
The only the types of files that SBBSecho actually checks/cares about the LOCAL attribute are NetMail "stored message files" (*.msg).
I did some tests with my golded and HPT as tosser these are the results:
NETMAIL:
- Message saved without the LOC (Local) Attribute: EXPORTED.
- Message saved with the LOCK (Locked) Attribute: NOT EXPORTED.
ECHOMAIL:
- Message saved without the LOC (Local) Attribute: NOT EXPORTED.
- Message saved with the LOCK (Locked) Attribute: NOT EXPORTED.
What do you think about it?
When you say "doubts", do you mean "questions"?
I'm a bit confused now. :)
How do you say when you're not sure about a thing?
If I want someone else to clarify something, then I have a question.
If someone has stated something that I think might be untrue, then I
have a doubt.
Hello Rob!
26 Mar 20 21:54, you wrote to me:
When you say "doubts", do you mean "questions"?
I'm a bit confused now. :)
How do you say when you're not sure about a thing?
If I want someone else to clarify something, then I have a question.
If someone has stated something that I think might be untrue, then I have a doubt.
I think it's a different way to look at things.
I've noticed it in the periodic surveys that my company send to us.
I work for an international telecomminications company based in UK and our italian managers told us that in a possibile range of values that starts from wery bad to very good only the far extremes are considered, the middle is not interesting.
Wheny here we say "I have a doubt" we mean "I'm not sure about it" that also means that I trust you but I still don't understand something and I'd like to discuss with you. :)
Anyway many thanks for your help! :)
But here in the US, "doubt" has a more negative connotation: more like
"I don't believe someone/thing" or "I don't trust someone/thing".
| Sysop: | Weed Hopper |
|---|---|
| Location: | Clearwater, FL |
| Users: | 12 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 10:17:24 |
| Calls: | 67 |
| Calls today: | 1 |
| Files: | 50,165 |
| D/L today: |
69 files (6,799K bytes) |
| Messages: | 279,555 |