On 14 Oct 2025, Sean Dennis said the following...

 SD> Just randomly connecting then dropping the connection to my BinkP is nop
 SD> different than being portscanned to me.

 SD> In the firewall he goes.

I have a similar problem with the ZC of another network that I joined
once-upon-a-time then then dropped.

He'll constantly hammer my system trying to deliver mail, often trying hundreds
(and sometimes over a thousand) times per day.  I'll email him, ask him to stop.
 It'll take a few weeks but he'll respond back apologizing and then it stops...
for a time...

Then randomly one day his system tries delivering something to me again, failing
every time as that network was dropped years ago.  So like you I've added his IP
addresses to my iptables to drop anything from them.  If he happens to change
IPs, I have a script that looks at my binkd.log files and if his name appears
that subnet gets added to the blocklist.

I've asked nicely several times for him to stop hammering me, whether through
ignorance, stupidity or malice he persists, so like you said...  I the firewall
it goes.

I'm beginning to see the wisdom of Deon's approach to having different dns names
for different networks.  If/when I ever join a new network in the future (quite
unlikely), I'll be creating a new subdomain specifically for that network (e.g.
bink-min.nrbbs.net, bink-fsx.nrbbs.net, etc...)


Jay

... I used to be a tap dancer until I fell in the sink

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
 * Origin: Northern Realms (618:400/23)