Skip to content
Jooosi
Account
JM Jooosi Mail

Amazon SES

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 Amazon SES profile supports AWS API, HTTPS API, and SES SMTP transports. API credentials and SES SMTP credentials are separate credential sets.

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 ses+api (default), ses+https, and ses+smtp.

Required settings#

  • API or HTTPS: Access key ID (identifier; masked in the UI) and secret access key (secret). Optional session token (secret) for temporary credentials.
  • SMTP: SES SMTP username and password; password is secret. These are not the AWS API credentials.
  • Region is an optional text setting; enter the SES region used by your account when needed.

Create the connection#

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

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 API authentication, check the access key, secret, and region together; include a session token when using temporary credentials.
  • For SMTP failures, confirm you entered SES SMTP credentials rather than AWS API keys. The profile does not declare a Jooosi Mail webhook adapter, so inspect delivery attempts and Email Logs.