| 1 |
email_verify: Verifies thoroughly that email addresses are correctly entered
|
| 2 |
during registration and account edition.
|
| 3 |
|
| 4 |
Copyright: Daniel Bonniot <bonniot@users.sourceforge.net>
|
| 5 |
License: GNU GPL v2 or later
|
| 6 |
|
| 7 |
|
| 8 |
Description
|
| 9 |
-----------
|
| 10 |
This module provides advanced email address checking. The core of
|
| 11 |
Drupal, through the user module, only performs syntactical checking of
|
| 12 |
user-entered email addresses, both during registration and account
|
| 13 |
edition. This creates loads of problems when users incorrectly enter
|
| 14 |
their address. First, they don't get any email from the site. If it
|
| 15 |
happened during registration, they will not get their password. They
|
| 16 |
will either bug the site admin or give up on the site altogether,
|
| 17 |
both cases being a bad thing. Second, the site admin will get email
|
| 18 |
bounces, which soon gets annoying if you have a moderately busy site.
|
| 19 |
|
| 20 |
This module tries to solve this problem by checking that the address
|
| 21 |
really exists when it is entered by the user. First, it checks if the
|
| 22 |
domain/host part exists at all, and reports an error if it does not. I
|
| 23 |
found that this step alone catches between 1/2 and 2/3 of typos.
|
| 24 |
Second, it tries to validate the user name too, by sending a HELO/MAIL
|
| 25 |
FROM/RCPT TO chain of commands to the SMTP servers for the found
|
| 26 |
host. Some hosts will not reveal if the user name is valid ("catch-all
|
| 27 |
policy") while others might refuse the check for some reason (for
|
| 28 |
instance, some hosts refuse deliveries from IPs delivered to home
|
| 29 |
users by Internet access providers). When in doub, we try to play it
|
| 30 |
safe and rather accept some invalid addresses than to refuse valid
|
| 31 |
ones.
|
| 32 |
|
| 33 |
NOTES:
|
| 34 |
* Provide any feedback on the issue queue:
|
| 35 |
http://drupal.org/project/issues/email_verify
|
| 36 |
* Please send feedback to the author, both praise and constructive
|
| 37 |
criticism, even patches!
|
| 38 |
* If the module does not make the right decision about a certain
|
| 39 |
address, let me know so I can check it. If you can provide a detailed
|
| 40 |
SMTP conversation to illustrate what is happening _from_the_machine
|
| 41 |
hosting_your_site, that will be most helpful.
|
| 42 |
* See below for known issues and things that can be improved.
|
| 43 |
|
| 44 |
|
| 45 |
Installation
|
| 46 |
------------
|
| 47 |
This module requires no database changes.
|
| 48 |
|
| 49 |
Install like any other module: copy the whole email_verify directory
|
| 50 |
into the directory sites/all/modules/ or wherever you usually put contrib modules.
|
| 51 |
|
| 52 |
You then need to go to admin/build/modules and check the Enabled box for
|
| 53 |
email_verify, then save configuration. The module uses the hooks for
|
| 54 |
user account validation. Therefore, email checking is automatically
|
| 55 |
active from then on. Sit back, and enjoy getting ten times less of
|
| 56 |
those email bounces and see more people succeed in registering to your
|
| 57 |
site!
|
| 58 |
|
| 59 |
If you see 'warning: fsockopen(): ...' output on your pages, make sure
|
| 60 |
that you set 'Error reporting' on admin/settings/error-reporting to 'Write errors to
|
| 61 |
the log'. You will still see such errors in the log. They indicate
|
| 62 |
that an SMTP server did not respond (in which case the username was
|
| 63 |
supposed valid).
|
| 64 |
|
| 65 |
|
| 66 |
Things to do / Known problems
|
| 67 |
-----------------------------
|
| 68 |
See the module's issue queue:
|
| 69 |
http://drupal.org/project/issues/email_verify
|
| 70 |
|
| 71 |
|
| 72 |
Contact
|
| 73 |
-------
|
| 74 |
Feedback should be sent to bonniot@users.sourceforge.net
|
| 75 |
|
| 76 |
This module is used in production on my drupal site: http://objectiftarot.net
|
Parent Directory
| 
Revision Log
| 
Revision Graph