Re: hpt moving/changing netmail?
  By: mark lewis to Joe Delahaye on Fri Jul 24 2015 11:01:18

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

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

Yes but it is time consuming. It would make more sense if the .try or .*lo
files had a node number in the text.  Sometimes there is a number, but I have
no idea what its purpose is.


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

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

Yes, but with Irex, and other mailers, you could look up a que and see what was
where.  Even Taurus has that capability.


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

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

Ancient technology IOW
--- SBBSecho 2.27-Win32