Aliases

first-time setup

Choose an app password

You'll use it to open this app. Keep it long — it's the only lock on your aliases.

Connect to Stalwart

Paste an API key from the Stalwart WebUI. It stays on the server and is only used to edit the aliases of one account.

How to create the key
  1. Stalwart WebUI → account menu (top-right) → Credentials → API Keys → Create.
  2. Permissions: Replace all permissions with authenticate, sysAccountGet, sysAccountUpdate, sysAccountQuery, sysDomainGet, sysDomainQuery.
  3. Optionally restrict Allowed IPs to the docker network this app runs in.
  4. Copy the secret (shown once) and paste it above.

Aliases

sign in to continue

Aliases

 
You're offline — showing the last list you loaded.
 

New alias

…
Also allow sending from itregisters it as an approved sender with the relay

Alias

Receiving mail
Created
Sending mail
Sending from this address
  1. Turn on Sending mail above — the app registers the address as an approved sender with the relay (OCI Email Delivery). Receiving needs nothing.
  2. eM Client → Accounts → General → Aliases → add it once, then pick it in the From field.

Settings

Managing
Version
Sending
Aliases live in Stalwart itself — the WebUI shows the same list.

Change app password

Replace Stalwart API key

Paste the new key. It is verified against Stalwart before it replaces the old one.

Sending from aliases

Outgoing mail is relayed by OCI Email Delivery, which only accepts approved senders. With an OCI API key the app registers each alias for you.

Leave empty to keep the stored key.
Where these come from (one-time, OCI console)
  1. Identity → Domains → Default domain → Groups: create a group aliasman.
  2. Identity → Policies (root compartment): create a policy with one statement: Allow group aliasman to manage approved-senders in tenancy.
  3. Users: create a user aliasman (no console password needed), add it to the group.
  4. Open that user → API keys → Add API key → Generate API key pair, download the private key, then copy user / fingerprint / tenancy / region from the configuration file preview.
  5. Compartment: the one your existing approved senders are in (Email Delivery → Approved Senders shows it; the root compartment's OCID is the tenancy OCID).