• Feature Request: choose which ".can" file that bot/attack IP addresses

    From Daniel Clough@1:103/705 to GitLab issue in main/sbbs on Sun May 17 18:33:00 2026
    open https://gitlab.synchro.net/main/sbbs/-/issues/1140

    Regarding the fairly recent "concurrent connections" change you made to auto-add abusers to the 'ip.can' file... could we make it configurable as to where the abuser's IP gets sent? I'd rather send it to the 'ip-silent.can' file because then my logs don't get cluttered up with the notification that an IP was blocked if/when they keep trying to connect.

    I understand there are some risks such as a valid user/IP getting blocked, but if the blocking criteria are set fairly "loose" that seems unlikely to happen to anyone but an abuser. As a multi-network FTN Hub, I like to keep a good eye on logs and the clutter from the "blocked" log messages makes that fairly cumbersome. Suggest keeping the current way as the default and let a sysop "opt-in" to changing the destination ".can" file. Thank you.
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)