Skip to content
Jooosi
Account
JM Jooosi Mail

Scaleway

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

Scaleway supports API and SMTP delivery. Both routes need a project identifier and API credential, but the SMTP route treats the project ID as the username and the API key as the 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#

  • scaleway+api (default): Required: API project ID and API key (secret). Optional: region text.
  • scaleway+smtp: Required: SMTP username (project ID) and SMTP password (API key secret).

Create the connection#

  1. In WordPress admin, open Jooosi Mail → Connections and choose New connection.
  2. Enter a descriptive Connection name and select Scaleway 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 API region field is optional and is not shown for SMTP. Keep the project identifier and credential from the same Scaleway project.

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.
  • For API delivery, check both the project ID and API key fields, then confirm the optional region value is the one configured for that project. For SMTP, enter the project ID as the username and the API key as the password; those SMTP fields have different labels from the API fields.