內容簡介
Solviroa 是一款針對 WordPress 的電子郵件設置、遷移與診斷工具，旨在幫助管理員了解並修復完整的發送路徑，而不僅僅是儲存 SMTP 憑證。
【主要功能】
• 步驟導向的設置精靈，協助設置發件人身份
• 檢測現有郵件外掛，兼容導入 SMTP 配置
• 提供中立的 SMTP、OAuth 和交易 API 連接方式
• 實施非發送的預檢查，確保測試郵件可行
• 提供可讀的診斷資訊，幫助解決連接問題
• 模擬模式可測試 wp_mail() 行為而不發送郵件
外掛標籤
開發者團隊
② 後台搜尋「Solviroa – Email Setup & Deliverability」→ 直接安裝（推薦）
原文外掛簡介
Solviroa is a guided email setup, migration and diagnostic tool for WordPress. It is designed to help administrators understand and repair the complete sending path instead of only storing SMTP credentials.
Free includes:
A step-by-step setup wizard for the site’s sender identity and connection.
Detection of existing mail plugins and compatible import of existing SMTP configuration where supported.
Provider-neutral SMTP, OAuth and transactional API connection methods.
Non-sending preflight checks before a real test message is attempted.
Human-readable diagnostics for connection, environment and mail-routing problems.
Read-only MX, SPF, DKIM, DMARC and nameserver checks without writing DNS records.
A local assistant that explains the current connection, health state and relevant next steps using data already stored on the site.
Email history with delivery-attempt status and non-secret technical details.
An optional Simulation Mode that lets WordPress exercise wp_mail() flows without contacting the provider or delivering a real message.
What makes Solviroa different?
Solviroa uses a migration-first and diagnostic-first workflow rather than treating email setup as only a credentials form. Its Free workflow combines these steps in one place:
Recover before re-entering: it detects compatible settings from several existing WordPress mail plugins and can import supported SMTP/OAuth configuration as an unverified candidate instead of immediately replacing the current mail route.
Verify before activation: imported or newly entered connections remain pending until Solviroa runs provider/environment checks; the normal setup flow does not activate a connection merely because credentials were saved.
Diagnose the complete path: connection checks, WordPress routing state, mail history and read-only MX/SPF/DKIM/DMARC/nameserver checks are presented together with human-readable explanations.
Test without delivery: Simulation Mode can exercise WordPress wp_mail() behavior without contacting the selected provider or delivering a real message.
Explain local state: the built-in assistant is deterministic and uses the state already stored on the WordPress site; it is not a remote AI/chat service and does not send the administrator’s questions to the developer.
These capabilities are intended to make migration, diagnosis and verification the primary workflow, with SMTP/API/OAuth transport configuration as one part of that workflow.
Solviroa does not claim that an accepted message reached the recipient’s inbox. Provider acceptance and confirmed delivery are different states.
Solviroa Free works independently. Solviroa Pro is a separate optional add-on for continuity features such as multiple connections, fallback, retry, Smart Routing, alerts, compatible delivery confirmation and reports. Free functionality does not require Pro.
External services
Solviroa has no telemetry or analytics service and does not send plugin-usage data to the developer. External connections occur only when an administrator configures or checks a selected mail connection, completes OAuth, explicitly sends mail, or when WordPress itself sends mail through an activated connection.
For provider-based sending, the selected provider can receive credentials or OAuth tokens required for authentication and, when a message is sent, the message data required for delivery. Depending on the provider this can include sender, To/CC/BCC, Reply-To, subject, headers, body and attachments. Credentials and OAuth tokens are stored locally in the WordPress site in encrypted form when the server supports the required cryptography.
Google OAuth
Used when an administrator chooses the Google OAuth connection. Solviroa sends the OAuth client identifier, redirect URI, requested scopes and OAuth protocol values to Google when the administrator starts or completes authorization. After authorization, the access token is sent to Google’s user-information endpoint to identify the authorized account. If the administrator disconnects Google, the stored access or refresh token may be sent to Google’s token-revocation endpoint. Google returns authorization/token data; Solviroa does not receive the user’s normal Google password.
API/authorization endpoints used: accounts.google.com, oauth2.googleapis.com, openidconnect.googleapis.com
Service: Google OAuth
Terms: Google Terms
Privacy: Google Privacy Policy
Gmail API
Used only when Gmail API is the selected sending method. On a send, Solviroa submits the authorized message to Gmail, including the message envelope/content needed for delivery. The openid, email and gmail.send scopes are used by the configured OAuth flow.
API endpoint used: gmail.googleapis.com
OAuth scope identifier used by the authorization flow: www.googleapis.com/auth/gmail.send
Service: Gmail API
Terms: Google APIs Terms
Privacy: Google Privacy Policy
Microsoft OAuth
Used when an administrator chooses Microsoft OAuth. Solviroa sends the OAuth client/application data, redirect URI, requested scopes and OAuth protocol values during authorization. It does not receive the user’s normal Microsoft password.
Authorization/token endpoint domain used: login.microsoftonline.com
Service: Microsoft identity platform
Terms: Microsoft Services Agreement
Privacy: Microsoft Privacy Statement
Microsoft Graph
Used after Microsoft OAuth to read the authorized account identity and to submit mail when Microsoft Graph is the selected method. Current delegated scopes include openid, profile, email, offline_access, User.Read and Mail.Send. Message data is sent only when a message is submitted.
API endpoint domain used: graph.microsoft.com
Service: Microsoft Graph
Terms: Microsoft Services Agreement
Privacy: Microsoft Privacy Statement
Brevo
Used only when Brevo is selected. Solviroa can send the configured API key for an account/preflight check and can submit sender, recipients, subject, headers, body and attachments when sending transactional email.
API endpoint domain used: api.brevo.com
Service: Brevo
Terms: Brevo Terms
Privacy: Brevo Privacy Policy
SendGrid
Used only when SendGrid API is selected. During preflight, Solviroa sends the configured API key plus a small sandbox message payload built from the configured sender and Solviroa preflight text; SendGrid validates the request in Sandbox Mode and does not deliver that preflight message. During a real send, Solviroa sends the configured API key and the message data required for delivery.
API endpoint domain used: api.sendgrid.com
Service: SendGrid
Terms: Twilio Terms
Privacy: Twilio Privacy Notice
Mailgun (US/EU)
Used only when Mailgun API is selected. During preflight, Solviroa sends the configured API key, selected region, sending domain, configured sender and a small Solviroa preflight payload with Mailgun test mode enabled, so the preflight request is validated but not delivered. During a real send, Solviroa sends the configured API key/domain plus the message data required for delivery to the selected US or EU endpoint.
API endpoint domains used: api.mailgun.net (US) and api.eu.mailgun.net (EU)
Service: Mailgun
Terms: Mailgun Terms
Privacy: Mailgun Privacy Policy
Postmark
Used only when Postmark is selected. Solviroa sends the configured server token for server/preflight checks and sends message data to the Email API when a message is submitted.
API endpoint domain used: api.postmarkapp.com
Service: Postmark
Terms: Postmark Terms
Privacy: Postmark Privacy Policy
Resend
Used only when Resend is selected. Solviroa sends the configured API key and message data to Resend when a transactional message is submitted.
API endpoint domain used: api.resend.com
Service: Resend
Terms: Resend Terms
Privacy: Resend Privacy Policy
MailerSend
Used only when MailerSend is selected. Solviroa sends the configured API token for domain/preflight checks and sends message data to the Email API when a message is submitted.
API endpoint domain used: api.mailersend.com
Service: MailerSend
Terms: MailerSend Terms
Privacy: MailerSend Privacy Policy
SMTP2GO
Used only when SMTP2GO API is selected. Solviroa sends the configured API key for account/preflight checks and sends message data to the Email API when a message is submitted.
API endpoint domain used: api.smtp2go.com
Service: SMTP2GO
Terms: SMTP2GO Terms
Privacy: SMTP2GO Privacy Policy
Amazon SES
Used only when Amazon SES is selected. Solviroa signs requests with the configured AWS access credentials and selected region. Account-status requests are sent during preflight; sender, recipients and message content are sent to the regional SES v2 endpoint when email is submitted.
Regional API endpoint pattern used: email.
Service: Amazon SES
Terms: AWS Service Terms
Privacy: AWS Privacy Notice
SparkPost / Bird (US/EU)
Used only when an administrator selects SparkPost as the transactional email provider. During the connection preflight, Solviroa sends the configured SparkPost API key for authentication and the domain part of the configured sender email address to SparkPost’s Sending Domains API so the selected US or EU account can be checked. When WordPress submits a real email through the activated SparkPost connection, Solviroa sends the API key plus the message data required for delivery, which can include the sender, To/CC/BCC recipients, Reply-To, subject, headers, body and attachments, to SparkPost’s Transmissions API. Solviroa does not contact SparkPost unless the administrator has selected/configured SparkPost and runs a connection check or WordPress sends mail through that connection. SparkPost is now part of Bird.
API endpoint used for US accounts: https://api.sparkpost.com/api/v1
API endpoint used for EU accounts: https://api.eu.sparkpost.com/api/v1
Service: SparkPost by Bird
SparkPost Terms of Service: Terms of Service for SparkPost
Current Bird Terms: Bird General Terms and Conditions
Privacy: Bird Privacy Statement
Mailjet
Used only when Mailjet is selected. During preflight, Solviroa sends the configured API credentials plus a small sandbox payload built from the configured sender and Solviroa preflight text; Mailjet validates it in Sandbox Mode without delivering the message. During a real send, Solviroa sends the configured API credentials and the message data required for delivery to Send API v3.1.
API endpoint domain used: api.mailjet.com
Service: Mailjet
Terms: Mailjet Terms
Privacy: Mailjet Privacy Policy
Elastic Email
Used only when Elastic Email is selected. Solviroa sends the configured API key for API-key checks and sends message data to the transactional email endpoint when email is submitted.
API endpoint domain used: api.elasticemail.com
Service: Elastic Email
Terms: Elastic Email Terms
Privacy: Elastic Email Privacy Policy
Preset SMTP services
The following SMTP presets are optional. A network connection to the named SMTP service occurs only when the administrator selects/configures that provider and runs a connection test or when WordPress submits mail through the activated connection. The SMTP service receives the configured authentication data during authentication and receives the message envelope/content when a real message is sent. Simulation Mode stops the message before the provider is contacted.
Hostinger Email — preset for smtp.hostinger.com. Service · Terms · Privacy
Titan Email — preset for smtp.titan.email. Service · Terms · Privacy
Gmail / Google Workspace SMTP — optional app-password SMTP path for smtp.gmail.com; Google OAuth/Gmail API are documented separately above. Service · Terms · Privacy
Microsoft 365 / Outlook SMTP — optional compatibility SMTP path for smtp.office365.com; Microsoft OAuth/Graph are documented separately above. Service · Terms · Privacy
Yahoo Mail SMTP — preset for smtp.mail.yahoo.com using an app password. Service · Terms · Privacy
iCloud Mail SMTP — preset for smtp.mail.me.com using an app-specific password. Service · Terms · Privacy
Zoho Mail SMTP — provider-specific SMTP details are supplied by the administrator because Zoho endpoints can vary by account/data centre. Service · Terms · Privacy
Brevo SMTP Relay — preset for smtp-relay.brevo.com. Service · Terms · Privacy
SendGrid SMTP — preset for smtp.sendgrid.net. Service · Terms · Privacy
MailerSend SMTP — preset for smtp.mailersend.net. Service · Terms · Privacy
User-configured SMTP services
When SMTP is selected, Solviroa connects only to the SMTP server configured or chosen by the administrator. This can include a hosting mailbox or services such as Hostinger, Titan, Gmail, Microsoft 365, Yahoo, iCloud, Zoho, Brevo SMTP, SendGrid SMTP, MailerSend SMTP or another SMTP service. The selected SMTP server receives the authentication data and message envelope/content necessary to deliver the message. The administrator chooses that server, so its own terms, privacy and retention policies apply.
DNS checks
MX, SPF, DKIM, DMARC and nameserver checks use PHP DNS functions and the DNS resolver configured by the website/server environment. They are read-only. Solviroa does not use a hard-coded third-party DNS API and never writes DNS records.
Remote assets and telemetry
Solviroa does not remotely load JavaScript, CSS, fonts, images, iframes or executable plugin code. It does not send analytics or telemetry to the developer. Provider API/OAuth requests described above are made only to provide the selected mail service.
Local privacy and storage
Connection settings and encrypted credentials are stored in WordPress options. Free mail history is stored in the site’s Solviroa table and may include status, category, recipient summary, subject, source, provider, transport, tracking/provider message identifiers, attachment count, retry/temporary flags, technical error details and timestamps. Solviroa Free does not store message bodies or attachment contents in its mail log.
