SEND EMAILS WITH MANDRILL
Send Emails with Mandrill translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Send Emails with Mandrill does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Replaces WordPress `wp_mail()` delivery with Mandrill API-based sending for outgoing emails, including messages with attachments.
- Tracks sent emails and applies automatic tagging so messages appear in Mandrill dashboard statistics.
- Supports adding general tags to all emails and specific tags to selected emails via plugin-defined requirements.
- Allows per-message customization through the `mandrill_payload` filter hook.
- Provides a plugin function, `wpMandrill::mail`, for sending mail from other plugins instead of using native `wp_mail()` directly.
- Supports using Mailchimp/Mandrill templates that have been shared with the connected Mandrill account.
- Accepts the Mandrill API key either in the plugin settings or via the `SEWM_API_KEY` constant in `wp-config.php`.
- Falls back to WordPress `wp_mail()` if Mandrill sending fails, and logs Mandrill responses or debug messages for troubleshooting.
Distinctive features
Replaces WordPress `wp_mail()` delivery with Mandrill API-based sending for outgoing emails, including messages with attachments. Tracks sent emails and applies automatic tagging so messages appear in Mandrill dashboard statistics. Supports adding general tags to all emails and specific tags to selected emails via plugin-defined requirements. Allows per-message customization through the `mandrill_payload` filter hook. Provides a plugin function, `wpMandrill::mail`, for sending mail from other plugins instead of using native `wp_mail()` directly. Supports using Mailchimp/Mandrill templates that have been shared with the connected Mandrill account. Accepts the Mandrill API key either in the plugin settings or via the `SEWM_API_KEY` constant in `wp-config.php`. Falls back to WordPress `wp_mail()` if Mandrill sending fails, and logs Mandrill responses or debug messages for troubleshooting.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Send Emails with Mandrill does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Send Emails with Mandrill and REEID Translate FAQ.
Does the current evidence establish translation scope for Send Emails with Mandrill?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.