Skip to content
Jooosi
Account
JM Jooosi Mail

MailKite

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

MailKite can deliver through its API or SMTP relay. Choose the route that matches the credential you have; Jooosi Mail keeps the credential fields separate by transport.

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#

  • mailkite+api (default): Required: API key (secret).
  • mailkite+smtp or mailkite+smtps: Required: SMTP username and SMTP password (secret). The username defaults to mailkite.

Create the connection#

  1. In WordPress admin, open Jooosi Mail → Connections and choose New connection.
  2. Enter a descriptive Connection name and select MailKite 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.

If you choose an SMTP scheme, keep the default username unless your MailKite account specifies another one. The password is required for both SMTP schemes.

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.
  • Confirm that the selected scheme matches the credential type: API key for API, SMTP password for either SMTP scheme. For SMTP, check the username and password together; the profile requires both.