TID: Mystic BBS 1.12 A48   
   MSGID: 1:266/625 bfa3f612   
   REPLY: 2:250/5 71729cb9   
   TZUTC: -0400   
   On 02 Jul 2024, Christian Sacks said the following...   
    CS> I think on the whole this is a nice approach, however what happens when   
    CS> Mystic accidentally blacklists your own IP, or it'self? Then you have   
    CS> iptables blocking you out and you won't be able to get back in =)   
      
   Understood, and Mystic already has a solution built-in.   Just be sure to add   
   the addresses you commonly connect from to the mystic/data/allowlist.txt; that   
   way the system will never lock you out.  And, if you are using the 4   
   connections in 120 secs suggested setting, the likelihood of locking yourself   
   out is pretty small. (unless of course your are testing ssh settings and you   
   keep trying options that fail..., ask me how I know?!? :) )   
      
   --- Mystic BBS v1.12 A48 (Linux/64)   
    * Origin: <=-{ The Digital Post }-=> (1:266/625)   
   SEEN-BY: 90/1 105/81 106/201 124/5009 128/260 129/12 102 125 160 165   
   SEEN-BY: 129/305 328 153/7715 218/700 226/30 227/114 229/110 111 112   
   SEEN-BY: 229/113 206 275 300 307 317 400 426 428 470 550 664 700 261/1   
   SEEN-BY: 261/220 266/75 215 512 618 625 267/152 154 282/1038 291/111   
   SEEN-BY: 292/854 320/219 322/757 342/200 396/45 460/58 633/280 712/848   
   SEEN-BY: 5075/35   
   PATH: 266/625 512 229/426