MSGID: 3:640/1384.125 5dc4962e   
   REPLY: 2:335/364.1 5dc42d6e   
   PID: JamNNTPd/Linux 1   
   CHRS: UTF-8 2   
   TZUTC: 1000   
   TID: CrashMail II/Linux 0.71   
   Hi! Fabio,   
      
   On 11/08/2019 12:42 AM, you wrote:   
      
    FB> BTW I did it at last, I've had to add the full path of the received file.   
    FB> It sounds a bit strange because the other exec statements works without   
    FB> the full path added. :/   
      
    FB> This Works:   
    FB> exec "/home/husky/bin/netsegments.sh" /home/husky/in.sec/net33?.???   
      
   That's one way of looking at it.  If your script knows where to look every   
   time, you win.  Because the binkD setting is only a trigger.   
      
   OTOH.  I share your frustration.  It would be nice if binkD was consistent.   
      
   Cheers,   
   Paul.   
      
   --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0   
    * Origin: Right Rudder, Left Stick.  Wheeeeeee! (3:640/1384.125)   
   SEEN-BY: 1/123 90/1 103/705 154/10 203/0 221/0 1 6 242 360 227/114   
   SEEN-BY: 229/101 200 354 426 1014 230/0 240/5832 249/307 317 280/464   
   SEEN-BY: 280/5003 5555 292/854 310/31 320/219 342/200 396/45 423/81   
   SEEN-BY: 423/120 633/280 640/1138 1321 1384 712/848 770/1 2452/250   
   SEEN-BY: 3634/12   
   PATH: 640/1384 221/1 280/464 229/426