Find the problem and collect diagnostics
Identify the failing operation and collect a useful, sanitized support report.
Start by identifying which operation failed: installation, mailbox connection, inbox refresh, composer sending, WordPress notifications, or a paid feature. They do not all use the same settings.
Collect diagnostics
Open PressedMail > Settings > Diagnostics and run the relevant checks. Record the result before changing settings, then repeat that check after a fix.
Keep the plugin edition and version, WordPress and PHP versions, provider name, and the exact error. If the plugin cannot open, use WordPress's error or recovery information instead of repeatedly activating it.
Review a copied report before sharing it. Remove credentials, license keys, private addresses, or message content that support does not need.
Choose the next check
| Symptom | Guide |
|---|---|
| ZIP upload, activation, license, or update failure | Installation, licensing, and updates |
| IMAP or SMTP connection test fails | Mailbox connections |
| Inbox is stale or a composer message will not send | Inbox sync and sending |
| Password resets, store emails, or form notifications fail | WordPress SMTP setup and WordPress email logs |
| AI, rules, or security controls behave unexpectedly | AI, rules, and security controls |
Change one relevant setting at a time. Before retrying an uncertain send, check the provider's Sent folder and recipient account. Before rerunning a rule, remember that it can modify real messages.
Common setup questions
PressedMail connects to an existing mail provider. It does not host a new mailbox. Provider selection and authentication are covered in Connect your first mailbox.
The native PHP IMAP extension is not required. A missing extension notice is not proof the mailbox connection is broken.
Contacts, calendars, AI, and some scheduling features require a paid build. Other features can have source code without an exposed workspace workflow. Check the relevant guide before trying to find a missing control.
Ask for help
Include what you tried, what you expected, what happened, when it happened, and whether one account or the whole site is affected. A short sequence that reproduces the issue is more useful than “email is broken.”
Send sanitized error text and relevant diagnostics. Do not send passwords, API keys, OAuth tokens, license keys, full message bodies, or private attachments unless a separate secure support process explicitly requires specific data.