The connection model
Everything in Wigmorean SMTP is organized around connections. A connection is one provider (SMTP server or API-based service) with its credentials and a "from" identity. You can add more than one, and route different kinds of mail through different providers.
Typical setup: one connection for transactional mail (receipts, password resets), a second for marketing (newsletters), a third as a failover.
Supported providers
| Provider | Type | Best for |
|---|---|---|
| Brevo (Sendinblue) | API | Transactional + marketing, generous free tier |
| SendGrid | API | High-volume transactional |
| Mailgun | API | Developer-friendly, good analytics |
| Amazon SES | SMTP | Lowest cost, technical setup |
| Generic SMTP | SMTP | Any SMTP relay (your web host, self-hosted Postfix) |
Adding a connection
- Go to Wigmorean → SMTP → Connections
- Click Add Connection
- Pick your provider
- Paste the API key (or SMTP host/port/username/password)
- Set the sender email and sender name
- Click Test to send a validation ping — you'll see a green check when the provider accepts the handshake
- Click Save
Email log
Every outgoing email passes through Wigmorean SMTP and gets logged. The log shows: timestamp, from, to, subject, connection used, delivery status, and the full body. Use the search bar to filter by recipient, subject, or date range. You can resend any message with one click.
DNS check
The DNS Check tool pulls the live records for your sending domain and compares them to what the provider expects. It flags missing or malformed SPF, DKIM, and DMARC records. Fix warnings before you rely on the connection for important mail.
Settings
- Default connection — which connection
wp_mail()uses when nothing else overrides it - Log retention — how long to keep messages in the log (7 to 365 days)
- Failover chain — if the primary connection errors out, try the next one