Send WordPress email through SendGrid
Twilio SendGrid is a long-standing sending service used by sites of every size, with detailed delivery statistics on its side, and one API key is all the SMTP login it needs.
- SMTP, through Custom SMTP
How BooleanSMTP sends through SendGrid
Through the Custom SMTP connection
In BooleanSMTP, add a mailer, choose Custom SMTP, and enter SendGrid’s SMTP server below with your SendGrid SMTP login. Logging, the fallback, retries and alerts work exactly as they do for every other connection.
| SMTP host | Port | Encryption |
|---|---|---|
| smtp.sendgrid.net | 587 | TLS |
| smtp.sendgrid.net | 2525 | TLS |
| smtp.sendgrid.net | 465 | SSL |
- Username
apikey, exactly as written- Password
- An API key with the Mail Send permission (Settings → API Keys)
SendGrid sends only from a verified sender: authenticate your domain or verify a single sender first.
Checked against SendGrid’s SMTP documentation.
Before you connect
Authenticate your sending domain in SendGrid and create an API key with permission to send mail. SendGrid’s SMTP login is the fixed username apikey with that key as the password. Use a From address on the domain you authenticated.
Setup guide: Custom SMTP connectionsPair it with a fallback
A revoked or expired API key stops every send at once. A fallback on a different provider means the next password-reset email still goes out while you replace the key.
When SendGrid refuses a message, BooleanSMTP tries your fallback connection at once, logs which one delivered it, and alerts you on Slack, Discord or Telegram only if every attempt fails. See the whole path
What SendGrid receives
Only what sending needs: each message (recipients, subject, body, headers, attachments) and the credentials you enter for the connection, sent to SendGrid when WordPress sends an email. BooleanSMTP stores those credentials encrypted in your own database. Read SendGrid’s terms and privacy policy.