feat: add email forwarding management UI

[filippoadessi]

Summary

Adds a dedicated email forwarding management section to the Directory module, allowing administrators to create, edit, and delete per-address forwarding rules without manually editing Sieve scripts.

Storage model

Rules are stored in the settings store under mail.forward.<from_address>.*:

• mail.forward.<addr>.to.0, .to.1, … — destination addresses (array)
• mail.forward.<addr>.keep-copy — boolean; when true uses Sieve :copy to keep a local mailbox copy

A per-domain Sieve trusted script (sieve.trusted.scripts.<domain_underscored>.contents) is generated, updated, or deleted automatically on every create / edit / delete operation.

New pages

• Directory → Forwards (/manage/directory/forwards) — paginated list with search and bulk delete; Sieve scripts are rebuilt on deletion.
• Directory → Forwards → Edit (/manage/directory/forwards/:id/edit) — create or edit a rule: source address (fixed on edit), one or more destination addresses, keep-copy toggle.

Inline editing in the Account detail page

The account edit page (/manage/directory/accounts/:id/edit) gains a Forwarding tab for Individual accounts. The UI mirrors the existing Aliases field: a stacked list of editable inputs with add/remove buttons and a keep-copy checkbox. Forward settings are loaded automatically when the account is opened and saved atomically together with "Save changes" — no separate save step required.

Test plan

• Create a forward rule from the Forwards list page; verify the Sieve script appears under sieve.trusted.scripts
• Edit the rule (change destinations, toggle keep-copy); verify the script is updated
• Delete the rule; verify the script is removed when no rules remain for that domain
• Open an Individual account, set forward addresses in the Forwarding tab, save; verify settings and Sieve script
• Clear all forward addresses for an account and save; verify settings and script are removed
• Verify the Forwards menu entry is only visible to users with settings-list permission

🤖 Generated with Claude Code

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[stappersg]

Text from #137 (comment)

Hi, thanks for the PR but this can't be merged as we're about to rewrite the webadmin from scratch using Leptos 0.8 and the new v0.16 JMAP API.

[mdecimus]

Thanks but AI generated code is not accepted. In addition to that the webadmin is going to be rewritten from scratch in the next few days.

[filippoadessi]

Thanks for your reply. I use forwarding feature and stalwart has a sieve scripting management workflow for this and it’s not so friendly as I expect. I thought that a little patch to webadmin could be useful not only for me. I will wait for the new webadmin application. Bye Filippo Il 22 mar 2026, 19:07 +0100, Maurus Decimus ***@***.***>, ha scritto:

…

mdecimus left a comment (stalwartlabs/webadmin#138) Thanks but AI generated code is not accepted. In addition to that the webadmin is going to be rewritten from scratch in the next few days. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>