Subj : bug in binkd flo file processing?
To   : all
From : mark lewis
Date : Sat Jun 22 2019 08:36 pm


i have a mail tosser that creates flo files containing "../" at the beginning 
of the line pointing to the files to be sent... this is fine in most cases 
because we generally change directory to a proper place before starting the 
mailer...

yesterday we had a power outage... when the power was restored and i was bring 
the system back online i forgot to change to the proper directory before 
starting binkd... as a result, it could not find the files it was trying to 
send and emitted messages like this...

start_file_transfer: ../fido/outbound/5d02ac39.pkt: No such file or directory

ok, i don't have a problem with that... the problem and the reason for this 
post is that the flo file is deleted thus leaving behind a file with no 
indication as to its destination...


my query is if binkd should be deleting the flo file when it cannot file the 
file(s) to send... i would think that if there is an error like this, binkd 
would elect to be cautious and not delete the flo file or to at least recreate 
it as it was like it does in other instances (eg: connection failure)...


i was able to recover and get the several thousand pkts sent but this is not a 
fun task to deal with...

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...

thank you for your time and attention :)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it 
wrong...
.... System Update - A quick method of trashing ALL of your software.
---
 * Origin:  (1:3634/12.73)

.