GHOSTONIX MAIL SMTP
Ghostonix Mail SMTP compatibility with REEID Translate
Ghostonix Mail SMTP compatibility with REEID Translate is being evaluated from available plugin evidence. Controls outgoing WordPress and WooCommerce sender identity by forcing From Name and From Email headers No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Ghostonix Mail SMTP.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Ghostonix Mail SMTP is documented in the Security category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Ghostonix Mail SMTP compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Controls outgoing WordPress and WooCommerce sender identity by forcing From Name and From Email headers
- Optionally forces Reply-To Name and Reply-To Email headers for outgoing site emails
- Optional SMTP delivery: routes outgoing mail through a user-configured SMTP server (host/port/encryption/username/password)
- Provides a test email tool and local sent/failed email logs stored in the WordPress database
- WooCommerce-compatible sender control for WooCommerce emails (sender identity via WordPress mail)
- Stores plugin settings and local email logs in the WordPress database; does not transmit email content, SMTP settings, SMTP credentials, or local mail logs to Ghostonix servers
- Does not generate DNS authentication records (CNAME, DKIM, SPF, DMARC); DNS authentication is handled by the site’s email provider/domain host
CONTENT BOUNDARY
Ghostonix Mail SMTP capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Ghostonix Mail SMTP and REEID Translate FAQ.
What does Ghostonix Mail SMTP do according to the available plugin evidence?
Ghostonix Mail SMTP has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Ghostonix Mail SMTP?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Ghostonix Mail SMTP?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Ghostonix Mail SMTP in a multilingual WordPress workflow.
REEID documents Ghostonix Mail SMTP functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.