A WordPress anti-spam plugin that checks the email address of commenters, registrants (also WooCommerce and multisite) and Contact Form 7 senders. Comments that fail are moved to spam, registrations and forms are refused. Formerly WP-Mail-Validator.
Install it from WordPress.org. This repository is where it is developed.
| # | Check | Details |
|---|---|---|
| 1 | Your blocklist | Regular expressions, one per line, matched case-insensitively |
| 2 | Disposable mail services | 10,000+ domains from disposable-email-domains, updated monthly in this repository and shipped with every release |
| 3 | Syntax | WordPress' is_email() |
| 4 | Mail server | MX record, or A/AAAA record as fallback (RFC 5321); null MX is rejected |
| 5 | Mailbox (optional) | SMTP RCPT TO on port 25, no mail is sent. Rejects only on 5.1.1/5.1.10 (recipient unknown); detects catch-all servers, caches results, skips itself when port 25 is blocked. For comments it runs in the background via WP-Cron by default: the comment is held as pending until the check is done |
Comments of logged-in users are never checked. Pingbacks and trackbacks can be accepted or dropped.
| Plugin | What is checked | Setting | Hook |
|---|---|---|---|
| WooCommerce | New customer accounts (My account, checkout) | Check registrations | woocommerce_registration_errors |
| Multisite | Sign-ups on wp-signup.php |
Check registrations | wpmu_validate_user_signup |
| Contact Form 7 | All email fields | Check Contact Form 7 (off by default, shown if CF7 is active) | wpcf7_validate_email, wpcf7_validate_email* |
Each integration is a small file in includes/integrations/. Forms cannot be held like comments, so with Check the mailbox in the background on, they only use mailbox results that are cached; registrations are always checked completely.
Check addresses in your own forms – with the checks and settings of the plugin:
// Safe to call when the plugin is not active: returns true then.
if ( ! apply_filters( 'wp_mail_validator_is_valid_email', true, $email ) ) {
// refuse the address
}
wp_mail_validator_is_valid_email( $email ); // the same as a functionRejected addresses are counted as blocked spam attacks. For themes:
echo wp_mail_validator_info_label( '<p>', '</p>' ); // <p>Protected by <a …>Mail Validator</a>: <strong>42</strong> spam attacks blocked</p>
echo wp_mail_validator_fended_spam_attack_count(); // 42
echo wp_mail_validator_version(); // the plugin versionRequirements: PHP 7.4+ and Composer – or just Docker.
composer install
composer test # PHPUnit unit tests (Brain Monkey, no WordPress needed)
composer lint # WordPress Coding Standards + PHP compatibility
composer lint:fix # fix what can be fixed automaticallyWithout a local PHP:
docker run --rm -v "$PWD":/app -w /app composer:2 install
docker run --rm -v "$PWD":/app -w /app php:8.4-cli vendor/bin/phpunit| File | Purpose |
|---|---|
wp-mail-validator.php |
Hooks, options, settings page |
includes/class-wp-mail-validator-checker.php |
Syntax, DNS and SMTP checks |
includes/integrations/ |
WooCommerce, Multisite, Contact Form 7 |
data/disposable-email-domains.txt |
Bundled disposable domain list |
readme.txt |
Plugin page on WordPress.org – keep it in sync with releases |
.distignore |
Files that are not shipped to WordPress.org |
CI runs the tests on PHP 7.4 – 8.4, the coding standards and the official Plugin Check on every pull request.
Releases are made by release-please from the pull request titles (Conventional Commits): feat(…): → new minor version (while below 1.0), fix(…): / perf(…): → patch, docs(…):, chore(…):, ci(…):, … → no release. Every title needs one of the scopes listed in .github/workflows/pr-title.yml, e.g. feat(integrations): …, fix(checker): …, and a summary in lowercase without a final period.
- release-please keeps a pull request "chore(release): x.y.z" open. It bumps the version in the plugin header,
WP_MAIL_VALIDATOR_VERSIONand the manifest, and adds the entry toCHANGELOG.md; a workflow copies that entry and theStable tagintoreadme.txt(.github/scripts/sync-readme.py). Edit the changelog in that pull request if you like –readme.txtfollows. - Merge it: release-please creates the tag and the GitHub release.
- Approve the deployment in the Actions tab. The workflow deploys to WordPress.org (SVN) and attaches the zip to the release.
CI checks that all version numbers agree (.github/scripts/check-versions.sh). The upgrade notice in readme.txt is still written by hand, in the release pull request.
Banners, icons and screenshots for the plugin page go into .wordpress-org/ (banner-1544x500.png, icon-256x256.png, screenshot-1.png, …); the deploy workflow uploads them to SVN assets/. Sources and the render command for banner and icon are in assets-src/.
Issues and pull requests are welcome – see CONTRIBUTING.md. Security issues: see SECURITY.md.
GPL-2.0-or-later, like WordPress itself. Versions up to 0.6.5 were released under GPLv3. The bundled disposable domain list is CC0.