

SMTP Configuration
Easily fix WordPress email delivery. Connect Gmail, Outlook/Microsoft 365, SendGrid, Amazon SES, Mailgun, Postmark, Brevo, Cloudflare Email Sending, and more — over their fast API, secure OAuth, or classic SMTP.
Add several sending connections, set a priority order so delivery automatically falls back to the next provider if one fails, see the real delivery status (delivered / bounced) of each email, and get alerts when sending fails — all free.
The default PHP mail() function is often blocked by hosts or filtered as spam. Bit SMTP sends your WordPress email through an authenticated provider instead, so receiving mail servers can trust that it really comes from you.
wp-config.php constants.Every field has help text that explains what it is and where to find it in your provider’s dashboard.
API integrations (paste an API key):
OAuth integrations (one-click Connect, no password stored): Gmail / Google Workspace and Microsoft 365 / Outlook.
Any SMTP server — use Other SMTP for your host, Yahoo, Zoho Mail, or any mailbox. Common settings:
You can also use PHP mail() (the server’s own mailer) when no external provider is configured.
Open Bit SMTP ▸ Settings to add alert channels. Bit SMTP sends one alert when a failure streak starts and one when it recovers, so an outage does not flood your inbox or channel.
https://hooks.slack.com/services/... URL.Use Test notification to check a saved channel. Webhook URLs and bot tokens are encrypted and shown masked. Alerts are best effort: each request has a five-second limit and can never change the outcome of the email that triggered it.
Bit SMTP handles any email sent through WordPress’s wp_mail() — WooCommerce, core notifications, and form plugins such as Bit Form, Contact Form 7, Gravity Forms, WPForms, Ninja Forms, Forminator, Fluent Forms, Formidable Forms, Everest Forms, Elementor Forms, and more.
Join our Bit Apps Community for updates. The full source code is on GitHub; contributions are welcome.
Bit SMTP delivers your site’s email through the provider you choose, so it connects to third-party services. Except for the optional deactivation feedback described below, nothing is contacted until you set up the matching feature. Your email content only ever goes to the email provider you configured.
When you add a connection, every email sent through it — including test emails, resends, and retries — is sent to that provider. Each request contains the full message (sender, To/Cc/Bcc recipients, Reply-To, subject, body, attachments, and headers) and is authenticated with the API key, SMTP login, or OAuth token you entered.
For providers that support it, saving a connection with Track delivery status turned on (the default) also registers your site’s webhook address (https://your-site/bit-smtp/...) with the provider through its API, so it can report delivery events back to your site. Deleting the connection removes that webhook. Turn Track delivery status off to skip this.
api.sendgrid.com. Terms, Privacy.email.<region>.amazonaws.com. If you subscribe your webhook address to Amazon SNS for delivery events, Bit SMTP also confirms that subscription and downloads the SNS signing certificate from sns.<region>.amazonaws.com. Customer Agreement, Service Terms, Privacy.api.mailgun.net or api.eu.mailgun.net. Terms, Privacy.api.postmarkapp.com. Terms, Privacy.api.brevo.com. After a successful connection test, Bit SMTP also reads that test email’s delivery events from Brevo’s statistics API. Terms, Privacy.api.resend.com. Terms, Privacy.api.mailjet.com. Terms, Privacy.api.zeptomail.com, api.zeptomail.eu, or api.zeptomail.in, depending on the data center you pick. Terms, Privacy.api.sparkpost.com or api.eu.sparkpost.com. Terms, Privacy.api.cloudflare.com. Terms, Privacy.accounts.google.com) with your Client ID and From address; Bit SMTP then exchanges the authorization code, and later refreshes the access token, with oauth2.googleapis.com using your Client ID and Secret. Email is sent through the Gmail API (gmail.googleapis.com). Terms, Privacy, API Services User Data Policy.login.microsoftonline.com; email is sent through Microsoft Graph (graph.microsoft.com). Services Agreement, Privacy.Only used when you add an alert channel in Settings. Alerts and test notifications include your site name and address, the connection’s name and provider, the error, and the failed email’s subject and up to 10 recipient addresses — never the email body. Health alerts include the connection’s status and last error.
hooks.slack.com. Terms, Privacy.discord.com. Terms, Privacy.api.telegram.org. Terms, Privacy.Only if you choose to share usage data in the welcome prompt or in Settings; you can stop at any time. The report goes to Bit Apps (wp-api.bitapps.pro) once when you agree and then about once a week. It contains your site name and address, the site admin email and the first administrator’s name, your server’s public IP address, WordPress, PHP, and MySQL versions, your theme and language, a few server settings, user counts by role, the names and versions of your active plugins, the number of inactive plugins, and how many test emails you sent. It never contains email content, recipients, logs, passwords, or API keys. Bit Apps Terms, Bit Apps Privacy.
To find the server’s public IP address, the report asks icanhazip.com, which is operated by Cloudflare. That request sends nothing except the request itself. Cloudflare Privacy.
When you deactivate Bit SMTP, an optional feedback form appears. Only if you choose a reason and submit it, Bit SMTP sends that reason and any text you typed, plus your site address, site language, and plugin version, to Bit Apps (wp-api.bitapps.pro). Choosing Skip sends nothing. Bit Apps Terms, Bit Apps Privacy.
Not an external service: when you turn it on, the tracking image and rewritten links point to your own site (https://your-site/bit-smtp/track/...), and the results are stored in your own database.