Secure WildDuck management API and mailbox access
Provision through the documented REST interface and distinguish administrative tokens, user credentials, and application-specific passwords.
Reviewed
WildDuck’s API manages accounts, mailboxes, and message resources. That administrative surface has a different trust boundary from a user’s IMAP login or an application’s permission to submit mail.
Configure least-privilege access
- Use the API access-control and account instructions linked from WildDuck’s documentation.
- Restrict API network exposure and configure supported authentication/permissions before provisioning real users.
- Create a controlled account with the current request schema; do not assume a user row alone configures every SMTP integration.
- Give clients the documented user/app-specific credentials and trusted TLS endpoints. Two-factor authentication may require application-specific passwords for mail clients.
Do not place a global management token in a user-facing client or model prompt. Limit service credentials to the operations and resources required by your application.
Verify access boundaries
Test a permitted account/mailbox read, denied cross-user access, incorrect credentials, and a controlled message retrieval. Confirm the actual API/client response shapes rather than adapting a Postal or MailKite payload parser blindly.
If integrating message events or webhooks, use WildDuck’s specific documented facility and authentication; neither callback shape nor signature is implied by having an HTTP API. Retain audit/correlation identifiers while keeping message bodies and credentials out of diagnostic logs. Back up account/authentication metadata together with message and attachment storage.