On 2019 Jun 23 18:52:30, you wrote to me:
i was able to recover and get the several thousand pkts sent but this
is not a fun task to deal with...
More of a task than I would care to do for sure.
thankfully there was an easy to use binary tool to analyze the raw pkts and emit their source and destination addresses... it sure beat having to look at the pkts manually for their passwords to figure them out... those without passwords certainly needed to be analyzed for their destination addresses... once we had the destination addresses, it was a simple matter to recreate the flo files...
eg:
# make a list of pkt destination addresses
/sbbs/exec/pktdump /sbbs/fido/outbound/*.pkt | \
egrep -e "Packet Type .* from $MYFTNADDR to " | \
cut -d " " -f 12 | sort -V | uniq
# choose an address from the above list
# get a list of pkts destined there and
# move those pkts to the tmp directory
/sbbs/exec/pktdump /sbbs/fido/outbound/*.pkt | \
egrep -e "Packet Type .* from $MYFTNADDR to $DESTADDR" | \
cut -d " " -f 1 | tr '\n' '\0' | \
xargs -0 -n1 -i mv '{}' /sbbs/tmp
# create a flo file with the pkts
printf "$(ls -d -1 $PWD/*.pkt | \
sed 's/^/\^/')\n" > \
$(printf "%04x%04x.flo\n" $DESTNET $DESTNODE)
it can be done a bit better by not moving the pkts to the tmp directory first but this works fine with some manual work added... once the flo file is created, it is a simple matter manually to copy/move it to the proper outbound directory and wait for the mailer to transit and delete the pkts listed in it before handling the next system in the list of destinations...
i've not yet spent more time to fix it up into a proper script that doesn't need to move the files at all plus there should be some .bsy file creation to prevent the tosser and mailer from jumping the gun while the pkts are moved and the flo is created... i've already got script code that breaks down FTN addresses into their component parts and determines the proper outbound directory so that part is already done... i just need to find that source library and use it for this, too...
yes, i'll also be checking with the mail tosser developer and seeing if
we can get the full path in place instead of using the "../blah/blah"
format...
I have run into that situation also. I tend to specify the full path's Linux path in my configs to hopefully avoid any doubt.
yeah, unfortunately i don't think the operator defined paths in the configs have much to do with the software's output of relative directory usage... i understand the reasoning for using relative directories but it can be problematic when mixing in 3rd party software... i do need to visit the wiki, though, and see if i can find something there that might point to a setting that might cover this...
)\/(ark
Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... We must all band together and be non-conformists.
---
* Origin: (1:3634/12.73)