App Password Policy & Revocation #

TsubameMail separates Webmail / Console login credentials (primary password or Passkey) from App Passwords used by third-party mail clients (Apple Mail, Mozilla Thunderbird, Microsoft Outlook).

Policy Rules #

  • Default Scopes: ["mail.read", "mail.send"] (imapd and pop3d require mail.read; smtp-in submission requires mail.send).
  • One-Time Secret Display: The plaintext App Password is returned only once at creation time (POST /v1/credentials/app-passwords). Neither admins nor users can view it again later; only its label, scopes, and status are retained.
  • Independent Revocation: Revoking an App Password immediately blocks that device/client on IMAP/POP3/SMTP without affecting the user's Webmail password or other devices.
  • Fail-Closed Encryption Key: control-backendd requires IDENTITY_APP_PASSWORD_KEY; if unconfigured, App Password issuance returns 503 Service Unavailable.

Issuing an App Password (Admin-Assisted) #

json
POST /v1/credentials/app-passwords
{
  "tenant": "<tenant-id>",
  "login": "alice@<your-domain>",
  "label": "Work Laptop Thunderbird",
  "scopes": ["mail.read", "mail.send"]
}

Revoking Compromised App Passwords #

  1. Open App Passwords in https://console.<your-domain>.
  2. Locate the user (alice@<your-domain>) and device label (e.g., Lost Phone).
  3. Click Revoke to terminate access immediately. Active imapd / pop3d / smtp-in credential status checks (CredentialStatusService.Status) deny further authentication fail-closed.
TIP

Encourage users to create one dedicated App Password per device via Webmail (https://mail.<your-domain>) rather than reusing one token across multiple clients.