21 Aug 16 01:37, you wrote to All:

 AP> Does anyone know where one can get a tutorial on how the .bso format
 AP> of mail packet attachments are done?

what do you need above that which we have already explained? it has been
written in posts numerous times and there's the original binkleyterm
documentation and a recent FTSC document, FTS-5005.002...

 AP> What are the structures of the .cut files

?UT files are just raw PKTs with a different extension...

 AP> and what is the logic in the filename

the file names *can be* four digits in hex for the destination net number
and four digits in hex for the destination node number... here's an example
using the netmail i sent you yesterday...

+ 16:22 [23448] sending ~/ftn/out/fido/09100064.dut as a9bb5f18.pkt (1571)

your address is 2320/100... in hex that is

$ printf "%04x %04x\n" 2320 100
0910 0064

09100064 which is the name of the DUT file... it was sent from my zone 1
default outbound directory...

note that i say "can be" above... one doesn't have to use ?UT
files at all... they can generate PKTs with whatever filename they want and
the standard PKT extension... then they just point to that PKT in a ?LO
file... ?LO files are just text files with one file specified per line...
the name of the ?LO file is as explained above... files attached to a
netmail are simply listed in the ?LO file addressed to the destination
system...

 AP>  and outbound directories.

the default zone outbound directory has no extension... all other outbound
directories get a hex extension for the destination zone... note that since
the extension can only be three characters long in the DOS world, the
maximum zone that binkleyterm can handle is

$ printf "%d\n" 0xfff
4095

someone in zone 5000, for instance, won't be able to use binkleyterm or the
standard BSO format... they might be able to use an "extended"
BSO outbound structure where the extension of the outbound directories may
be longer than three characters but i'm not aware of any BSO tossers or
mailers that do that yet... other mailers may have a similar zone
restriction but for other reasons than a simple three character limit on
the extension...


look for BDOC_260.ZIP for the original detailed documentation... that's the
documentation for binkleyterm v2.60...


)\/(ark

Always Mount a Scratch Monkey

... In case of fire, yell, "FIRE"!
---