24 Jul 15 09:25, you wrote to Eric Renfro:

 ER>> ArcMail/Attach-mail mailers used "Stored Messages",
FTS-1 style,
 ER>> meaning they directly utilize the *.msg files and in monitoring and
 ER>> in transmission, they are read, attached, and changed.

 ER>> binkd is BSO/FLO style mailer, which means it doesn't use "Stored
 ER>> Messages", instead, NetMail is packed into PKTs and
shipped that way.
 ER>> Combined with an .out file in a specific directory matching zone,
 ER>> net, node, and point in a specific hexadecimal naming convention.

 JD> Yes, and the hexidecimal naming convention is confusing without a
 JD> converter 

that's easy enough to deal with, though...

 JD> At least with Arcmail attach, I knew what was going where,

have you ever looked into your raw AM/FA outbound? i was never able to tell
what was going where by looking in the directory... luckily most tossers
used the same base filename for a system's packed mail... raw PKTs, on the
other hand, not so easy to tell... with packed mail using the same names
for each system, it was easy enough to write a quick little script that
showed each file and its destination at the command line level in the
outbound directory... since i've switched to raw PKTs and no longer pack
PKTs into bundles, this script cannot do anything because PKT names are
always different...

 JD> and I could manage it if required.  With BSO style it is difficult.
 JD> Can be fixed to some extent using file boxes

one only needs the proper BSO tools to manage a BSO outbound... the sad
part is that they are pretty much lost to history and the sands of time...
if they are able to be found, it is possible that they won't work (runtime
error 200 - division by zero while attempting to calculate the delay loop)
on today's blazingly fast behemoth machines...

)\/(ark

... 39. Under no circumstances should you ask a woman if she is pregnant.
---