Hi! Even though we have “Allow Free Emails” turned off, we noticed that the following email format will still be allowed through -> [email protected] , [email protected]?, [email protected]?etc. It is working great, but we noticed that it will still allow all of these through. Is someone able to take a look at this? Appreciate it! ??
]]>Attempting to install Antideo email validator, and the field label “OTP Value label” is not present inside Gravity Forms, as demonstrated in the set up video???? How am I supposed to set up this form, if this field cannot be set up??
]]>Greetings Antideo, nice to meet you…
?How or where I can find older versions of your plugin? I question this because I have problems with PHP 7.4:
Backend fatal error: PHP Fatal error: Uncaught Error: Call to undefined function str_ends_with() in /home/**********/public_html/wp-content/plugins/antideo-email-validator/antideo-email-validator.php:693
This functions str_ends_with() doesn’t exist in PHP 7.4. and I need to fix the website quickly with a older version while we have a final fix or solution, at this moment we disable the plugin and the site works fine.
Greetings from Venezuela
1: On the main page of Antideo Email Validator plugin, the totals counter shows wrong data. So for example, I got 5 emails for invalid mx records, but counters show “0”.
2: Feature needed: Ability, to reset all counters.
3: Feature needed: Ability, to delete all or chosen emails, from the list below the counters to the bin.
]]>We want to “Allow Free Emails” only for one form. Is it possible to set special settings for certain form, maybe by using hook or customization code snippet?
]]>Hello,
Thanks for providing this plugin.
sharknet.com domain is listed for sale.
For testing reasons I used email id [email protected] and this was accepted as valid email address.
Let me know what kind of email id will be blocked.
Thanks for this plugin
]]>Works great to check some miss typos like hotmail.co, hmail.com, hotmail.co, but I have noticed, it’s blocking other domains that not are reachable, but got an MX record.
For example, “onlcool.com” and “cottagecards.co.uk” is bad host accordingly to Antideo Email Validator, no A record, not pointing to any server, but still got MX records and they can send and receive emails.
Need an option to block if only no MX record, or run a sequence, check host OK – NO, check MX and if MX is existed, allow email to be submitted.
The solution is editing file antideo-email-validator.php
under private function: line 135 – to line 165
‘each update again’ ??
Solutions in mind:
– Going into .po
or reduce the number of ‘case’ into one.
that permit to have a 1 “general input” where user can change text language.
Disallow Free Emails, Generic Emails, Disposable Emails…etc
need to be added by owner himself into is form submit.
Is not your goal.
By the way great job we have to keep this going.
I have Installed and activated the plugin , But does not work with elementor forms. I want to disallow for free email to sumit the form. Is there a any option to configure with elementor forms ?
]]>I’ve tried using this integration with Gravity forms and it simply does not work.
I’ve tested a form entering the email address [email protected] for example and the form still submits.
This plugin doesn’t seem to do anything useful. At least with the latest update, it no longer does anything damaging.
]]>Hi
The plugin does not work as usual since the last update. It blocks now gmail and other wellknown domains. I use the free version. How can I do to avoid blosking gmail, yahoo and……others.
Best
P
v1.0.4 Update is blocking free addresses. Only whitelisted emails I have tested have been successful. Currently using with Gravity Forms.
]]>Will it work with post comment form?
Thanks
]]>on any post editing url in the admin interface, this error pops up before the content:
`
Notice: Function register_rest_route was called incorrectly. The REST API route definition for antideo-email-validator/v1/disposable_emails/(?P[0-9-]+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /www/wp/wp-includes/functions.php on line 5831
Notice: Function register_rest_route was called incorrectly. The REST API route definition for antideo-email-validator/v1/disposable_emails is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /www/wp/wp-includes/functions.php on line 5831
`
]]>Installed and activated the plugin. Tested my Gravity Form.
Was able to submit the form successfully with test @ gmail.con
Uninstalled.
I noticed the existing code in antideo-email-validator.php line 708 (domain blacklisting) does:
$black_listed = false;
foreach($domain_blacklist as $key => $value){
if (stripos($value, $domain) !== false) {
$black_listed = true;
}
}
This potentially could match a blacklist entry of foo.co if the email address was foo.co.uk because foo.co ($value) will be found within foo.co.uk ($domain). These should not match, however as they are different domains. Additionally, trying to blacklist a subdomain like foo.bar.com will accidentally catch ANY bar.com emails, because bar.com ($domain, the ‘needle’ in the search) does appear in foo.bar.com ($value, the ‘haystack’).
The solution would seem to be to do str_ends_with() instead of stripos(), to make sure that the blacklisted domain is found AT THE END of the string being tested, not anywhere within it. This would also allow for blacklisting of entire top level domains (like .xxx or .adult) to catch all domains within the TLD.
A potential implementation would look like
$black_listed = false;
foreach($domain_blacklist as $key => $value){
if (str_ends_with($domain, $value) == true) {
$black_listed = true;
}
}
]]>
I have few contact forms but I need dis allow business email validation for few of them. I am using contact form 7.
]]>Hello, please tell me why the plugin skips some domains. Eg:
I have this email in my whitelist: yandex.ru . That is, it is allowed to register on the site with this mailbox. But only if, for example, you remove one letter in the domain name, then registration also takes place. Example: yanex.ru
I think that this should not be. That is, the system should not allow registration on the site at all with those domains that are not on the white list!
How to make it possible to register only from those addresses that are in the white list?
]]>Hi!
Excellent plugin!
How do we change the error message for the invalid mail? Maybe you can add it to the settings? Or some code?
Thanks!
]]>