Description

When I create a filter that moves messages to a sub-folder of the Inbox, the
generated Sieve uses the localized Inbox display name ("Entrada" in pt-BR) as the
path prefix instead of INBOX, so the target folder doesn't exist and the message
is never moved.

Rewriting the script by hand to use INBOX/... makes filtering work, so the issue
is the path Bulwark generates — the Inbox seems to be resolved to its localized
display name rather than the real mailbox name.

Steps to Reproduce

1. Set the UI language to a locale where the Inbox is translated (pt-BR = "Entrada").
2. Create a filter that moves matching messages to a sub-folder of the Inbox, e.g. Host/EVEO.
3. Save it, then inspect the active Sieve script (ManageSieve GETSCRIPT or JMAP).
4. The action reads fileinto "Entrada/Host/EVEO" — a path that doesn't exist — so nothing is filed.

Expected Behavior

The filter should target the real mailbox name, e.g. fileinto "INBOX/Host/EVEO";, regardless of UI language.

Actual Behavior

The saved filter generates fileinto "Entrada/Host/EVEO";, using the localized
Inbox display name as the path. That mailbox doesn't exist (the real tree is rooted
at INBOX, e.g. INBOX/Host/EVEO), so the message is never filed and stays in the
Inbox. The script is otherwise valid and active.

Bulwark Version

1.6.6

Stalwart Mail Server Version

0.16.4

Browser

No response

Operating System

None

Screenshots / Screen Recording

No response

Relevant Logs or Error Output

Additional Context

No response