home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   BINKD      Support for the Internet BinKD mailer      8,958 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 7,455 of 8,958   
   Wilfred van Velzen to Paul Hayton   
   Re: Rejecting an incoming connection   
   20 May 21 10:29:19   
   
   TID: FMail-lnx64 2.1.0.18-B20170815   
   RFC-X-No-Archive: Yes   
   TZUTC: 0200   
   CHRS: UTF-8 2   
   PID: GED+LNX 1.1.5-b20161221   
   MSGID: 2:280/464 60a61e34   
   REPLY: 3:770/100 2a9887ba   
   Hi Paul,   
      
   On 2021-05-20 19:59:44, you wrote to All:   
      
    PH> As some of you may know I run an othernet in Zone 21 and have a /999   
    PH> test AKA that nodes who which to test their polling setup to my HUB   
    PH> can use when first setting up and before they apply and get their own   
    PH> node number.   
      
    PH> The problem I have at present is that someone has set up their BBS and   
    PH> is polling the HUB every 2 minutes using the test AKA. This is way too   
    PH> frequent, has been going on for weeks, and despite a netmail to that   
    PH> test system asking for the sysop to contact me to arrange their own   
    PH> node number, there's been no reply and no let up in polling frequency.   
      
    PH> I'm looking for a way for BinkD to reject the incoming connection   
    PH> based on something like SYS or ZYZ info presented. Is such a thing   
    PH> possible using a perl script or similar?   
      
    PH> Note I am not a perl guru so any suggested fix you have I'd appreciate   
    PH> a bit of hand holding to implement it.   
      
    PH> Also of note, setting such a block up is not my preferred choice but I   
    PH> have exhausted options to contact the unknown sysop and want to ensure   
    PH> the test AKA is available for others to send/recieve packets from   
    PH> also...  with a polling frequency of 2 mins the offending system gives   
    PH> no one else a look in.   
      
   Why not just block his IP (range) in your firewall? That would be the easy   
   sollution...   
      
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 1/123 90/1 103/705 105/81 114/709 120/340 123/131 124/5016   
   SEEN-BY: 129/305 154/10 203/0 220/50 221/0 226/30 227/114 229/100   
   SEEN-BY: 229/101 200 424 426 550 664 700 720 1016 1017 240/5832 249/109   
   SEEN-BY: 249/110 206 307 317 280/464 5003 5555 282/1038 288/100 292/854   
   SEEN-BY: 292/8125 301/1 310/31 317/3 322/757 342/200 396/45 423/120   
   SEEN-BY: 460/58 633/280 712/848 770/1 2452/250   
   PATH: 280/464 229/101 426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca