Version: 1.00, by echamberlain
Developer Last Online: Mar 2017
Category: Miscellaneous Hacks -
Version: 3.6.5
Rating:
Released: 04-10-2007
Last Update: 04-10-2007
Installs: 265
Uses Plugins
No support by the author.
This mod checks that the user supplied e-mail address is a real address before allowing registration to continue.
Even though we use Verify Email address in Registration, I still get tired of cleaning up bad e-mail addresses.
This mod integrates with the user registration process and performs the following tasks:
Syntax checking (configurable) to make sure what was entered is an e-mail address.
Looks up the MX records for the e-mail address.
Cycles through the mail servers by connecting to each mail server and tries to verify that the e-mail address is a valid address. The cycling stops as soon as a mail server returns a valid or invalid user.
Installation
Install the attached xml product file. The product is active at installation and most sites should run fine with the default settings.
If you run the default configuration, e-mail addresses will be rejected when:
Syntax doesn't look like an e-mail address
MX record or A record does not exist for the e-mail domain
A mail server reports that the e-mail address is invalid
If you run the default configuration, e-mail address will pass when:
Syntax looks like an e-mail address
MX record or A record exists for the e-mail domain
All mail servers timeout or a mail server reports that the e-mail address is valid.
Configuration
This mod is managed from the vBulletin Options -> User Registration Options page. The following options are added to the page:
Validate Registration E-mail Addresses - Enter a regular expression to use when validating e-mail addresses. Leave the field blank to disable validation. The recommendation is to use the default value.
Treat E-mail Address As Valid If All Mail Hosts Timeout - If all the mail hosts timeout, should the e-mail address be treated as valid?
NOTE: Changing this to no will reject valid users when your hosting provider doesn't allow fsockopen calls or when the timeout value is too short. The SMTP RFC's allow for a connection request response wait time of up to minues, since this test is real-time with a waiting user, waiting minutes is impractical. Just because a host timesout doesn't mean the host is not there.
Mail Host Timeout Value (Seconds) - Length of time to wait when trying to open a session with a mail host.
NOTE: Don't set this value too large, if a domain has more than one MX record, the user will have to wait for each connection attempt.
Does This Host Support fsockopen? - A PHP fsockopen call is used to try and connect to the remote mail servers. Some systems may not support or block these calls. With the value set to Yes, the connection attempts will timeout. GoDaddy's Shared Hosting is an example of a hosting provider that blocks outbound connection attempts.
With this value set to no, the system will try to look up the MX records, but will not attempt to connect to each mail server.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
But then... I have similiar problem Mecho stated above. They can register, but no confirmation mail ever sent to Yahoo, Gmail or Hotmail. I had to disable it. Any hints? :erm:
This code does not work and WILL RETURN FALSE POSITIVES AS CODED.
The comparator code for a valid response with substr() is coded wrong and also checks the wrong response it appears. The defaults for the below init seem to guarantee a false positive. EDIT: I see the reason now for the false positive, but I don't like that idea. We need all or nothing. This is like a false sense of security as is. This can be great however and should be!
Sets this positive to start. I'm pretty sure that should be the opposite for sanity. In my testing and simple knowledge anyway.
It can work as far as I can tell with my own testing and modifications, so far. I tested it against my sever and yahoo with my fixes as working. But I don't want to get ahead of myself. There may be more pitfalls I missed in my simple debugging.
It can work as far as I can tell with my own testing and modifications, so far. I tested it against my sever and yahoo with my fixes as working. But I don't want to get ahead of myself. There may be more pitfalls I missed in my simple debugging.
If you get it working, could you advise and provide your version?
I'm trying to figure out improved ways to stop spammers who are registering with false email addresses and posting garbage.
Check E-mail Address Before Registration Details »»
About Developer
Visit Web Site
Uses Plugins 
No support by the author.
10-10-2007, 02:54 AM
