What is Pepipost?#
Pepipost, part of Netcore, provides email delivery through an API and SMTP. Read more on the official website and in the official documentation.
Profile#
The Pepipost profile supports API, SMTP, and secure SMTP delivery. The API scheme is the default.
- API: pepipost+api requires an API key (secret). The optional region selector currently offers eu.
- SMTP: pepipost+smtp and pepipost+smtps require an SMTP username and SMTP password (secret).
- The region selector is shown only for API mode; SMTP has no region field.
Create the connection#
Before you begin, create an account and prepare the credentials for the selected transport. Complete any sender or domain verification required by the provider.
- In WordPress admin, open Jooosi Mail → Connections and choose New connection.
- Enter a descriptive Connection name and select Pepipost in Profile.
- Choose pepipost+api, pepipost+smtp, or pepipost+smtps and enter the matching credential fields. For API mode, set the region only if needed; the form currently offers eu.
- Review the sender, routing, and advanced settings for this connection.
- Choose Create connection to save it.
For the shared connection workflow, see Provider profiles and transports.
Verify delivery#
Follow Send a test email and send it to a mailbox you can check. A test sends a real email. Check the mailbox and Jooosi Mail → Logs for the attempt status. See Email logs and resending for details.
Webhooks#
The Pepipost profile does not declare a provider webhook adapter. Track delivery attempts in Jooosi Mail email logs.
Troubleshooting#
- For missing-field validation, confirm the scheme and fill the required settings listed in Profile.
- After a failed test, re-copy the matching credential and inspect the connection status and email log.
- For API mode, check the API key and use a region value offered by the form. For SMTP, verify both username and password and select pepipost+smtp or pepipost+smtps.