| Product Summary |
 |
|
|
EmailResolver |
|
| Guide Rating - |
 |
|
| Pros |
• Verifies addresses reliably
• Flexibly uses various validation methods
• Easy to use
|
|
| Cons |
• Requires support for OCX components
|
|
|
The Bottom Line -
Verify email address reliably and flexibly from any application that can contain OCX components.
Manufacturer's Page
|
|
|
| Product Description |
|
| • |
Validate email addresses from any application (including ASP) that can use OCX components. |
| • |
Checks syntactic correctness, looks up mail servers, tries to verify email addresses at the server or send a dummy message. |
| • |
Windows 9x/ME/NT/2000/XP |
| |
|
|
| Guide Review |
|
Don't Use Email Addresses UnEmailResolvered
An email address is only as good as its validity is. Checking for proper syntax (there really should be a '@' somewhere in the address, for example) goes a long way, but it by no means validates that you can send an email to the address and it will get delivered.
EmailResolver can do that crucial validation in a process involving up to five steps. First comes a syntax check, then EmailResolver finds out whether mail servers exist for the address' domain only to try to verify the address with these servers in the next step. If this test fails, EmailResolver tries to actually send a message. All these steps can be flexibly and easily used from -- and this is the drawback -- any program supporting OCX controls. |
|
|
Manufacturer's Page
|
|
|
|
