NNTP false bogus commands?

I was checking my logs and saw this.

Feb 26 19:04:01 bbs synchronet: srvc 0052 NNTP [DOVE-Net.Synchronet_Announcements] cmd: GROUP DOVE-Net.Synchronet_Baja
Feb 26 19:04:01 bbs synchronet: srvc 0052 NNTP Throttling bogus command sending client for 3 seconds

but on another connection

Feb 26 19:07:23 bbs synchronet: srvc 0051 NNTP [SpookNet.SN_PARANORMAL] cmd: GROUP SpookNet.SN_POLITICS
Feb 26 19:07:23 bbs synchronet: srvc 0051 NNTP [SpookNet.SN_POLITICS] cmd: GROUP SpookNet.SN_PREDICT

No error.

Not sure why this should be happening.

added nntp-service label

My guess: the client sent unrecognized commands before the pasted log message. Look further back in the log output of the NNTP session to find them. If you have debug-level logging enabled, you should see some log message such as:

Received bogus command:

Feb 25 13:47:36 bbs synchronet: srvc 0052 NNTP [Fidonet.ZEC] cmd: GROUP FSXNET.FSX_ADM
Feb 25 13:47:36 bbs synchronet: srvc 0052 NNTP !no such group
Feb 25 13:47:36 bbs synchronet: srvc 0052 NNTP Received bogus command: 'GROUP FSXNET.FSX_ADM'

Seems I have a usenet group in my reader that I deleted from the news server. I'm not sure I'd call this a bogus command, especially if there is no error reported back to the client so the user can fix it.

Maybe if there's a a large number of invalid groups requested then yeah, I can see throttling.

Yeah, the "no such group" requests are considered bogus commands. There is a negative response sent to the client for those received commands (unrecognized/supported group) as well.