Documentation
Welcome to the PRO Mail SMTP Documentation page. Here you’ll find detailed guides and instructions to help you easily install, configure, and optimize our SMTP plugin for WordPress, ensuring reliable email delivery for your website.
General Setup
- Navigate to Pro Mail SMTP → Settings
- Configure your default “From Email” and “From Name”
- Choose whether to enable email summaries and set your preferred frequency
Adding Email Providers
- Go to Pro Mail SMTP → Providers
- Click Add Provider
- Select your email service provider
- Enter your credentials:
- For SMTP: Server, port, username, password, encryption type
- For API-based services: API key and required settings
- For OAuth services: Follow the authentication flow
- Set a priority level for each provider (lower numbers = higher priority)
- Test the connection before saving
Email Routing (Optional)
- Navigate to Pro Mail SMTP → Email Router
- Create rules to route specific emails through particular providers
- Set conditions based on recipient email, source plugin, or other factors
Third-Party Services
Pro Mail SMTP connects to various third-party email service providers to send your WordPress site’s emails. When you configure and use these services, your site will transmit data to these external services. Below is information about each service:
Google / Gmail
Privacy Policy: Google’s Privacy Policy is available here: https://policies.google.com/privacy
Service Description: This integration allows your WordPress site to send emails using your Gmail or Google Workspace account via the official Google APIs, typically using OAuth 2.0 for secure authentication.
What data is sent and when:
Authentication: When you authorize the plugin to connect to your Google account, authentication data (such as OAuth 2.0 tokens, Client ID, and Client Secret, if applicable) is exchanged with Google’s authentication servers (e.g., https://accounts.google.com/o/oauth2/v2/auth
, https://oauth2.googleapis.com/token
) to securely link your account. This happens during the setup process for the Gmail mailer.
Email Transmission: When an email is sent from your WordPress site using a configured Gmail connection, the email content (including sender address, recipient(s) address(es), subject, body, headers, and any attachments) is transmitted to Google’s email sending servers (e.g., https://www.googleapis.com/gmail/v1/users/me/messages/send
) for delivery.
Service Provider: Google LLC
Terms of Service: You can find Google’s Terms of Service here: https://policies.google.com/terms
Brevo (formerly Sendinblue)
- Service Description: This integration allows your WordPress site to send emails using the Brevo (formerly Sendinblue) email service via their API.
- What data is sent and when:
- Authentication: When you configure the plugin to use Brevo, your API key is stored by the plugin. This API key is sent to Brevo’s API endpoints (e.g.,
https://api.brevo.com/v3/...
) for authentication with each email sent from your WordPress site. - Email Transmission: When an email is sent from your WordPress site using a configured Brevo connection, the email content (including sender address, recipient(s) address(es), subject, body, headers, and any attachments) is transmitted to Brevo’s servers for delivery.
- Authentication: When you configure the plugin to use Brevo, your API key is stored by the plugin. This API key is sent to Brevo’s API endpoints (e.g.,
- Service Provider: Brevo
- Terms of Service: You can find Brevo’s Terms of Use here: https://www.brevo.com/legal/termsofuse/
- Privacy Policy: Brevo’s Privacy Policy is available here: https://www.brevo.com/legal/privacy-policy/
Microsoft / Outlook / Office 365
- Service Description: This integration allows your WordPress site to send emails using your Outlook.com or Microsoft 365 account via Microsoft’s APIs, typically using OAuth 2.0 for secure authentication.
- What data is sent and when:
- Authentication: When you authorize the plugin to connect to your Microsoft account, authentication data (such as OAuth 2.0 tokens, Client ID, and Client Secret, if applicable) is exchanged with Microsoft’s authentication servers (e.g.,
https://login.microsoftonline.com/common/oauth2/v2.0/authorize
,https://login.microsoftonline.com/common/oauth2/v2.0/token
) to securely link your account. This happens during the setup process for the Outlook/Microsoft mailer. - Email Transmission: When an email is sent from your WordPress site using a configured Microsoft connection, the email content (including sender address, recipient(s) address(es), subject, body, headers, and any attachments) is transmitted to Microsoft’s email sending servers (e.g., via the Microsoft Graph API) for delivery.
- Authentication: When you authorize the plugin to connect to your Microsoft account, authentication data (such as OAuth 2.0 tokens, Client ID, and Client Secret, if applicable) is exchanged with Microsoft’s authentication servers (e.g.,
- Service Provider: Microsoft Corporation
- Terms of Service: You can find the Microsoft Services Agreement here: https://www.microsoft.com/en-us/servicesagreement/
- Privacy Policy: Microsoft’s Privacy Statement is available here: https://privacy.microsoft.com/en-us/privacystatement
Mailgun
- Service Description: This integration allows your WordPress site to send emails using the Mailgun email service via their API.
- What data is sent and when:
- Authentication: When you configure the plugin to use Mailgun, your API key and sending domain are stored by the plugin. The API key is sent to Mailgun’s API endpoints (e.g.,
https://api.mailgun.net/v3/...
) for authentication with each email sent from your WordPress site. - Email Transmission: When an email is sent from your WordPress site using a configured Mailgun connection, the email content (including sender address, recipient(s) address(es), subject, body, headers, and any attachments) is transmitted to Mailgun’s servers for delivery.
- Authentication: When you configure the plugin to use Mailgun, your API key and sending domain are stored by the plugin. The API key is sent to Mailgun’s API endpoints (e.g.,
- Service Provider: Mailgun Technologies, Inc.
- Terms of Service: You can find Mailgun’s Terms of Service here: https://www.mailgun.com/terms/
- Privacy Policy: Mailgun’s Privacy Policy is available here: https://www.mailgun.com/privacy-policy/
Postmark
- Service Description: This integration allows your WordPress site to send emails using the Postmark transactional email service via their API.
- What data is sent and when:
- Authentication: When you configure the plugin to use Postmark, your Server API Token is stored by the plugin. This token is sent to Postmark’s API endpoints (e.g.,
https://api.postmarkapp.com/email
) for authentication with each email sent from your WordPress site. - Email Transmission: When an email is sent from your WordPress site using a configured Postmark connection, the email content (including sender address, recipient(s) address(es), subject, body, headers, and any attachments) is transmitted to Postmark’s servers for delivery.
- Authentication: When you configure the plugin to use Postmark, your Server API Token is stored by the plugin. This token is sent to Postmark’s API endpoints (e.g.,
- Service Provider: Wildbit LLC (the company behind Postmark)
- Terms of Service: You can find Postmark’s Terms of Service here: https://postmarkapp.com/terms-of-service
- Privacy Policy: Wildbit’s Privacy Policy (covering Postmark) is available here: https://wildbit.com/privacy-policy
SendGrid
- Service Description: This integration allows your WordPress site to send emails using the SendGrid email delivery service via their API.
- What data is sent and when:
- Authentication: When you configure the plugin to use SendGrid, your API key is stored by the plugin. This API key is sent to SendGrid’s API endpoints (e.g.,
https://api.sendgrid.com/v3/mail/send
) for authentication with each email sent from your WordPress site. - Email Transmission: When an email is sent from your WordPress site using a configured SendGrid connection, the email content (including sender address, recipient(s) address(es), subject, body, headers, and any attachments) is transmitted to SendGrid’s servers for delivery.
- Authentication: When you configure the plugin to use SendGrid, your API key is stored by the plugin. This API key is sent to SendGrid’s API endpoints (e.g.,
- Service Provider: Twilio Inc. (the company behind SendGrid)
- Terms of Service: You can find SendGrid’s Terms of Service here: https://sendgrid.com/policies/tos/
- Privacy Policy: SendGrid’s Privacy Policy is available here: https://sendgrid.com/policies/privacy/
SMTP2GO
- Service Description: This integration allows your WordPress site to send emails using the SMTP2GO email delivery service via their API or SMTP.
- What data is sent and when (API Method):
- Authentication: When you configure the plugin to use SMTP2GO via API, your API key is stored by the plugin. This API key is sent to SMTP2GO’s API endpoints (e.g.,
https://api.smtp2go.com/v3/...
) for authentication with each email sent. - Email Transmission: When an email is sent using a configured SMTP2GO API connection, the email content (including sender address, recipient(s) address(es), subject, body, headers, and any attachments) is transmitted to SMTP2GO’s servers.
- Authentication: When you configure the plugin to use SMTP2GO via API, your API key is stored by the plugin. This API key is sent to SMTP2GO’s API endpoints (e.g.,
- What data is sent and when (SMTP Method):
- Authentication: If configured via SMTP, your SMTP credentials (hostname, port, username, password) are sent to SMTP2GO’s SMTP servers for authentication with each email.
- Email Transmission: When an email is sent using a configured SMTP2GO SMTP connection, the email content is transmitted to SMTP2GO’s SMTP servers.
- Service Provider: SMTP2GO
- Terms of Service: You can find SMTP2GO’s Terms of Service here: https://www.smtp2go.com/terms-of-service/
- Privacy Policy: SMTP2GO’s Privacy Policy is available here: https://www.smtp2go.com/privacy-policy/
SparkPost
- Service Description: This integration allows your WordPress site to send emails using the SparkPost email delivery service via their API.
- What data is sent and when:
- Authentication: When you configure the plugin to use SparkPost, your API key is stored by the plugin. This API key is sent to SparkPost’s API endpoints (e.g.,
https://api.sparkpost.com/api/v1/...
) for authentication with each email sent from your WordPress site. - Email Transmission: When an email is sent from your WordPress site using a configured SparkPost connection, the email content (including sender address, recipient(s) address(es), subject, body, headers, and any attachments) is transmitted to SparkPost’s servers for delivery.
- Authentication: When you configure the plugin to use SparkPost, your API key is stored by the plugin. This API key is sent to SparkPost’s API endpoints (e.g.,
- Service Provider: Message Systems, Inc. (SparkPost)
- Terms of Service: You can find SparkPost’s Terms of Use here: https://www.sparkpost.com/policies/tou/
- Privacy Policy: SparkPost’s Privacy Policy is available here: https://www.sparkpost.com/policies/privacy/
TurboSMTP
- Service Description: This integration allows your WordPress site to send emails using the TurboSMTP transactional email service.
- What data is sent and when:
- Authentication: When you configure the plugin to use TurboSMTP, your API key (and potentially username/password) is stored by the plugin and sent to TurboSMTP’s API endpoint (e.g.,
https://api.turbo-smtp.com/api/v2/mail/send
) for authentication with each email sent. - Email Transmission: When an email is sent from your WordPress site using a configured TurboSMTP connection, the email content (including sender address, recipient(s) address(es), subject, body, headers, and any attachments) is transmitted to TurboSMTP’s servers for delivery.
- Authentication: When you configure the plugin to use TurboSMTP, your API key (and potentially username/password) is stored by the plugin and sent to TurboSMTP’s API endpoint (e.g.,
- Service Provider: Delivery Media S.R.L. (the company behind TurboSMTP)
- Terms of Service: You can find TurboSMTP’s Terms and Conditions here: https://www.serversmtp.com/terms-and-conditions/
- Privacy Policy: TurboSMTP’s Privacy Policy is available here: https://www.serversmtp.com/privacy-policy/
Other SMTP Servers (Generic SMTP)
- Service Description: This integration allows your WordPress site to send emails using any standard SMTP server you configure (e.g., your web host’s mail server, or other third-party SMTP providers not explicitly listed above).
- What data is sent and when:
- Authentication: When you configure a generic SMTP connection, your SMTP credentials (hostname, port, username, password, encryption type) are stored by the plugin. These credentials are sent to your configured SMTP server for authentication each time an email is sent from your WordPress site. We recommend using constants defined in
wp-config.php
for sensitive data like passwords where possible. - Email Transmission: When an email is sent from your WordPress site using a configured generic SMTP connection, the email content (including sender address, recipient(s) address(es), subject, body, headers, and any attachments) is transmitted to your configured SMTP server for delivery.
- Authentication: When you configure a generic SMTP connection, your SMTP credentials (hostname, port, username, password, encryption type) are stored by the plugin. These credentials are sent to your configured SMTP server for authentication each time an email is sent from your WordPress site. We recommend using constants defined in
- Service Provider: This will be the specific SMTP provider you have chosen to configure.
- Terms of Service & Privacy Policy: You are responsible for obtaining and reviewing the terms of service and privacy policy of the specific SMTP provider you configure. These documents will be provided by that third-party service.