Subj : Messages attributes in FTSC docs
To : Fabio Bizzi
From : Rob Swindell
Date : Thu Mar 26 2020 09:58 pm
Re: Messages attributes in FTSC docs
By: Fabio Bizzi to Rob Swindell on Wed Mar 25 2020 08:46 am
> 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. :)
>
> RS> The answer is, most likely: nothing.
>
> :O
>
> RS> SBBSecho (the echomail program, "tosser", that I have developed and
> RS> supported for 25+ years) sets the "LOCAL" attribute on exported
> RS> 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?
It could. It could also represent messages that were uploaded to the BBS via QWK. Or if the BBS supports NNTP, SMTP or any other transport, messages that were posted in that manner. These messages are still locally-created with relation to the rest of FidoNet.
> Once exported in a mail packet the LOCal attribute shouldn't be trimmed to
> zero?
I don't think it really matters. It's obvious once a packet has been received from any system that it was not a local message - regardless of that attribute flag value.
> RS> The only the types of files that SBBSecho actually checks/cares about
> RS> 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?
