TID: Mystic BBS 1.12 A47   
   MSGID: 1:229/110 140f8145   
   REPLY: 1:129/215 eb640e61   
   TZUTC: -0400   
    g0> Mystic can automatically ban an IP after a certain number of attempts   
    g0> within a time window, but that still doesn't stop them from connecting   
    g0> it will just refuse to service them.   
    g0>    
    g0> I suppose I could add a specific feature to BINKP server that gives them   
    g0> an "BUSY" with a message that they can only connect X many times per Y   
    g0> seconds. If they are within those limits it would give them mail, if   
    g0> they were not within those limits it would give them a message and   
    g0> disconnect.   
    g0>    
    g0> But I wonder if there is really a point to do that since at that point   
    g0> they're already connected to you anyway.  I am open to suggestions as to   
    g0> whether or not such a feature would be worth it.   
      
   Personally, I don't think ol' Binky is as big a problem as port-trolling.   
   After all, one can always use the 'autoban' option in the BinkP server, too!   
      
   But, I also think that this might be a good idea, for when PiBBS is too busy   
   grinding her nightly maintenance...after all, there are other reasons why a   
   particular BBS might be busy...   
      
   Thanks for listening to us!   
      
   McDoob   
   SysOp, PiBBS   
   pibbs.sytes.net   
      
   ... If you can't make it good, make it LOOK good. -Bill Gates.   
      
   --- Mystic BBS v1.12 A47 2021/12/24 (Raspberry Pi/32)   
    * Origin: PiBBS (1:229/110)   
   SEEN-BY: 1/123 15/0 90/1 105/81 106/201 120/340 123/131 129/305 330   
   SEEN-BY: 129/331 153/7715 218/700 226/30 227/114 229/110 206 307 317   
   SEEN-BY: 229/400 424 426 428 452 550 664 700 240/5832 266/512 282/1038   
   SEEN-BY: 292/854 301/1 317/3 320/219 322/757 342/200 396/45 460/58   
   SEEN-BY: 633/280 712/848   
   PATH: 229/110 426