Skip to content
Jooosi
Account
JM Jooosi Mail

MailPace

Browse documentation
Overview
Contents
On this page
  1. Before you begin
  2. Supported transport and settings
  3. Create the connection
  4. Verify delivery
  5. Webhooks
  6. Troubleshooting

MailPace supports API and SMTP delivery. Each route uses its own MailPace token field, so select the scheme before entering the credential.

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#

  • mailpace+api (default): Required: API token (secret).
  • mailpace+smtp: Required: SMTP API token (secret).

Create the connection#

  1. In WordPress admin, open Jooosi Mail → Connections and choose New connection.
  2. Enter a descriptive Connection name and select MailPace in Profile.
  3. Choose the transport scheme you want to use. Enter its required fields listed above and leave fields for other schemes empty.
  4. Review the sender, routing, and advanced settings for this connection.
  5. Choose Create connection to save it.

The profile does not ask for an SMTP username or separate host settings. Use the token issued for the route you selected.

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#

This profile does not declare a provider webhook adapter. Track delivery outcomes in the Jooosi Mail email logs. See the shared email logs guide.

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.
  • A credential entered for one route does not satisfy the other: API requires the API token field, while SMTP requires the SMTP API token field. If the form reports missing configuration, reselect the scheme and check the corresponding token field.