Hello Nick,

Tuesday February 27 2018, Nick Andre wrote to Michael Dukelsky:

 MD>> There are two different formats of stored message (*.MSG): OPUS and
 MD>> FTS-0001. Unlike OPUS, message header in FTS-0001 format contains
 MD>> destination zone number and destination point number. Husky programs
 MD>> use smapi library which uses OPUS format.
 MD>>
 MD>> Does anybody use both Husky and some program that reads .MSG using
 MD>> FTS-0001 format and takes a point number from the message header
 MD>> instead of FMPT kludge?

 NA> The zone headers as noted in the current FTS-0001 are optional; and
 NA> most mail tossers do not insert the zone into those fields. What is of
 NA> "critical" importance is the net and node numbers; followed by the
 NA> insertion of the INTL kludge for zones and TOPT for points.

 NA> If a tosser does not do it this way and ignores the insertion of INTL
 NA> for example, most other tossers will treat the message as belonging to
 NA> the same zone class as the address of the processing system... leading
 NA> to misrouting of the message and a barrage of flaming from the
 NA> know-it-all Sysop crowd.

 NA> It is extremely rare to see a BBS or 3rd-party program specifically
 NA> use the header and not the kludge-method.

My question was not about messages transerred to other nodes but about
messages stored by the HPT tosser locally that may be read by some other
program. Such a program may be a netmail tracker or a message viewer/editor
for example.

I've discovered that SMAPI library used by HPT for (among other things)
storing .MSG type messages on disk writes destination point number to
'times' field designed for storing the number of times the message was
read. Thus it turns out that a freshly written message is shown by a
message editor as already read.

I want to delete the code spoiling the 'times' field but I don't know
whether any program uses the point number written to this field.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20170303