Provider guides · v2.7

Your provider, and the parts nobody writes down.

The server address, port and encryption fill themselves in when you pick a preset. What actually blocks people is the rest: where the username and password live in the provider’s interface, and the one rule each provider enforces without saying so. One guide per provider, exactly for that.

Twelve presets

Pick yours,
the fields fill themselves.

Every guide answers the same three questions in the same order: where to find your credentials, what to enter in the plugin, and what this provider trips people on.

smtp.gmail.com
Port 587 · TLS

smtp.office365.com
Port 587 · TLS

email-smtp.<region>
Port 587 · TLS

smtp.sendgrid.net
Port 587 · TLS

smtp.mailgun.org
Port 587 · TLS

smtp-relay.brevo.com
Port 587 · TLS

smtp.postmarkapp.com
Port 587 · TLS

in-v3.mailjet.com
Port 587 · TLS

smtp.zoho.com
Port 587 · TLS

smtp.mail.yahoo.com
Port 587 · TLS

smtp.mail.me.com
Port 587 · TLS

smtp.tem.scaleway.com
Port 587 · TLS

Your host

any server, port, login
see below

No preset needed

Using your hosting
company’s server?

Most hosting plans include an SMTP server at no extra cost, and it is often the simplest choice: the mailbox already exists and the DNS is often already right.

Choose Other / Custom in the provider list and fill the fields with what your host gave you. If you cannot find the values, they live in your hosting panel next to your email account, or one message to support gets you all five:

  • Server address, usually something like mail.yourdomain.com or smtp.yourhost.com.
  • Port and encryption, most commonly 587 with TLS, sometimes 465 with SSL.
  • Username, almost always the full email address of the mailbox.
  • The mailbox password, the same one the webmail uses.
  • The sender address, which should be that same mailbox for the mail to be trusted.

Configured, tested, still stuck?

The documentation covers the rest of the plugin: reading the email log, resending a failed message, alerts, and what the common error messages mean.

Read the docs