Issues for Email Verifyhttps://www.drupal.org/project/issues/email_verify?text=&status=All&priorities=All&categories=All&version=All&component=All
enCan not activate modulehttps://www.drupal.org/project/email_verify/issues/2872833
<p>Hi, I am getting a white screen when attempting to activate the module.</p>
<p>when I check the dblogs I receive</p>
<p>Recoverable fatal error: Argument 1 passed to Drupal\email_verify\Form\EmailVerifyAdminForm::__construct() must be an instance of Drupal\email_verify\EmailVerifyManagerInterface, instance of Drupal\email_verify\EmailVerifyManager given, called in /home/client/public_html/modules/email_verify/src/Form/EmailVerifyAdminForm.php on line 44 and defined in Drupal\email_verify\Form\EmailVerifyAdminForm-&gt;__construct() (line 34 of /home/client/public_html/modules/email_verify/src/Form/EmailVerifyAdminForm.php) #0 /home/client/public_html/core/includes/bootstrap.inc(552): _drupal_error_handler_real(4096, 'Argument 1 pass...', '/home/client/...', 34, Array) #1 /home/client/public_html/modules/email_verify/src/Form/EmailVerifyAdminForm.php(34): _drupal_error_handler(4096, 'Argument 1 pass...', '/home/client/...', 34, Array) #2 /home/client/public_html/modules/email_verify/src/Form/EmailVerifyAdminForm.php(44): Drupal\email_verify\Form\EmailVerifyAdminForm-&gt;__construct(Object(Drupal\email_verify\EmailVerifyManager)) #3 /home/client/public_html/core/lib/Drupal/Core/DependencyInjection/ClassResolver.php(28): Drupal\email_verify\Form\EmailVerifyAdminForm::create(Object(Drupal\Core\DependencyInjection\Container)) #4 /home/client/public_html/core/lib/Drupal/Core/Controller/HtmlFormController.php(47): Drupal\Core\DependencyInjection\ClassResolver-&gt;getInstanceFromDefinition('\\Drupal\\email_v...') #5 /home/client/public_html/core/lib/Drupal/Core/Controller/FormController.php(59): Drupal\Core\Controller\HtmlFormController-&gt;getFormObject(Object(Drupal\Core\Routing\RouteMatch), '\\Drupal\\email_v...') #6 [internal function]: Drupal\Core\Controller\FormController-&gt;getContentResult(Object(Symfony\Component\HttpFoundation\Request), Object(Drupal\Core\Routing\RouteMatch)) #7 /home/client/public_html/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(123): call_user_func_array(Array, Array) #8 /home/client/public_html/core/lib/Drupal/Core/Render/Renderer.php(574): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber-&gt;Drupal\Core\EventSubscriber\{closure}() #9 /home/client/public_html/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(124): Drupal\Core\Render\Renderer-&gt;executeInRenderContext(Object(Drupal\Core\Render\RenderContext), Object(Closure)) #10 /home/client/public_html/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(97): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber-&gt;wrapControllerExecutionInRenderContext(Array, Array) #11 [internal function]: Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber-&gt;Drupal\Core\EventSubscriber\{closure}() #12 /home/client/public_html/vendor/symfony/http-kernel/HttpKernel.php(144): call_user_func_array(Object(Closure), Array) #13 /home/client/public_html/vendor/symfony/http-kernel/HttpKernel.php(64): Symfony\Component\HttpKernel\HttpKernel-&gt;handleRaw(Object(Symfony\Component\HttpFoundation\Request), 1) #14 /home/client/public_html/core/lib/Drupal/Core/StackMiddleware/Session.php(57): Symfony\Component\HttpKernel\HttpKernel-&gt;handle(Object(Symfony\Component\HttpFoundation\Request), 1, true) #15 /home/client/public_html/core/lib/Drupal/Core/StackMiddleware/KernelPreHandle.php(47): Drupal\Core\StackMiddleware\Session-&gt;handle(Object(Symfony\Component\HttpFoundation\Request), 1, true) #16 /home/client/public_html/core/modules/page_cache/src/StackMiddleware/PageCache.php(99): Drupal\Core\StackMiddleware\KernelPreHandle-&gt;handle(Object(Symfony\Component\HttpFoundation\Request), 1, true) #17 /home/client/public_html/core/modules/page_cache/src/StackMiddleware/PageCache.php(78): Drupal\page_cache\StackMiddleware\PageCache-&gt;pass(Object(Symfony\Component\HttpFoundation\Request), 1, true) #18 /home/client/public_html/core/lib/Drupal/Core/StackMiddleware/ReverseProxyMiddleware.php(47): Drupal\page_cache\StackMiddleware\PageCache-&gt;handle(Object(Symfony\Component\HttpFoundation\Request), 1, true) #19 /home/client/public_html/core/lib/Drupal/Core/StackMiddleware/NegotiationMiddleware.php(50): Drupal\Core\StackMiddleware\ReverseProxyMiddleware-&gt;handle(Object(Symfony\Component\HttpFoundation\Request), 1, true) #20 /home/client/public_html/vendor/stack/builder/src/Stack/StackedHttpKernel.php(23): Drupal\Core\StackMiddleware\NegotiationMiddleware-&gt;handle(Object(Symfony\Component\HttpFoundation\Request), 1, true) #21 /home/client/public_html/core/lib/Drupal/Core/DrupalKernel.php(656): Stack\StackedHttpKernel-&gt;handle(Object(Symfony\Component\HttpFoundation\Request), 1, true) #22 /home/client/public_html/index.php(19): Drupal\Core\DrupalKernel-&gt;handle(Object(Symfony\Component\HttpFoundation\Request)) #23 {main}.</p>Wed, 26 Apr 2017 00:49:07 +0000amh5514https://www.drupal.org/project/email_verify/issues/2872833Notice: Undefined index: op in email_verify_edit_validate() (line 122 of /var/www/drupal7/web/sites/all/modules/contrib/email_verify/email_verify.module).https://www.drupal.org/project/email_verify/issues/2939279
<p>When trying to create a new account, I get this error.</p>
<p>Notice: Undefined index: op in email_verify_edit_validate() (line 122 of /var/www/drupal7/web/sites/all/modules/contrib/email_verify/email_verify.module).</p>Wed, 24 Jan 2018 20:07:26 +0000joncuphttps://www.drupal.org/project/email_verify/issues/2939279Reporting valid email hosts as invalidhttps://www.drupal.org/project/email_verify/issues/2930018
<p>The module sometimes reports valid email hosts as invalid email hosts. Customers are reporting that they can't register with their company email addresses. for example <a href="mailto:xxx@potterviolins.com" rel="nofollow">xxx@potterviolins.com</a></p>Mon, 11 Dec 2017 18:54:17 +0000khaldoon_masudhttps://www.drupal.org/project/email_verify/issues/2930018Port Email Verify to Drupal 8https://www.drupal.org/project/email_verify/issues/2693349
<p>I am porting this module as part of the CI&amp;T/Acquia Hackathon in Ningbo today</p>Thu, 24 Mar 2016 05:35:13 +0000adammalonehttps://www.drupal.org/project/email_verify/issues/2693349Update code based on updated Drupal Coding Standardshttps://www.drupal.org/project/email_verify/issues/2885172
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>The Drupal Coding Standards were recently updated, and the code should to be updated to the new standards, plus there were some old things that had not been updated previously.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Update the code to match the new standards.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<ol><li><del>Fix the issue</del></li>
<li><del>Create a patch</del></li>
<li>Review the patch</li>
<li><del>Commit the patch</del></li>
</ol><h3 id="summary-ui-changes">User interface changes</h3>
<p>None.</p>
<h3 id="summary-api-changes">API changes</h3>
<p>None.</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>None.</p>Sat, 10 Jun 2017 22:31:19 +0000oadaehhttps://www.drupal.org/project/email_verify/issues/2885172No check for .[ext]https://www.drupal.org/project/email_verify/issues/2881234
<p>Installed the module today and did two tests. First test was an email address with no "@", second was with no ".com" at the end. I did get an invalid email warning for no @, but the system accepted the email address with no .com extension.</p>
<p>No idea if it's related, but I did try to view the admin page to see if it was a setting of some type, but I am getting a white screen with that. Error message runs very long, but here's the beginning:<br /><code class="language-php">Recoverable fatal error: Argument 1 passed to Drupal\email_verify\Form\EmailVerifyAdminForm::__construct() must be an instance of Drupal\email_verify\EmailVerifyManagerInterface, instance of Drupal\email_verify\EmailVerifyManager given, called in /Users/Bcorrigan/sites/flowrite8/web/modules/contrib/email_verify/src/Form/EmailVerifyAdminForm.php on line 44 and defined in Drupal\email_verify\Form\EmailVerifyAdminForm-&gt;__construct() </code></p>Wed, 24 May 2017 17:42:16 +0000corgy99https://www.drupal.org/project/email_verify/issues/2881234Email validation issuehttps://www.drupal.org/project/email_verify/issues/2852975
<p>There is a problem with the email validation. The validation function sometimes reporting an error for the same email and sometimes not.<br />
I checked the dblog and I am seeing multiple log messages reported with one email validation. logs are showing validations for different email addresses.</p>
<p>Could not verify email address at host outlook.com: 550 SC-002 (BAY004-MC5F26) Unfortunately, messages from 54.86.2.165 weren't sent. Please contact your Internet service provider since part of their network is on our block list. You can also refer your provider to <a href="http://mail.live.com/mail/troubleshooting.aspx#errors" rel="nofollow">http://mail.live.com/mail/troubleshooting.aspx#errors</a>.</p>
<p>Could not verify email address at host live.com: 550 SC-002 (BLU004-MC1F28) Unfortunately, messages from 54.86.2.165 weren't sent. Please contact your Internet service provider since part of their network is on our block list. You can also refer your provider to <a href="http://mail.live.com/mail/troubleshooting.aspx#errors" rel="nofollow">http://mail.live.com/mail/troubleshooting.aspx#errors</a>. </p>
<p>Could not verify email address at host hotmail.com: 550 SC-002 (COL004-MC5F7) Unfortunately, messages from 54.86.2.165 weren't sent. Please contact your Internet service provider since part of their network is on our block list. You can also refer your provider to <a href="http://mail.live.com/mail/troubleshooting.aspx#errors" rel="nofollow">http://mail.live.com/mail/troubleshooting.aspx#errors</a>. </p>
<p>Could not verify email address at host mail.com: 554-mail.com (mxgmxus001) Nemesis ESMTP Service not available </p>
<p>Rejected email address: <a href="mailto:example@gmail.com" rel="nofollow">example@gmail.com</a>. Reason: 552-5.2.2 The email account that you tried to reach is over quota. Please direct </p>Wed, 15 Feb 2017 19:33:02 +0000khaldoon_masudhttps://www.drupal.org/project/email_verify/issues/2852975Backdrop porthttps://www.drupal.org/project/email_verify/issues/2417999
<p>As useful as this module is for Drupal, I suspect it will be equally useful for Backdrop.</p>
<p>I am willing to port this module to Backdrop and maintain or co-maintain it, once it is ported.</p>
<p>If any of the other maintainers are interested in porting the 7.x-3.x version of this module to Backdrop and/or maintaining or co-maintaining it afterward, please let me know.</p>
<p>There are a number of open bug reports and feature requests that I will take care of first, but once they are handled, I will start the process of creating a stable release for this module and then begin porting it to Backdrop.</p>Sun, 01 Feb 2015 02:24:37 +0000oadaehhttps://www.drupal.org/project/email_verify/issues/2417999Add another verification method - sending a real test e-mailhttps://www.drupal.org/project/email_verify/issues/2794945
<p>It would be helpful an another email address checking method (which could be enabled or disabled): send a mail to the receipent.<br />
There is an option to asking the recipient server that "will this address accept mail?". This test actually don't send a message just checking the address but because of it some servers are throws to blacklist the IP address from where the request sent. (read more e.g here: <a href="https://www.drupal.org/node/2585741#comment-11441083" rel="nofollow">https://www.drupal.org/node/2585741#comment-11441083</a>)</p>
<p>In our use-case it would be acceptable if the recipient got an email (which could be customizable on the module's settings page.) e.g. with something similar content: "You got this email because we've to verify that your address is exists. No action required. You can delete this email."<br />
Module could try to send this email and based on the recipient's server answer can decide that is the address existing or not.</p>Sun, 04 Sep 2016 17:23:13 +0000kepesvhttps://www.drupal.org/project/email_verify/issues/2794945Add an option to exclude email (whiltelist) domainshttps://www.drupal.org/project/email_verify/issues/2852690
<p>I can't create accounts or update accounts with my domain's email address, cause this module it reporting my domain's emails as bad emails.<br />
Could you add a domain exclude option? So I can ignore the email validation for specific domains. Thanks</p>Tue, 14 Feb 2017 21:55:14 +0000khaldoon_masudhttps://www.drupal.org/project/email_verify/issues/2852690Detect and fix existing bad emailshttps://www.drupal.org/project/email_verify/issues/2847215
<p>What if this module is enabled after so many bad email addresses have been stored.<br />
There should be an option or submodule to detect bad emails at login time and force the user to put a valid email address before any other activity. </p>Fri, 27 Jan 2017 00:46:02 +0000khaldoon_masudhttps://www.drupal.org/project/email_verify/issues/2847215Remove @file tag docblock from all the .php files. &amp; $this-&gt;t() should be used instead of t() for Drupal 8 versionhttps://www.drupal.org/project/email_verify/issues/2846607
<p>As per coding standard documentation at '<a href="https://www.drupal.org/coding-standards/docs" rel="nofollow">https://www.drupal.org/coding-standards/docs</a>', @file tag docblock should not be there in the files that contain a namespaced class/interface/trait, whose file name is the class name with a .php extension.</p>Wed, 25 Jan 2017 11:41:28 +0000nehakhadkehttps://www.drupal.org/project/email_verify/issues/2846607Keep getting not a valid email host!!https://www.drupal.org/project/email_verify/issues/2758467
<p>I am using it with webform. Few times it worked but then started ".... Not a valid email host" no matter what host I chose! what could be issue please?</p>Thu, 30 Jun 2016 10:46:42 +0000tapashhttps://www.drupal.org/project/email_verify/issues/2758467server IP blacklistedhttps://www.drupal.org/project/email_verify/issues/2585741
<p>I have been getting these watchdog errors:</p>
<blockquote><p>Could not verify email address at host outlook.com.: 550 SC-001 (BAY004-MC4F12) Unfortunately, messages from ***.***.**.*** weren't sent. Please contact your Internet service provider since part of their network is on our block list. You can also refer your provider to <a href="http://mail.live.com/mail/troubleshooting.aspx#errors" rel="nofollow">http://mail.live.com/mail/troubleshooting.aspx#errors</a>.</p></blockquote>
<p>I am no email expert and am not sure if this problem is caused by this module or not.</p>
<p>Is there an option to just check the DNS of the host and turn off the attempted sending of the check email?</p>
<p>What are the implication of sending the test email? Could it potentially get the server blacklisted?</p>Sat, 10 Oct 2015 01:53:00 +00002phahttps://www.drupal.org/project/email_verify/issues/2585741PDO error on database with prefixhttps://www.drupal.org/project/email_verify/issues/2771091
<p>Module doesn't work with prefixed tables.</p>
<blockquote><p>PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'rcgkh_site.users' doesn't exist: SELECT COUNT(DISTINCT uid) FROM users; Array ( ) в функции email_verify_user_check_form() (строка 66 в файле /usr/local/www/rcgkh/sites/all/modules/email_verify/email_verify.check.inc).</p></blockquote>
<p>From file:</p>
<pre class="codeblock"><code class="language-php"> $all_user_count = db_query("SELECT COUNT(DISTINCT uid) FROM users")-&gt;fetchField();
$active_user_count = db_query("SELECT COUNT(DISTINCT uid) FROM users WHERE status = 1")-&gt;fetchField();
</code></pre>Fri, 22 Jul 2016 08:58:20 +0000Razunterhttps://www.drupal.org/project/email_verify/issues/2771091Integrate with User Restrictions modulehttps://www.drupal.org/project/email_verify/issues/2751717
<p>Thanks for this module. It came at a time where my site was under heavy manually opened spam accounts using fake emails (where Honeypot was useless).</p>
<p>A suggestion, if I may... I think it woud be cool if Email Verify was blended with <a href="https://www.drupal.org/project/user_restrictions" rel="nofollow">User Restrictions</a> (one "complete" module; 2 maintainers cutting the work load in half).</p>
<p>Thanks again.</p>
<p>NG</p>Sun, 19 Jun 2016 12:10:41 +0000Northern_Girlhttps://www.drupal.org/project/email_verify/issues/2751717Integration with other modules (especially webform and simplenews)https://www.drupal.org/project/email_verify/issues/898726
<p>How would I use this module with my Webforms, to verify a visitor's email is valid?</p>
<p>I have a couple contact webforms (quick contact and full contact) on many of my sites. I'd *love* to not need to use a CAPTCHA. Both of these forms require an email address from the visitor. Is there a way to utilize your email address checking together with the Webform to prevent spammers using my Contact forms (or other Webforms)?</p>Tue, 31 Aug 2010 19:11:26 +0000gavinengelhttps://www.drupal.org/project/email_verify/issues/898726Added option to validate all Email module form elementshttps://www.drupal.org/project/email_verify/issues/2549165
<p>Hi, I've attached a patch to add an option to add email verification to all Email module elements (form API field of '#type' =&gt; 'email_textfield'), via a field widget alter.</p>Tue, 11 Aug 2015 04:02:12 +0000bgilhomehttps://www.drupal.org/project/email_verify/issues/2549165Module does not show tab for validating existing usershttps://www.drupal.org/project/email_verify/issues/2561163
<p>Perhaps this is a question not a feature request. After reading all the issues and browsing the documentation and testing the module, it doesn't seem to check existing emails when installed on an existing site.</p>
<p>Second question/request is for this module to validate on bulk user &amp; email import.</p>
<p>Can email verify do either of these?</p>
<p>I don't want to use 3rd parties tools via the other modules which might harvest my email list.</p>
<p>Thanks for coding this module.</p>Tue, 01 Sep 2015 15:21:29 +0000sajoshhttps://www.drupal.org/project/email_verify/issues/2561163Provide a way for an admin to specify which tests to runhttps://www.drupal.org/project/email_verify/issues/2827654
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>Triggered by <span class="project-issue-issue-link project-issue-status-info project-issue-status-7"><a href="/project/email_verify/issues/2585741" title="Status: Closed (fixed)">#2585741: server IP blacklisted</a></span> the idea was suggested that some of the various tests that are done to verify the email address could be disabled.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Create a mechanism where a system admin can choose which tests to execute when checking the email addresses.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<ol><li>Fix the issue</li>
<li>Create a patch</li>
<li>Review the patch</li>
<li>Commit the patch</li>
</ol><h3 id="summary-ui-changes">User interface changes</h3>
<p>This will need some admin UI changes.</p>
<h3 id="summary-api-changes">API changes</h3>
<p>TBD.</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>TBD.</p>Tue, 15 Nov 2016 02:41:48 +0000oadaehhttps://www.drupal.org/project/email_verify/issues/2827654Provide a mechanism where an admin can force a system capability checkhttps://www.drupal.org/project/email_verify/issues/2670050
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>Once a system capability check has been done, there is no way to initiate another test without uninstalling and re-installing the module.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Create a mechanism where a system admin can force another system capability check.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<ol><li>Fix the issue</li>
<li>Create a patch</li>
<li>Review the patch</li>
<li>Commit the patch</li>
</ol><h3 id="summary-ui-changes">User interface changes</h3>
<p>This will need some admin UI changes.</p>
<h3 id="summary-api-changes">API changes</h3>
<p>None.</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>None.</p>Tue, 16 Feb 2016 21:32:57 +0000oadaehhttps://www.drupal.org/project/email_verify/issues/2670050550 5.5.1 Protocol errorhttps://www.drupal.org/project/email_verify/issues/2775351
<p>I am getting the above message from some mailserver (posteo.org) in response to the validation test.</p>
<p>According to <a href="https://www.roessner-network-solutions.com/mail.html" rel="nofollow">https://www.roessner-network-solutions.com/mail.html</a></p>
<p>they must think that the request is somehow invalid. Anybody got an idea?</p>Fri, 29 Jul 2016 11:55:40 +0000killes@www.drop.orghttps://www.drupal.org/project/email_verify/issues/2775351Invalid string comparisonhttps://www.drupal.org/project/email_verify/issues/2744195
<p>In the function email_verify_get_form_fields is a typo</p>
<pre class="codeblock"><code class="language-php"> if (!empty($form) &amp;&amp; !empty($field) &amp;&amp; $form = $form_id) {
</code></pre><p>
which should be </p>
<pre class="codeblock"><code class="language-php"> if (!empty($form) &amp;&amp; !empty($field) &amp;&amp; $form == $form_id) {
</code></pre><p>
Otherwise that function will return something for all the forms and the email check will be triggered for all the forms and in case you are on a dev machine with no valid emails some forms won't validate and ....</p>Tue, 07 Jun 2016 15:12:11 +0000killes@www.drop.orghttps://www.drupal.org/project/email_verify/issues/2744195Typo on Email Verify project page and in READMEhttps://www.drupal.org/project/email_verify/issues/2742999
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>"When in doub, we try to play it safe and rather accept some invalid addresses than to refuse valid ones." has typo on project page:</p>
<p>doub =&gt; doubt</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Fix typo. :)</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<p>Fix typo. :)</p>
<h3 id="summary-ui-changes">User interface changes</h3>
<p>n/a</p>
<h3 id="summary-api-changes">API changes</h3>
<p>na/</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>n/a</p>Mon, 06 Jun 2016 03:50:31 +0000Kristen Polhttps://www.drupal.org/project/email_verify/issues/2742999Not all forms use the same element for validationhttps://www.drupal.org/project/email_verify/issues/2719507
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>Some forms do not use the $form['#validate'] element, but the $form['submit']['#validate'] element, for form validation.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Add the $form['submit']['#validate'] element as an additional place to tack on the validation for this module.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<ol><li><del>Fix the issue</del></li>
<li><del>Create a patch</del></li>
<li><del>Review the patch</del></li>
<li><del>Commit the patch</del></li>
</ol><h3 id="summary-ui-changes">User interface changes</h3>
<p>None.</p>
<h3 id="summary-api-changes">API changes</h3>
<p>None.</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>None.</p>Thu, 05 May 2016 14:10:18 +0000oadaehhttps://www.drupal.org/project/email_verify/issues/2719507[meta] Create a 7.x-2.0 releasehttps://www.drupal.org/project/email_verify/issues/2706461
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>This is to keep track on which issues are deemed important to complete before considering this branch ready for a .0 release.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>These are the things that should be added before creating a .0 release for the 2.x branch:</p>
<ul><li><span class="project-issue-issue-link project-issue-status-info project-issue-status-1"><a href="/project/email_verify/issues/2671926" title="Status: Active">#2671926: Update documentation</a></span></li>
<li><span class="project-issue-issue-link project-issue-status-info project-issue-status-1"><a href="/project/email_verify/issues/2669088" title="Status: Active">#2669088: Create a "strict" mode</a></span></li>
<li><span class="project-issue-issue-link project-issue-status-info project-issue-status-1"><a href="/project/email_verify/issues/2670050" title="Status: Active">#2670050: Provide a mechanism where an admin can force a system capability check</a></span></li>
<li><span class="project-issue-issue-link project-issue-status-info project-issue-status-7"><a href="/project/email_verify/issues/2585741" title="Status: Closed (fixed)">#2585741: server IP blacklisted</a></span> (provide a mechanism for separating domain from user checks and allow the admin to choose which to perform)</li>
<li><span class="project-issue-issue-link project-issue-status-info project-issue-status-7"><a href="/project/email_verify/issues/2719507" title="Status: Closed (fixed)">#2719507: Not all forms use the same element for validation</a></span></li>
</ul>Thu, 14 Apr 2016 15:19:48 +0000oadaehhttps://www.drupal.org/project/email_verify/issues/2706461Fix tests of return valueshttps://www.drupal.org/project/email_verify/issues/2704229
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>The code in the email_verify_verify_address() function does not correctly check the return results from email_verify_check(), as was introduced in the patch included with this comment: <span class="project-issue-issue-link project-issue-status-info project-issue-status-7"><a href="/comment/10907654#comment-10907654" title="Status: Closed (fixed)">#2493515-8: Add debugging logging</a></span>.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Add the omitted code changes from the original patch.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<ol><li><del>Fix the issue</del></li>
<li><del>Create a patch</del></li>
<li><del>Review the patch</del></li>
<li><del>Commit the patch</del></li>
</ol><h3 id="summary-ui-changes">User interface changes</h3>
<p>None.</p>
<h3 id="summary-api-changes">API changes</h3>
<p>None.</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>None.</p>Mon, 11 Apr 2016 20:06:57 +0000oadaehhttps://www.drupal.org/project/email_verify/issues/2704229Greylist + Multiline responses + Timeoutshttps://www.drupal.org/project/email_verify/issues/2102323
<p>After a great deal of work with this module, I ended up doing several tuning:</p>
<p>- Fixed a FALSE negative in some greylist responses from SMTP servers.</p>
<p>- Improved overall SMTP communication to accept multi-line responses and read response code.</p>
<p>- Implemented socket timeout for unresponsive servers.</p>
<p>- Improved output messages for log that include complete communication with server and e-mail addresses.</p>
<p>- On high traffic sites, bots will use once and again the same e-mail address, you server's IP will eventually get blocked. Added a caching layer to mail verification.</p>Tue, 01 Oct 2013 18:15:40 +0000david_garciahttps://www.drupal.org/project/email_verify/issues/2102323Read Documentation Link does not workhttps://www.drupal.org/project/email_verify/issues/2704775
<p>Today I tried to click the "Read Documentation" link on the project page. It goes to cvs.drupal.org. This link fails, apparently the server either no longer exists or maybe it's temporarily offline.</p>Tue, 12 Apr 2016 15:06:51 +0000garyebickfordhttps://www.drupal.org/project/email_verify/issues/2704775Support for Commerce&#039;s Checkout module&#039;s formhttps://www.drupal.org/project/email_verify/issues/2403949
<p>Hi,</p>
<p>I'm looking for support on Commerce's Checkout form, when anonymous users enter their e-mail address and intend to receive order confirmation etc on that address (screenshot with example attached).</p>
<p>I've tried this piece of code in email_verify.module, but that did not result in a working solution yet.</p>
<pre class="codeblock"><code class="language-php">/**
* Implements hook_form_FORM_ID_alter().
*
* For the Commerce's Checkout module's form.
* https://www.drupal.org/project/commerce
*/
function email_verify_form_commerce_checkout_form_checkout_alter(&amp;$form, &amp;$form_state, $form_id) {
$form['#validate'][] = 'email_verify_edit_validate';
}</code></pre><p>
Thanks!</p>
<p>Léon</p>Thu, 08 Jan 2015 13:16:21 +0000elsteff1385https://www.drupal.org/project/email_verify/issues/2403949Cache bad e-amilshttps://www.drupal.org/project/email_verify/issues/2241483
<p>My situation:</p>
<p>- High volume sites, using HONEYPOT + HIDDEN CAPTCHA + EMAIL_VERIFY leads to perfect protection against bots.<br />
- Some bots are able to get through HONEYPOT + HIDDEN CAPTCHA, in those cases EMAIL_VERIFY is "the last stand".<br />
- These bots are using similar e-mail address patterns, but constantly changing source IP.</p>
<p>Results:</p>
<p>- The e-mails servers start throttling and/or blocking SMTP and/or greylisting connections from my server.</p>
<p>Solution:</p>
<p>- Cache e-mail verification results for address proven to be "bad"</p>Tue, 15 Apr 2014 14:08:41 +0000david_garciahttps://www.drupal.org/project/email_verify/issues/2241483Allow for more flexible form verification https://www.drupal.org/project/email_verify/issues/2426859
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>There are other modules out there that provide forms for adding email addresses. However, it is impractical for this module to provide custom solutions for all the possible modules available.<br />
Also, it's entirely likely that a site might have custom forms and email address fields that people want checked.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Modify the admin form and the code to provide a generic way for specifying the form and email address field, such that the admin can specify any form they want to verify the email address on. This requires specifying both the form ID and the field ID the email address is in.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<ol><li><del>Fix the issue</del></li>
<li><del>Create a patch</del></li>
<li><del>Review the patch</del></li>
<li><del>Commit the patch</del></li>
</ol><h3 id="summary-ui-changes">User interface changes</h3>
<p>The admin UI will need to be modified to allow this.</p>
<h3 id="summary-api-changes">API changes</h3>
<p>To be determined.</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>To be determined.</p>Sun, 15 Feb 2015 18:08:34 +0000oadaehhttps://www.drupal.org/project/email_verify/issues/2426859User check form does not use offsethttps://www.drupal.org/project/email_verify/issues/2669358
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>When running through the user check process, the code does not correctly handle the offset field and will end up checking all users if anything is entered there.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Troubleshoot and fix it.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<ol><li><del>Fix the issue</del></li>
<li><del>Create a patch</del></li>
<li><del>Review the patch</del></li>
<li><del>Commit the patch</del></li>
</ol><h3 id="summary-ui-changes">User interface changes</h3>
<p>None.</p>
<h3 id="summary-api-changes">API changes</h3>
<p>None.</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>None.</p>Mon, 15 Feb 2016 23:59:52 +0000oadaehhttps://www.drupal.org/project/email_verify/issues/2669358Check activation correctlyhttps://www.drupal.org/project/email_verify/issues/2676830
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>There are a couple of places where module activation is checked without using the email_verify_activated() function.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Fix them.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<ol><li><del>Fix the issue</del></li>
<li><del>Create a patch</del></li>
<li><del>Review the patch</del></li>
<li><del>Commit the patch</del></li>
</ol><h3 id="summary-ui-changes">User interface changes</h3>
<p>None.</p>
<h3 id="summary-api-changes">API changes</h3>
<p>None.</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>None.</p>Sat, 27 Feb 2016 00:21:51 +0000oadaehhttps://www.drupal.org/project/email_verify/issues/2676830Add debugging logginghttps://www.drupal.org/project/email_verify/issues/2493515
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>At times, it is difficult to figure out why the module appears to not be working, and/or why a particular address is or is not validating.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Add an option for adding debugging messages to the log and/or the current page, so that users of this module can figure out if things are working correctly or not.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<ol><li><del>Fix the issue</del></li>
<li><del>Create a patch</del></li>
<li><del>Review the patch</del></li>
<li><del>Commit the patch</del></li>
</ol><h3 id="summary-ui-changes">User interface changes</h3>
<p>There will at least be a modification to the admin UI for en/disabling the functionality, and there will be updates to the UI for the reporting.</p>
<h3 id="summary-api-changes">API changes</h3>
<p>None.</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>None.</p>Fri, 22 May 2015 14:10:56 +0000oadaehhttps://www.drupal.org/project/email_verify/issues/2493515Add message to indicate the user check was completedhttps://www.drupal.org/project/email_verify/issues/2669258
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>There is no indication on the user check page when no addresses failed the check or when the check was completed.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Add some sort of message to indicate that the check was completed, and if no failed addresses were found.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<ol><li><del>Fix the issue</del></li>
<li><del>Create a patch</del></li>
<li><del>Review the patch</del></li>
<li><del>Commit the patch</del></li>
</ol><h3 id="summary-ui-changes">User interface changes</h3>
<p>None.</p>
<h3 id="summary-api-changes">API changes</h3>
<p>None.</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>None.</p>Mon, 15 Feb 2016 20:12:29 +0000oadaehhttps://www.drupal.org/project/email_verify/issues/2669258Add watchdog entry when module is activated and inactivatedhttps://www.drupal.org/project/email_verify/issues/2669256
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>There is no indication in the logs when the module is activated or inactivated.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Add watchdog entry when the module is activated and inactivated.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<ol><li><del>Fix the issue</del></li>
<li><del>Create a patch</del></li>
<li><del>Review the patch</del></li>
<li><del>Commit the patch</del></li>
</ol><h3 id="summary-ui-changes">User interface changes</h3>
<p>None.</p>
<h3 id="summary-api-changes">API changes</h3>
<p>None.</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>None.</p>Mon, 15 Feb 2016 20:11:35 +0000oadaehhttps://www.drupal.org/project/email_verify/issues/2669256Rename email_verify.inc.php to email_verify.inchttps://www.drupal.org/project/email_verify/issues/2669082
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>The name of the email_verify.inc.php file is not consistent with practices for modules and include files on d.o, nor within this module itself.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Rename email_verify.inc.php to email_verify.inc, so that it is in-line with normal Drupal practices.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<ol><li><del>Fix the issue</del></li>
<li><del>Create a patch</del></li>
<li><del>Review the patch</del></li>
<li><del>Commit the patch</del></li>
</ol><h3 id="summary-ui-changes">User interface changes</h3>
<p>None.</p>
<h3 id="summary-api-changes">API changes</h3>
<p>None.</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>None.</p>Mon, 15 Feb 2016 15:45:29 +0000oadaehhttps://www.drupal.org/project/email_verify/issues/2669082can&#039;t open the module page one ime installedhttps://www.drupal.org/project/email_verify/issues/477032
<p>I have nstalled this module using plugin manager, as for other dozens of modules without problems.<br />
But for this module when I go on admin/user/user/email_verify the page continue loading without opening.<br />
What I can do to use this module?<br />
I'm using drupal 6.12 on <a href="http://www.forniture-alberghiere.net" rel="nofollow">www.forniture-alberghiere.net</a> .</p>Sat, 30 May 2009 00:31:59 +0000matteoraggihttps://www.drupal.org/project/email_verify/issues/477032fsockopen functionhttps://www.drupal.org/project/email_verify/issues/2049147
<p>Hi there,</p>
<p>I have contacted my hosting services about the "Email verify has tried contacting the mail host but did not receive a reply. Check with your hosting provider that the function fsockopen() is properly configured on your server, and that port 25 is open. The module has been disabled." message and that's what they tell me.</p>
<blockquote><p>This function is restricted. You must connect to 'localhost' for SMTP and use authenticated e-mail transport. This will not be relaxed as it is an anti-spam measure.</p>
<p>The module is poorly coded if there is no way to use authenticated SMTP to localhost. You may NOT make unsolicited SMTP connections from ANY PHP script on our services. The only way to use e-mail is using authenticated SMTP provided by your account.</p></blockquote>
<p>Any suggestions other that the patch at <span class="project-issue-issue-link project-issue-status-info project-issue-status-5"><a href="/project/email_verify/issues/431376" title="Status: Closed (won't fix)">#431376: Running with shared hosting security</a></span>?</p>
<p>As no checking the mailbox name makes this module pretty useless (no offence) as most spammers will use working domains like hotmail, gmail, etc etc ... and addresses syntax is already covered by core.</p>
<p>Thanks</p>Wed, 24 Jul 2013 09:38:01 +0000manolokahttps://www.drupal.org/project/email_verify/issues/2049147Blacklist Featurehttps://www.drupal.org/project/email_verify/issues/1063568
<p>I'm interested to the opportunity to provide a blacklist feature for this module. For this reason I wrote the code necessary to allow site administrators to input different domain inside a blacklist form. The email address with these domain will be automatically rejected during user registration. A regexpr avoid to insert faked domain inside blacklist form. I hope it's interesting. Regards.</p>Wed, 16 Feb 2011 16:51:08 +0000abertullahttps://www.drupal.org/project/email_verify/issues/1063568Valid emails do not passhttps://www.drupal.org/project/email_verify/issues/1909918
<p>Sometimes, valid emails are rejected, preventing people to register.<br />
These addresses are actually rejected too by online checking services like <a href="http://tools.email-checker.com/" rel="nofollow">http://tools.email-checker.com/</a><br />
This is certainly due to the mail server configuration that does not like to be checked and sends back weird insults that makes this module mad.<br />
Nethertheless, this should not block the registation process as it is said in the module page.</p>
<p>The error I get is <a href="mailto:yy@xx.com" rel="nofollow">yy@xx.com</a> is invalid, please contact us for clarification.<br />
This seems to comes from the last check </p>
<pre class="codeblock"><code class="language-php">if (!ereg ("^250", $to)) {
watchdog('email_verify', "Rejected email address: $mail. Reason: $to");
return t('%mail is invalid, please contact us for clarification.', array('%mail' =&gt; "$mail"));
}</code></pre><p>What is this test about, why is it blocking without further explanation?</p>
<p>Thanks</p>Wed, 06 Feb 2013 18:28:38 +0000jvieillehttps://www.drupal.org/project/email_verify/issues/1909918Module testing wrong smtp server?https://www.drupal.org/project/email_verify/issues/737978
<p>When trying to enable the module, I got the error informing me that fsockopen was not working. I opened up an SSH shell and tested it with a telnet command (<code class="language-php">telnet mail.mydomain.com 25</code>) and was able to connect fine, so it would appear that the error message was in fact in error.</p>
<p>I went in and I changed these two lines of code:</p>
<p>email_verify.install, line 41<br />
Changed this:<br /><code class="language-php">$connect = @fsockopen($smtp, 25, $errno, $errstr, 15);</code><br />
To this:<br /><code class="language-php">$connect = @fsockopen("mail.mydomain.com", 25, $errno, $errstr, 15);</code></p>
<p>email_verify.inc.php<br />
Changed this:<br /><code class="language-php">$connect = @fsockopen($smtp, 25, $errno, $errstr, 15);</code><br />
To this:<br /><code class="language-php">$connect = @fsockopen("mail.mydomain.com", 25, $errno, $errstr, 15);</code></p>
<p>The module seems to work fine this way. It gives me errors for domains that don't exist, and lets through domains that do exist.</p>
<p>Does anybody see any problems with this? Am I missing something here, or is my problem solved? </p>Wed, 10 Mar 2010 07:55:18 +0000Jaypanhttps://www.drupal.org/project/email_verify/issues/737978When i first put &quot;Email verify&quot; module on I get this. --- When I registrar I get this. https://www.drupal.org/project/email_verify/issues/1172212
<p><b>When i first put "Email verify" module on I get this.</b></p>
<p>Warning: MySQL server has gone away query: INSERT INTO watchdog (uid, type, message, variables, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', '%message in %file on line %line.', 'a:4:{s:6:\"%error\";s:12:\"user warning\";s:8:\"%message\";s:651:\"MySQL server has gone away\nquery: INSERT INTO watchdog\n (uid, type, message, variables, severity, link, location, referer, hostname, timestamp)\n VALUES\n (1, 'email_verify', 'Email verify has tried contacting the mail host but did not receive a reply. Check with your hosting provider that the function fsockopen() is properly configured on your server, and that port 25 is open. The module has been disabled.', 'i:3;', 5, '', '<a href="http://aphasiatoolbox.com/?q=admin/build/modules/list/confirm'" rel="nofollow">http://aphasiatoolbox.com/?q=admin/build/modules/list/confirm'</a>, '<a href="http://aphasiatoolbox.com/?q=admin/build/modules'" rel="nofollow">http://aphasiatoolbox.com/?q=admin/build/modules'</a>, '[IP address] in /home/content/a/p/h/aphasia/html/includes/database.mysqli.inc on line 134</p>
<p><b>When I registrar I get this.</b> </p>
<p>Warning: MySQL server has gone away query: INSERT INTO watchdog (uid, type, message, variables, severity, link, location, referer, hostname, timestamp) VALUES (0, 'php', '%message in %file on line %line.', 'a:4:{s:6:\"%error\";s:12:\"user warning\";s:8:\"%message\";s:120:\"MySQL server has gone away\nquery: SELECT uid FROM users WHERE LOWER(mail) = LOWER('carolm') AND uid &lt;&gt; 0\";s:5:\"%file\";s:85:\"/home/content/a/p/h/aphasia/html/sites/all/modules/logintoboggan/logintoboggan.module\";s:5:\"%line\";i:1116;}', 3, '', '<a href="https://aphasiatoolbox.com/?q=user/register" rel="nofollow">https://aphasiatoolbox.com/?q=user/register</a>', '<a href="https://aphasiatoolbox.com/?q=user/register" rel="nofollow">https://aphasiatoolbox.com/?q=user/register</a>', '[IP address]', 1306655966) in /home/content/a/p/h/aphasia/html/includes/database.mysqli.inc on line 134</p>Sun, 29 May 2011 08:07:49 +0000earth1https://www.drupal.org/project/email_verify/issues/1172212valid E-Mail invalidhttps://www.drupal.org/project/email_verify/issues/604406
<p>On my Drupal 6.14 your modul works fine, except for one address: <a href="mailto:info@fahrschule-wunderlich.de" rel="nofollow">info@fahrschule-wunderlich.de</a><br />
I don't know why, but your moduls says it is invalid. But it isn't!</p>Wed, 14 Oct 2009 16:08:28 +0000fabskehttps://www.drupal.org/project/email_verify/issues/604406does not parse a multi-line 220 (after connection) correctlyhttps://www.drupal.org/project/email_verify/issues/762110
<p>Example: </p>
<p>Connect to (mailserver) via telnet at port 25, receive:</p>
<p>Trying 127.0.0.1...<br />
Connected to xxxx (x.x.x.x).<br />
Escape character is '^]'.<br />
220-mailserver ESMTP Exim 4.69 #1 Sun, 04 Apr 2010 22:52:51 -0500<br />
220-We do not authorize the use of this system to transport unsolicited,<br />
220 and/or bulk e-mail.</p>
<p>The current code uses fgets() a single time to get the 220 status indicating the server is ok.</p>
<p>The code then HELO, MAIL FROM, and RCPT TO each time using fgets() to retrieve the server's result.</p>
<p>The problem comes because the server has returned multiple lines of 220 and at least one of the tests following the HELO (in my case, the MAIL FROM) will return 220 instead of an expected OK code. The verification then bails (giving the user benefit-of-doubt)</p>
<p>Since fgets() returns only a single line of code, here is my workaround:</p>
<p> if (ereg("^220", $out = fgets($connect, 1024))) {<br />
// OK, we have a SMTP connection<br />
+ while ($out != ""):<br />
+ $out = fgets($connect, 1024);<br />
+ endwhile;<br />
break;</p>
<p>Probably not the cleanest code, but it's needed to work around a server that returns more than one 220 line....</p>
<p>I have verified that this is working by adding this at the end of my code:</p>
<p> // Everything OK<br />
+ watchdog('email_verify', "Everything OK with email address: $mail");<br />
return;</p>Mon, 05 Apr 2010 03:58:49 +0000mbeach1https://www.drupal.org/project/email_verify/issues/762110Add a compatibility with sharedemail modulehttps://www.drupal.org/project/email_verify/issues/860008
<p><a href="http://drupal.org/project/sharedemail" rel="nofollow">sharedemail: </a><cite>The shared email module overrides the 'user' module's validation that prevents the same email address being used by more than one user. Works for both registration and account updates. Displays a warning to the user that they are using a shared email.</cite></p>
<p>Really it adds a prefix 'sharedemail_' to $edit['mail'] on hook_user($op = 'validate') preventing the core from generating a warning. Later this module roll's back the user's mail to it's original value.</p>
<p>Of course this changed email doesn't pass email verification, so we can just check for this 'sharedemail_' prefix and remove it if needed.</p>Wed, 21 Jul 2010 02:16:15 +0000Victor Safronovhttps://www.drupal.org/project/email_verify/issues/860008Email Verify requires the server of a version of PHP 5.3 on Windows?https://www.drupal.org/project/email_verify/issues/508004
<p>when i tried to install it on my local machine, i got this message "Email Verify could not contact the mail host because the server is running on Windows with a version of PHP below 5.3"</p>Thu, 02 Jul 2009 08:55:37 +0000doriangrayhttps://www.drupal.org/project/email_verify/issues/508004Cannot enable modulehttps://www.drupal.org/project/email_verify/issues/763996
<p>When I enable the module, it comes back with the following message:<br />
Email verify has tried contacting the mail host but did not receive a reply. Check with your hosting provider that the function fsockopen() is properly configured on your server, and that port 25 is open. The module has been disabled.<br />
I am running Drupal on our onw LAMP server. What could be the issue?</p>Wed, 07 Apr 2010 00:19:47 +0000Alan.Guggenheimhttps://www.drupal.org/project/email_verify/issues/763996Rejected email address, Reason: 530 SMTP authentication is required.https://www.drupal.org/project/email_verify/issues/1669710
<p>Hi,<br />
When I am using my domain's email id (<a href="mailto:subhash@domain.in" rel="nofollow">subhash@domain.in</a>), I am getting this error message in db log<br />
"Rejected email address: <a href="mailto:subhash@domain.in" rel="nofollow">subhash@domain.in</a>. Reason: 530 SMTP authentication is required. "</p>
<p>For gmail and yahoo it is working fine. Is there any configuration setting I need to do ?</p>
<p>Thanks</p>Tue, 03 Jul 2012 12:46:35 +0000subu.purohithttps://www.drupal.org/project/email_verify/issues/1669710