• nntpservers reports non-existing group fetch as a bogus command

    From Nigel Reed@1:103/705 to GitLab issue in main/sbbs on Tue Nov 30 20:49:25 2021
    open https://gitlab.synchro.net/main/sbbs/-/issues/308

    If a sysop removes a group and a usenet client ties to fetch from it, it's logged as a bogus command and throttled, however each group after is also throttled. Fetching from a non-existent group should just be logged and skipped, especially for authenticated clients, since this then blocks further legitimate use.Nov 30 22:42:04 bbs synchronet: srvc 0096 NNTP [Fidonet.OTHERNETS] cmd: XHDR cc 4275Nov 30 22:42:04 bbs synchronet: srvc 0096 NNTP [Fidonet.OTHERNETS] cmd: GROUP Fidonet.R19_CHATNov 30 22:42:04 bbs synchronet: srvc 0096 NNTP [Fidonet.R19_CHAT] cmd: GROUP Fidonet.R19COORDNov 30 22:42:04 bbs synchronet: srvc 0096 NNTP !no such groupNov 30 22:42:04 bbs synchronet: srvc 0096 NNTP Received bogus command: 'GROUP Fidonet.R19COORD'Nov 30 22:42:04 bbs synchronet: srvc 0096 NNTP Throttling bogus command sending client for 1 secondsNov 30 22:42:06 bbs synchronet: srvc 0096 NNTP [Fidonet.R19SYSOP] cmd: GROUP Fidonet.SYSOPNov 30 22:42:06 bbs synchronet: srvc 0096 NNTP Throttling bogus command sending client for 1 secondsObviously, this can only be fixed on the client side by the user removing the group but they may not be aware it's been removed.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)