OneLinersCommand workbench
AI
Back to prompts
plain-prompt

Diagnose Dovecot authentication failures

Separate user lookup, password verification, TLS, and protocol-layer failures.

Revision
1
Verified
2026-07-26
Save or explore
Save to collectionCreate a collection in the sidebar first.

Compatibility and paths

GenericWorks with instruction-following chat models.
ChatGPT
Claude Code
Gemini CLI

Trust and provenance

Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.

Fill variables

Values stay in this browser tab and are not stored.

Generated asset2 required field(s) must be completed
Objective: Identify the authentication stage and protect credentials during testing.

Context: Never request real passwords in diagnostic output.

Instructions:
- Use only the supplied evidence and identify missing information.
- Lead with the finding, confidence, and one safe next action.
- Put read-only checks before mutations and include a stop condition.
- Never request or reproduce secrets, credentials, or private keys.

User request:
Dovecot version/backend:
{{environment}}

Redacted logs and test output:
{{evidence}}

Diagnose authentication.

Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop condition

Real example

Input

auth-worker: passwd-file(user@example.net): unknown user

Expected result

The user database lookup failed before password verification. Confirm the configured userdb source, normalized username, and domain mapping with redacted test data.

Source evidence

Dovecot documentationofficial