Skip to main content

New module: Email Validator

Today I published on drupal.org the module I was developing the last few days: Email Validator. I copy from there the description of the module:
Integrates Drupal with the Email Address Online Verification API. As it is said in the service's website, the validation process includes the following steps:
  • Syntax verification
  • DNS validation including MX record lookup
  • Disposable email address (DEA) detection
  • SMTP connection and availability checking
  • Temporary unavailability detection
  • Mailbox existence checking
  • Catch-All testing
  • Greylisting detection
In case the service is unavailable at the moment, this module may use Drupal's built-in valid_email_address() function, assume a valid email address or assume an invalid email address. The administrator of the website may change the action to use, using the configuration form of this module.

It was a nice challenge for me since it was the first time I played around with the Field API to make sure this module played well with the Email field widget. It was a fascinating procedure and is was awkward to find out that there was no hook_field_settings_form_alter() or equivalent to target the settings form of a specific field or field type. I had to use the common hook_form_FORM_ID_alter() (actually it's hook_form_field_ui_field_edit_form_alter() since the form is produced by the field_ui core module) and check the widget type from $form_state['build_info']['args'][0]['widget']['type'].

I also sent a message to Email Validator service in case they could provide an API call for getting the credits the account has before making a verification call. I think it would be a nice addition.

For any issues or feature request, please prefer the issue queue ;)

Comments

Popular posts from this blog

Drupal: Allow registrations through Invite or Referral modules only

The Invite module provides invitations from existing users to their contacts. The Referral module, in contrary, creates a special URL for each existing user, which can be found in each user's profile, and allows new user registration. Even though, these two modules seem to provide the same functionality, they don't (and they shouldn't). Invite module, provides a mechanism for a site administrator to limit new registrations to "Invitations only". Referral module doesn't provide any of this functionality. Some users have requested the Invite module and Referral module to join in one module. Until now, there isn't anything to that direction. Wouldn't it be great though if there was a solution to limit drupal registration to referral or invitation only? Copy the functions below to a refinvite.module file in your sites→all→modules→refinvite folder and enable the module. Then go to http://<your-address-here>/admin/user/settings and enable the new …

Configure drupal_http_request() on the fly

The drupal_http_request() function supports connections using a proxy. You can configure a global proxy to use for all drupal_http_request() callbacks from the settings.php file of your website/installation by filling the following lines with the proper information:For those of you preferring a UI, then HTTP proxy module is for you.But what if you only want to use a proxy in some cases; like a custom module? In that case you will need the following function(modify accordingly):Now all you have to do is Call <?php _MYMODULE_change_proxy(); ?>.Do your drupal_http_request() calls.Call <?php _MYMODULE_change_proxy(TRUE); ?> to reset your previous settings.

Drupal: Status report problem: HTTP request status fails

Some of you may have encountered this problem in some cases. In "Status Report" page, accidentally appears the error below:

HTTP request status   FailsYour system or network configuration does not allow Drupal to access web pages, resulting in reduced functionality. This could be due to your webserver configuration or PHP settings, and should be resolved in order to download information about available updates, fetch aggregator feeds, sign in via OpenID, or use other network-dependent services.
What I did, was to recheck that my webserver had access to internet. Of course it had! The problem exists mostly when there is no information to resolve the domain name used with the local ip address of the webserver. This means that an error occurs in the entries of the DNS server.

In cases where DNS server is not existant(ex. local testing environment) all you have to do is inform the /etc/hosts file. For example if you use the domain http://www.example.local/ and your local ip addr…