Rutvik Panchal

<p><strong>Trumailo</strong> 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 <em>before</em> they touch your CRM, mailing list, or order pipeline.</p>
<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>
<p>Trumailo catches all of those at the form, with a friendly inline message.</p>
<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>
<p>No configuration per integration — add your API key, the plugin detects what’s installed and starts verifying.</p>
<h4>Features</h4>
<ul>
<li><strong>Server-side blocking</strong> — survives JavaScript-disabled bots; the rejection happens during form validation.</li>
<li><strong>Real-time inline validation</strong> — debounced typing check with “did you mean” suggestions and accessible status badges.</li>
<li><strong>Per-status policy</strong> — choose what to block: invalid, disposable, risky, role addresses, or anything below a quality threshold.</li>
<li><strong>Whitelist / blacklist</strong> — skip the API for trusted internal domains; always reject specific bad ones.</li>
<li><strong>Cache</strong> — repeat verifications served instantly from local transients (configurable TTL).</li>
<li><strong>Fail-open by default</strong> — if the API is unreachable, submissions go through (configurable to fail-closed).</li>
<li><strong>Verification log</strong> — opt-in, with optional email-hashing for GDPR compliance and configurable retention.</li>
<li><strong>Dashboard</strong> — counts of allowed, blocked, cached, and per-day trend.</li>
<li><strong>REST endpoint</strong> — for custom front-ends and third-party integrations (<code>/wp-json/trumailo/v1/verify</code>).</li>
<li><strong>Multisite-aware</strong>, <strong>i18n-ready</strong>, <strong>GPL-2.0</strong>.</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 <span aria-hidden="true" class="wp-exclude-emoji">→</span> Trumailo <span aria-hidden="true" class="wp-exclude-emoji">→</span> paste the key.</li>
<li>Done — every supported form on your site is now verifying emails.</li>
</ol>
<h3>External services</h3>
<p>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.</p>
<p><strong>What the service is and what it is used for</strong></p>
<p>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.</p>
<p><strong>What data is sent and when</strong></p>
<ul>
<li>The plugin sends the <strong>email address being verified</strong> 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>
<p><strong>Service provider, terms, and privacy</strong></p>
<ul>
<li>Service: <strong>Trumailo</strong> — https://trumailo.com</li>
<li>Terms of Service: https://trumailo.com/terms</li>
<li>Privacy Policy: https://trumailo.com/privacy</li>
</ul>
<p>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.</p>


Trumailo — Email Verification

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

Tikweb Management

<p>Automatic mail bounce handling for MailPoet 3, for installations using your own SMTP server. Install the plugin and find <code>Bounce Handling</code> menu under the MailPoet menu to setup.</p>
<h4>What’s new?</h4>
<ul>
<li>New Action & rules (Change status to Bounce) added in the bounce scenario</li>
<li>Proper e-mail fields validation</li>
<li>Bounced email logs.</li>
</ul>
<h4>Features</h4>
<ul>
<li>Delete bounce emails</li>
<li>Automatic un-subscribing of users from the MailPoet newsletter list, based on bounced emails</li>
<li>Connect with IMAP, POP3 and NNTP</li>
<li>Check bounced emails with selected scheduling settings</li>
</ul>
<h3><a></a>How to translate?</h3>
<p>We use the official WordPress Polyglots translation team and online translation system – which is not very common among plugin authors, and therefore we would like to explain why this is both easier and better for all than the common .pot/.po/.mo files.</p>
<h4>Online web translation</h4>
<p>To make it short, you simply use the online system at https://translate.wordpress.org/projects/wp-plugins/bounce-handler-mailpoet to translate both “Development” and “Development Readme” into your language. And when a translation editor have approved the translations, a language pack will automatically be generated for all websites using our plugin and the language you translated. No need to work with any files at all, WordPress will automatically load the translation, when it is approved by an editor.</p>
<h4>.pot/.po/.mo files</h4>
<p>If you need to have your own texts and translations, you can off course still use Poedit or a plugin like Loco Translate with your own .po files. You can export and download a translation to a .po file from<br />
https://translate.wordpress.org/projects/wp-plugins/bounce-handler-mailpoet -> Choose language -> Choose Development -> Export (at the bottom)<br />
If you add new translations, please consider using the import button at the same place, to import your .po file translations into the online system so everyone may benefit from your translations 🙂</p>
<h4>Online web translation: Editors and approval</h4>
<p>Everyone can edit and add translations for our plugin using the online system at https://translate.wordpress.org/projects/wp-plugins/bounce-handler-mailpoet – this only require that you are logged in with your wordpress.org user name. But only editors may approve translations. So after adding translations for a new language, you should apply to become the Project Translation Editor (PTE) for your language for our plugin, then you may approve your own translations.</p>
<p>Only members of the WordPress Polyglots team can approve new PTEs, which they usually do pretty fast when you have added a full language of translations. To approve a new PTE, the polyglots team member must be a General Translation Editor (GTE) for the language, meaning one that have access to all plugins for the specific language, since the one approving you off course needs to be fluent in your language to be able to read your first translations and check that they are of good quality.</p>
<p>To become PTE, you simply request it at the Polyglots forum.<br />
We suggest you use the example below – exchange xx_XX with your locale (ex. da_DK for danish in Denmark) and XXXXX with your wordpress.org username (ex. mine is kasperta). If your language have several different locales, add an extra line with that locale.<br />
So copy and paste the text below to a new post at https://make.wordpress.org/polyglots/ – and edit locale + user name, and soon you may approve your own translations 🙂<br />
—beginning of forum post—<br />
Hello Polyglots, I have added translations for <a href="https://wordpress.org/plugins/bounce-handler-mailpoet/" rel="ugc">Bounce Handler Mailpoet 3</a> and would like to become the Project Translation Editor (PTE) for my language.<br />
Please add my WordPress.org user as Project Translation Editor (PTE) for the respective locales:<br />
o #xx_XX – @XXXXX<br />
If you have any questions, just comment here. Thank you!</p>
<p>editor-requests</p>
<p>—end of forum post—</p>
<h4>Translations and editors</h4>
<p>See the current translation contributors and editors for our plugin for the different languages at:<br />
https://translate.wordpress.org/projects/wp-plugins/bounce-handler-mailpoet/contributors</p>
<p>See the generated language packs at:<br />
https://translate.wordpress.org/projects/wp-plugins/bounce-handler-mailpoet/language-packs</p>
<p>If the online system have not generated a language pack for your language, it is because:<br />
1. Your texts are not approved, check if they are still in the “waiting” column. If they are, then check if there is an editor (https://translate.wordpress.org/projects/wp-plugins/bounce-handler-mailpoet/contributors) for your language, if not, then request to become an editor.<br />
2. There are not enough texts translated, you need about 90% translated before a translation pack is generated.<br />
3. You have only translated the plugin strings and not the readme. You need above 90% for “Development” and “Development Readme” together, check the percentage of both columns for your language at https://translate.wordpress.org/projects/wp-plugins/bounce-handler-mailpoet</p>


Bounce Handler MailPoet 3

This plugin is very uesefull and easy to setup.
It provides the information about your bad results for specific email addresses.


Very usefull

Automatic mail bounce handling for MailPoet 3 to handle bounce emails easily when using your own SMTP server.

Trumailo — Email Verification vs Bounce Handler MailPoet 3