Mailomat offers API and SMTP delivery in Jooosi Mail. The API scheme is selected by default and needs one API key; SMTP uses a username and password.
Before you begin#
- You need access to the provider account and the Jooosi Mail Connections screen. If the provider requires sender or domain verification, complete it in the provider account first.
- Copy credentials directly from the provider’s own console into the matching Jooosi Mail field. Keep secret values private; never include them in screenshots or support messages.
Consult provider sending documentation for any provider-side setup requirements.
Supported transport and settings#
mailomat+api(default): Required: API key (secret).mailomat+smtp: Required: SMTP username and SMTP password (secret).
Create the connection#
- In WordPress admin, open Jooosi Mail → Connections and choose New connection.
- Enter a descriptive Connection name and select Mailomat in Profile.
- Choose the transport scheme you want to use. Enter its required fields listed above and leave fields for other schemes empty.
- Review the sender, routing, and advanced settings for this connection.
- Choose Create connection to save it.
Webhooks are optional and configured separately from sending credentials. If you enable them, Jooosi Mail also requires a webhook shared secret; see the webhook note below.
For the shared form workflow, see Connect a provider.
Verify delivery#
Use Send a test email with a recipient you control; it sends a real message through this connection. Check its status and the email log for the provider response.
Webhooks#
The Mailomat adapter accepts accepted, not_accepted, delivered, temporary and permanent failure, open, and click events. Enabling webhooks requires a shared secret in the connection. Jooosi Mail verifies the request HMAC using the Mailomat event, webhook ID, timestamp, and signature headers. Use the endpoint and setup flow in Provider webhooks; copy the matching secret from the provider’s own console without sharing its value.
Troubleshooting#
- For missing-field validation, confirm the scheme and fill all required settings listed above.
- After a failed test, re-copy the matching credential and inspect the connection status and email log.
- If the connection cannot be saved with webhooks enabled, check that its webhook secret is present. If an event is rejected, confirm the provider webhook is signing with the same secret and that its signed headers reach WordPress unchanged.