tVerifyEmail Standard properties

Schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

Built-In: You create and store the schema locally for this component only.

Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

Edit Schema

The output schema of tVerifyEmail has different read-only columns depending on the options you select in the component Basic settings view. Read-only output columns include:

VerificationLevel: provides you with the verification status of the processed email addresses as the following:

-VALID: means that the email address comply with the defined rule.

-INVALID: means that the email address does not comply with the defined rule.

-CORRECTED: means that the input email does not comply with the defined rule and has been corrected by using the content of the selected columns. This column is available only when you select the Use column content option in the LOCAL Part Options section.

-VERIFIED: means that the email address does exist at the domain. This column is available only when you select the Check with mail server callback option.

-REJECTED: means that the email address does not exist at the domain. This column is available only when you select the Check with mail server callback option.

Suggested_Email: provides you with a suggested content for the email part before the @ sign. The email string is built up from the columns you select from the Use column content view.

Column to validate

Select from the list the column you want to validate with tVerifyEmail.

Check the entire email with regular expression

Select this check box if you want to match the complete email address against a specific regular expression.

Complete regular expression: enter the regular expression against which you want to match email addresses.

This match is done as a first step to optimize the matching process and exclude addresses that have problems before going any further to match the local and domain parts of email addresses.

LOCAL Part Options

Fields in this section will vary according to what option you select. "LOCAL part" in an email address refers to the string before the @ sign.

-Use regular expression: enter in the Pattern field the expression against which you want to check the local part of the email address.

-Use simplified pattern: enter in the Pattern field the simplified pattern against which you want to check the local part of the email address. Select the Show syntax of simplified pattern option to display the syntax to use for simplified patterns. For more information about the syntax, see Simplified pattern syntax for tVerifyEmail.

-Use column content: use the fields in this view to decide the content against which you want to check the local part of the email. If the local part does not match what you have defined, it will be rewritten by using the content of the fields.

-Enable case-sensitive pattern matching: select this check box to enable a case sensitive pattern matching of the local part of email addresses. You can use case sensitive pattern matching with each of the above options.

DOMAIN Part Options

Fields in this view will vary according to what option you select.

-Check the Top-level Domains and the following ones: select this check box to verify the part of the email address which follows the last dot. You can use the Additional Top-level Domains table to add additional top-level domains against which you want to validate email addresses.

-Check domains with a black list: select this option to verify the domains you define in the Domain list table as black listed.

-Check domains with a white list: select this option to verify the domains you define in the Domain List table as white listed.

Check with mail server callback

Select this check box to enable the verification of email addresses by the SMTP server.

With this technique, the mail server verifies the complete address (parts before and after the @ sign). It establishes a successful SMTP connection to the mail exchanger (MX) of the email address. Then it queries the exchanger, and make sure that it accepts the address as a valid one. This is done in the same way as sending an email to the address, however the process is stopped after the mail exchanger accepts or rejects the address.

It is not advisable to enable the SMTP verification when you have a lot of email addresses with different domains to check as some mail servers may not reply correctly and even black list your IP address.

When the mail server accepts all emails from a domain, the component cannot verify whether the email address exists or not.

In all these cases, the component results will only take into account the results from the other rules you set in the component settings.

Only positive integers are supported. The default value is 10.

For performance reasons, when you enter 0, the timeout is set to 10 seconds.

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at the Job level as well as at each component level.

Global Variables

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl + Space to access the variable list and choose the variable to use from it.

For further information about variables, see Talend Studio User Guide.

Usage rule

This component is usually used as an intermediate component, and it requires an input component and an output component.