Rutvik Panchal

Trumailo verifies every email address submitted to your WordPress site — in real time, with one drop-in plugin — and stops fake, throwaway, mistyped, and risky addresses before they touch your CRM, mailing list, or order pipeline.
<h4>Why bother</h4>
<ul>
<li>Spam signups inflate your list and tank deliverability.</li>
<li>Disposable inboxes (Mailinator, 10MinuteMail, etc.) never convert.</li>
<li>Typo’d emails (<code>gmial.com</code>, <code>yhaoo.com</code>) are lost forever.</li>
<li>Role addresses (<code>admin@</code>, <code>info@</code>) hurt sender reputation.</li>
</ul>
Trumailo catches all of those at the form, with a friendly inline message.
<h4>Works out of the box with</h4>
<ul>
<li>WordPress core (registration, comments, REST users)</li>
<li>WooCommerce (classic checkout, block checkout, registration)</li>
<li>Easy Digital Downloads</li>
<li>Contact Form 7</li>
<li>WPForms</li>
<li>Gravity Forms</li>
<li>Ninja Forms</li>
<li>Fluent Forms</li>
<li>Elementor Pro Forms</li>
<li>Forminator</li>
<li>Formidable Forms</li>
<li>MailPoet</li>
<li>FluentCRM</li>
<li>Mailchimp for WordPress</li>
<li>Newsletter (by Stefano Lissa)</li>
<li>Groundhogg</li>
<li>BuddyPress</li>
<li>Ultimate Member</li>
<li>MemberPress</li>
<li>LearnDash</li>
</ul>
No configuration per integration — add your API key, the plugin detects what’s installed and starts verifying.
<h4>Features</h4>
<ul>
<li>Server-side blocking — survives JavaScript-disabled bots; the rejection happens during form validation.</li>
<li>Real-time inline validation — debounced typing check with “did you mean” suggestions and accessible status badges.</li>
<li>Per-status policy — choose what to block: invalid, disposable, risky, role addresses, or anything below a quality threshold.</li>
<li>Whitelist / blacklist — skip the API for trusted internal domains; always reject specific bad ones.</li>
<li>Cache — repeat verifications served instantly from local transients (configurable TTL).</li>
<li>Fail-open by default — if the API is unreachable, submissions go through (configurable to fail-closed).</li>
<li>Verification log — opt-in, with optional email-hashing for GDPR compliance and configurable retention.</li>
<li>Dashboard — counts of allowed, blocked, cached, and per-day trend.</li>
<li>REST endpoint — for custom front-ends and third-party integrations (<code>/wp-json/trumailo/v1/verify</code>).</li>
<li>Multisite-aware, i18n-ready, GPL-2.0.</li>
</ul>
<h4>Getting started</h4>
<ol>
<li>Install and activate the plugin.</li>
<li>Get an API key at https://trumailo.com.</li>
<li>Settings → Trumailo → paste the key.</li>
<li>Done — every supported form on your site is now verifying emails.</li>
</ol>
<h3>External services</h3>
This plugin connects to the Trumailo email-verification API to determine whether each submitted email address is deliverable. The API is provided by Trumailo (https://trumailo.com), the same vendor that publishes this plugin.
What the service is and what it is used for
Trumailo is a real-time email-verification API. It checks an address for syntactically-valid format, MX records, disposable / role / catch-all signals, and (where the recipient mail server cooperates) an SMTP-level deliverability probe. The plugin uses it so your site can reject invalid, disposable, and risky addresses before they enter your forms, lists, or checkout.
What data is sent and when
<ul>
<li>The plugin sends the email address being verified to <code>https://api.trumailo.com/v1/verify</code> over HTTPS, together with your API key in the <code>Authorization: Bearer</code> header. This happens every time a supported form is submitted with a value the plugin hasn’t already cached.</li>
<li>The plugin sends a lightweight request to <code>https://api.trumailo.com/v1/account</code> to read the calling key’s remaining monthly credits. This is used to populate the credits gauge on the plugin dashboard and is polled at most every 5 minutes.</li>
<li>No other personal data, form fields, page URLs, or visitor identifiers are transmitted.</li>
<li>Verification results are cached locally in WordPress transients to minimise repeat API calls; you can configure the TTL and toggle full-email vs hashed-email storage in the plugin settings.</li>
</ul>
Service provider, terms, and privacy
<ul>
<li>Service: Trumailo — https://trumailo.com</li>
<li>Terms of Service: https://trumailo.com/terms</li>
<li>Privacy Policy: https://trumailo.com/privacy</li>
</ul>
Use of this plugin requires that you (the site owner) agree to Trumailo’s Terms of Service and Privacy Policy linked above. You should disclose Trumailo as a sub-processor in your own site’s privacy notice if you operate in a jurisdiction that requires such disclosure.

Trumailo — Email Verification

Real-time email verification for WordPress. Block invalid, disposable, and risky emails before they enter your forms, lists, or checkout.

Md Monirul Alom

Integration for MailPoet and CF7 connects Contact Form 7 and MailPoet in a practical, admin-friendly workflow.
After enabling the plugin, you get a CF7 Integration submenu under MailPoet where you can:
<ul>
<li>Select a Contact Form 7 form from a form list</li>
<li>Map CF7 fields to MailPoet subscriber fields</li>
<li>Choose one or more MailPoet lists per form</li>
<li>Review sync errors from the integration screen</li>
</ul>
The plugin includes a dedicated CF7 form-tag generator for <code>mailpoet_signup_consent</code>, including privacy-policy link support.
Key behavior:
<ul>
<li>Subscribers are added only when <code>mailpoet_signup_consent</code> is checked</li>
<li>MailPoet Email must be mapped to a CF7 email-type field</li>
<li>A form must contain exactly one <code>mailpoet_signup_consent</code> tag for configuration</li>
<li>Error logs are stored in a dedicated custom database table</li>
</ul>

Integration for MailPoet and CF7

Map Contact Form 7 submissions to MailPoet subscribers with per-form field mapping, consent control, list selection, and error logging.

Trumailo — Email Verification vs Integration for MailPoet and CF7