Skip to content
Jooosi
Account
JM Jooosi Mail

Provider profiles and transports

Compare the built-in provider profiles, transport schemes, and fields before creating a connection.

Browse documentation
Overview
Contents
On this page
  1. Choose a profile
  2. Available provider families
  3. Connection fields

Profiles provide the provider-specific fields, transport schemes, and webhook behavior that Jooosi Mail needs to build a connection.

Choose a profile#

  • Use SMTP when your provider gives you a server, port, username, and password.
  • Choose a provider profile when you want its API transport and credential fields.
  • Use Sendmail, Native, or Null only when their local or test behavior fits your setup.

Available schemes and required fields depend on the profile. Check the current catalog on your site with:

wp jooosi-mail connection:profiles

The command lists profile IDs, supported schemes, required fields, and webhook support. Use its output as the authoritative list for the installed version.

Available provider families#

The catalog includes AhaSend, Azure, Bird, Brevo, Cloudflare, Elastic Email, Emailit, Gmail, Infobip, MailerSend, Mailgun, Mailjet, MailKite, Mailomat, MailPace, Mailtrap, Mandrill, Microsoft Graph, Pepipost, PufferPost, Postal, Postmark, Resend, Scaleway, SendGrid, SendLayer, SendPulse, Amazon SES, SMTP2GO, SMTP.com, SparkPost, Sweego, toSend, TurboSMTP, ZeptoMail, and Zoho Mail.

Connection fields#

Enter credentials in the profile’s matching fields. Leave Raw DSN override empty to let Jooosi Mail build the transport from the selected profile and scheme. A raw DSN replaces that generated transport, so only use it when you specifically need a custom transport string.

Continue to connect a provider after choosing a profile.