VR SMTP Mailer replaces the default WordPress mail transport with SMTP or an OAuth-based mail API, with full support for Microsoft 365 (Office365), Outlook SMTP, and Microsoft Graph API.<\/p>\n\n
It is designed as a complete email solution for WordPress \u2014 combining SMTP delivery, OAuth authentication, and API-based sending in a single plugin, without requiring multiple paid extensions.<\/p>\n\n
Send emails using either SMTP or an OAuth-based mail API (Graph-compatible).\nWorks with wp_mail() (for immediate sends):\nWhen WordPress sends emails through this plugin, it keeps the same structure as the default wp_mail() function. This includes support for multiple recipients, subject, message body, headers (From, Cc, Bcc, Reply-To, Content-Type), attachments, and inline images where supported.\nStandard WordPress filters like wp_mail, wp_mail_from, wp_mail_content_type, and phpmailer_init are applied in SMTP mode, so behavior remains consistent with native WordPress email handling.\nGraph API limitations:\nWhen using the Graph API, emails support HTML or plain text content, along with To, Cc, Bcc, and Reply-To fields. Attachments and inline images are supported, but typically limited to around 3 MB per file.\nCustom MIME headers are not fully supported, and only standard fields are mapped to the API. More complex email structures may behave differently compared to traditional PHP mail handling.\nEmail queue (WP-Cron):\nEmails can be queued and processed later using WP-Cron. Queued emails store only basic details such as recipient, subject, and message body. Attachments, headers, and inline images are not included in queued jobs.\nAutomatic OAuth token refresh:\nAccess tokens are refreshed automatically to ensure uninterrupted email delivery.\nSecure OAuth handling:\nToken exchange (authorization code to access\/refresh tokens) is restricted to users with administrator-level permissions (manage_options). You must be logged in as an admin when completing the OAuth connection.\nTesting tools included:\nIncludes a built-in test email feature and an SMTP connection tester to help verify configuration.\nLogging and debugging:\nEmail activity and debug information are stored in custom database tables for troubleshooting and monitoring.<\/p>\n\n
Security and stored secrets<\/p>\n\n
This plugin stores SMTP passwords, OAuth client secrets, refresh tokens, and access tokens in the WordPress options table, using the same approach as most WordPress settings. These values are not encrypted at rest.<\/p>\n\n
Anyone with access to the database, a full site backup, or an administrator account could potentially view this information. It\u2019s recommended to use strong admin credentials, secure hosting, and limit your app permissions to only what is required.<\/p>\n\n
This plugin is not affiliated with or endorsed by Microsoft. Microsoft, Microsoft 365, Azure, Office, and related names are trademarks of Microsoft Corporation. These names are used only to describe compatibility and technical functionality.<\/p>\n\n
Do not use Microsoft or related logos, branding, or visual assets in your plugin icon, banner, or screenshots on WordPress.org. Use your own branding and neutral visuals.<\/p>\n\n
Third-party services<\/p>\n\n
This plugin connects to external services only when required for email delivery or authentication. It does not send general site traffic or unrelated data to third parties.<\/p>\n\n
Microsoft identity platform (OAuth2) \u2014 login.microsoftonline.com<\/p>\n\n
What it is\nThis is Microsoft\u2019s OAuth2 authentication service (also known as the Microsoft Identity Platform or Entra ID). It is used when you connect your account using OAuth.<\/p>\n\n
What it is used for<\/p>\n\n
Signing in through Microsoft\nExchanging authorization codes for access and refresh tokens\nRefreshing expired access tokens<\/p>\n\n
What data is sent and when<\/p>\n\n
During login (via browser): client ID, redirect URI, requested scopes (such as Mail.Send, User.Read), and a state parameter for security\nDuring token exchange (server-side): authorization code, client ID, client secret, redirect URI, grant type, and scopes<\/p>\n\n
Terms\nhttps:\/\/www.microsoft.com\/servicesagreement<\/p>\n\n
Privacy\nhttps:\/\/privacy.microsoft.com\/privacystatement<\/p>\n\n
Microsoft Graph API \u2014 graph.microsoft.com<\/p>\n\n
What it is\nMicrosoft\u2019s API for accessing Microsoft 365 services, including sending emails.<\/p>\n\n
What it is used for\nSending emails through the Graph API (\/v1.0\/me\/sendMail).<\/p>\n\n
What data is sent and when\nWhen an email is sent (including test emails), the plugin makes a secure HTTPS request that includes:<\/p>\n\n
An OAuth access token\nEmail details such as recipients, subject, message body, and optional Cc\/Bcc\/Reply-To\nAttachments or inline images (within API limits)<\/p>\n\n
Terms\nhttps:\/\/www.microsoft.com\/servicesagreement<\/p>\n\n
Privacy\nhttps:\/\/privacy.microsoft.com\/privacystatement<\/p>\n\n
Note: Use of Microsoft APIs is also subject to Microsoft\u2019s developer and product terms. Refer to https:\/\/www.microsoft.com\/legal\/\n for details.<\/p>\n\n
User-configured SMTP server<\/p>\n\n
What it is\nAn SMTP server that you configure (for example, your hosting provider, Microsoft 365, Google Workspace, or another email service).<\/p>\n\n
What it is used for\nSending emails using your SMTP credentials.<\/p>\n\n
What data is sent and when\nWhenever an email is sent (including test emails), the plugin transmits:<\/p>\n\n
SMTP credentials (if configured)\nEmail content such as recipients, subject, and message body<\/p>\n\n
This plugin does not control or manage the infrastructure of your SMTP provider.<\/p>\n\n
Terms and privacy\nYou are responsible for reviewing the terms and privacy policy of your email provider. This plugin does not replace or override those agreements.<\/p>\n\n\n
vr-smtp-mailer<\/code> folder to the \/wp-content\/plugins\/<\/code> directory.<\/li>\n- Activate the plugin through the \"Plugins\" menu in WordPress.<\/li>\n
- Go to VR SMTP Mailer \u2192 Settings<\/strong> to configure:\n\n
\n- Choose provider (SMTP or Graph OAuth mail).<\/li>\n
- Enter SMTP host, username, password, and port, or tenant ID, client ID, and client secret for OAuth.<\/li>\n
- Set From Email and From Name.<\/li>\n
- Enable Debug Mode if desired.<\/li>\n<\/ul><\/li>\n
- For Graph OAuth mail:\n\n
\n- Save settings, then click Sign in to connect<\/strong> and complete the OAuth consent.<\/li>\n
- Add the Authorization Redirect URI<\/strong> shown on the settings page to your cloud identity app registration (for example
https:\/\/yoursite.com\/vr-smtp-mailer-oauth<\/code>). Legacy paths \/vr-smtp-oauth<\/code> and \/m365-mailer-oauth<\/code> still work if you registered those URLs earlier.<\/li>\n<\/ul><\/li>\n- Use VR SMTP Mailer \u2192 Test Email<\/strong> to verify sending.<\/li>\n
- Use VR SMTP Mailer \u2192 SMTP Tester<\/strong> to verify SMTP connectivity.<\/li>\n<\/ol>\n\n\n
\nDoes this plugin replace the default `wp_mail` behavior?<\/h3><\/dt>\nYes. Emails are queued and delivered via the configured provider (SMTP or Graph OAuth mail) using WP-Cron.<\/p><\/dd>\n
Does it require WP-Cron to be enabled?<\/h3><\/dt>\nYes. The queue worker runs on a custom five-minute cron schedule.<\/p><\/dd>\n
Why does the readme list \u201cvinodkram\u201d under Contributors?<\/h3><\/dt>\nWordPress.org uses contributor profile usernames<\/strong> (slugs), not display names. List your WordPress.org username exactly as it appears in your profile URL (https:\/\/profiles.wordpress.org\/username\/<\/code>).<\/p><\/dd>\n