Skip to content
Jooosi
Account
JM Jooosi Mail

SMTP2GO

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

The SMTP2GO profile offers API and SMTP relay transports. Its optional Region choice applies to the selected scheme.

Before you begin#

Have an account with the provider that is enabled to send mail, a sender address accepted by that account, and credentials for the method you plan to use. Copy credentials from your own provider console. Do not include credential values in documentation, screenshots, or support requests.

Supported transport and settings#

Supported transport schemes#

The profile supports smtp2go+api (default), smtp2go+smtp, and smtp2go+smtps.

Required settings#

  • API: SMTP2GO API key (secret).
  • SMTP or SMTPS: SMTP username and password; password is secret.
  • Optional Region choices: global (default), us, eu, eu2, or au.

Create the connection#

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

For the shared form workflow, see Connect a provider.

Verify delivery#

Use Jooosi Mail’s Send a test email flow, select this connection, and send to an inbox you control. The test sends a real message. Confirm the attempt appears in Email Logs and review the provider response if it fails. See Send a test email.

Webhooks#

SMTP2GO callbacks are supported for processed, delivered, open, click, bounce, spam complaint, unsubscribe, resubscribe, and rejected events. Enable webhook ingestion and configure SMTP2GO to post to the callback URL displayed for this connection. The current adapter accepts callbacks without signature verification, so check webhook status before relying on event data.

Troubleshooting#

  • If credentials are rejected, confirm that the selected scheme matches the API key or SMTP login pair.
  • If callbacks do not appear, confirm ingestion is enabled and the provider is posting to this connection’s URL; inspect Webhook Logs.