TIP: Click on subject to list as thread! ANSI
echo: ftsc_public
to: MICHAEL DUKELSKY
from: MARK LEWIS
date: 2020-05-02 14:52:00
subject: Message flag bits

  Re: Message flag bits
  By: Michael Dukelsky to All on Sat May 02 2020 21:13:08


 MD> According to fts-0001 a stored message has an AttributeWord with 16
 MD> bits. Some of them are marked with '+' to show that they are not
 MD> zeroed before packeting. That means that other bits at least MAY be
 MD> zeroed. Nothing is said if there is any distinction between the
 MD> locally created and transit messages. So may the bits not marked
 MD> with '+' be zeroed for transit messages?

without looking, locally created messages generally/should(?) have the local
bit set to differentiate them from off-system messages...

bits marked without the + are generally zeroed at some point... either when
packed or when unpacked... when zeroed during unpacking, this is generally done
to prevent the local tosser from becoming confused...

eg1: a netmail arrives with the crash bit set and the local tosser would
normally route it but can/will not because of the crash bit...

eg2: when a locally generated message is packed, the local bit would be zeroed
to indicate to other tossers that it is not local to them...

generally speaking, it would be better for allowed bits to be zeroed during
packing...

again, without looking at the document or any others that discuss this
situation/distinction... but don't take only my word for it, please...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.