Is it possible to have a valid (Drupal.org) email address to check whether the own server is able to use email verify.
Reason: the provider prohibited fsockopen one day. So if the check to a valid (Drupal.org) email address would fail, the email verify could be detect that the server is not ready to use email verify.

maybe drupal.org could activate an email like emailverify@drupal.org for that reason.

Comments

etron770’s picture

I found the reason for the issue:
The provider does not permit @fsockopen($smtp, 25, $errno, $errstr, 15);
And all addresses will be rejected with the present code.

so maybe it is a bug report?

david_garcia’s picture

This verification is already done during the module's installation (see email_verify_enable in email_verify.install).

Maybe it could be improved, but this must be done carefully I am thinking of:

- Keep track of an internal variable, something such as "fsockopen_25_working", after install set it to true.
- Implement a cache based mechanism on _email_verify_check so that when a certain amount of failed connections are detected, this variable is set to false, or maybe trigger an additional check against drupal.org (the same performed during install) before setting it to false. Log this events to watchdog.
- When this variable is false, no e-mail checks will be performed so the module will be virtually disabled.
- We need to add some UI for admins (possibly in the module's administration page) so that they can see what this "fsockopen..." variable value has, and have the possibility of manually rechecking if fsockopen is working on port 25.
- Perform check on System Status Page so administrators can see if this variable is TRUE, and if not give a link to the admin page where they can manually trigger a fsockopen verification.

oadaeh’s picture

Status: Active » Closed (works as designed)

As the OP's original issue is works as designed, I'm closing this. David, if you want to pursue the feature additions, please create a new feature request for them.