TZUTC: -0700   
   MSGID: 57928.sync_sys@1:103/705 2c72341c   
   REPLY: 57902.sync_sys@1:103/705 2c709c0f   
   PID: Synchronet 3.20e-Win32 master/f99713f33 Mar 06 2025 MSC 1942   
   TID: SBBSecho 3.24-Linux master/45743e3e1 Apr 22 2025 GCC 12.2.0   
   BBSID: REALITY   
   CHRS: CP437 2   
   -=> nelgin wrote to All <=-   
      
    ne> Hi all,   
      
    ne> I'm considering moving from binkp to binkit for no particular reason   
    ne> and just wondered who has done this in the past and are there any   
    ne> pros/cons to the process?   
      
    I moved from Radius (an Argus clone) to Binkit a couple of years ago,   
    now. I wanted a mailer that could move with me to Linux.   
      
    If memory serves, I created the nodes in echoefg, copied the passwords   
    and info over, copied my inbound over from Radius and let it rip. I set   
    that up before filefix and tickit support, so needed to add that in   
    manually.   
      
    ne> I do have a script to automate some areafix and filefix commands   
    ne> that'll construct the email and then call binkd to send the message. It   
    ne> looks like this isn't possible with binkit at the moment. From what I   
    ne> can tell you can either poll all the nodes at once that have Poll=Yes   
    ne> or just poll a node but not send messages.   
      
   Synchronet does areafix/filefix, and there's a tickit package that does   
   most of what an end-node could need.   
      
   With binkley format, you could flavor your message Crash and poll the   
   node, would that work for your scenario?   
      
   Nowadays, I set most of my nodes as crash/direct, no need to route for   
   cost savings these days.   
      
    ne> My board has more than one link to fidonet, I assume that's a regular   
    ne> thing and shouldn't be a problem otherwise.   
      
   I think you'd just put them both in your areas file, but then you're   
   packing dupe messages if you're fed all areas by both uplinks, unless   
   feed1 also feeds feed2? If you have area lists that don't overlap per   
   uplink, that should be just fine. Binkit won't care, as that's all   
   happening at the packing stage.   
      
      
       
   --- MultiMail/Win v0.52   
    þ Synchronet þ .:  realitycheckbbs.org  ::  scientia potentia est  :.   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/13 705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 110 203/0 218/700 221/0 226/30 227/114 229/110 114   
   SEEN-BY: 229/206 317 400 426 428 470 550 700 705 240/1120 5832 263/1   
   SEEN-BY: 266/512 280/464 5003 5006 291/111 292/8125 301/1 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 467/888 633/280 712/848 770/1 902/26 5020/400 8912 5054/30   
   SEEN-BY: 5075/35   
   PATH: 103/705 280/464 460/58 229/426