Manually adding blocked IP requires restart

Issue Description

Manually addeding blocked IPs via web interface requires a service restart to take effect.

Expected Behavior

Changes to allowed/blocked IP should be applied without requiring restart.

Relevant Log Output

Before restart:
2026-10-19T10:56:51Z INFO SMTP EHLO command (smtp.ehlo) listenerId = “submission”, localPort = 587, remoteIp = 31.70.76.30, remotePort = 52979, domain = “User”
2026-10-19T10:56:51Z INFO Auth mechanism not supported (smtp.auth-mechanism-not-supported) listenerId = “submission”, localPort = 587, remoteIp = 31.70.76.30, remotePort = 52979

After restart:
2026-10-19T10:57:39Z INFO Blocked IP address (security.ip-blocked) listenerId = “submission”, localPort = 587, remoteIp = 31.70.76.30, remotePort = 52730
2026-10-19T10:57:54Z INFO Blocked IP address (security.ip-blocked) listenerId = “submission”, localPort = 587, remoteIp = 31.70.76.30, remotePort = 54985

Stalwart Version

v0.16.x

Installation Method

Binary (FreeBSD)

Database Backend

RocksDB

Blob Storage

RocksDB

Search Engine

Internal

Directory Backend

Internal

I have reviewed the documentation and FAQ and confirm that my issue is NOT addressed there.

on

I have searched this support forum (open and closed topics) and confirm this is not a duplicate.

on

I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.

on

Found it. There is documented “Action” to reload blocked IPs without a restart. Let’s check the docs page for how to actually trigger this.

I have enough to answer confidently.

Adding a BlockedIp record through the WebUI does not by itself refresh the live in-memory blocklist used by the SMTP/IMAP listeners; that list is only picked up automatically when the record is created through the block_ip path (e.g. automatic fail2ban). For entries added manually via the Settings UI, you need to trigger the ReloadBlockedIps Action afterwards so the server rereads the blocked IP list without a restart.

You can do this from the WebUI’s server Actions screen (create a new Action of type “Reload: Blocked IPs list”), via stalwart-cli create action/reload-blocked-ips, or by calling Action/set with @type: "ReloadBlockedIps" over JMAP. This reloads the blocklist applied by the inbound filters immediately.

Reference: Actions | Stalwart and Action | Stalwart

This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong.

Just go to Management → Actions → Under Reload click Blocked IPs list

@Corne is correct. Blocked IPs you add by hand are written to the registry, and the running server picks them up when you run the “Blocked IPs list” reload under Management › Actions, or stalwart-cli create Action/ReloadBlockedIps. No restart needed. Bans the server adds on its own apply immediately; it’s manual edits that need the reload (Overview | Stalwart).

This is the same client from Auth mechanism not supported (smtp.auth-mechanism-not-supported) does not result in banning; I answered there why it never got auto-banned.