Configuration

Creates an email validation configuration with customizable parameters for verifier identity, timeouts, validation rules, and domain management. This configuration is used by all validation nodes in the Email Validator package.

Common Properties

Name - The custom name of the node.
Color - The custom color of the node.
Delay Before (sec) - Waits in seconds before executing the node.
Delay After (sec) - Waits in seconds after executing node.
Continue On Error - Automation will continue regardless of any error. The default value is false.

info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Input

Verifier Email - Email address used as the verifier identity for SMTP validation. This email represents your automation in SMTP conversations with mail servers. Required field.

Output

Configuration Id - Unique identifier for the created configuration. Pass this ID to validation nodes (Validate Regex, Validate MX, Validate MX Blacklist, Validate SMTP) to use this configuration.

Options

Basic Options

Verifier Domain - Domain used for verification. If not specified, defaults to the domain of the verifier email address.
Email Pattern - Custom regex pattern for email format validation. Override the default email validation pattern with your own regular expression.
Smtp Error Body Pattern - Regex pattern to match SMTP error response bodies. Use this to customize how SMTP errors are detected and handled.

Timeout & Connection Options

Connection Timeout - Connection timeout in seconds. Default: 2 seconds. Adjust based on network conditions and mail server response times.
Response Timeout - Response timeout in seconds. Default: 2 seconds. Maximum time to wait for SMTP server responses.
Connection Attempts - Number of connection attempts before failing. Default: 2. Retry logic for handling temporary network issues.
Smtp Port - SMTP port for validation connections. Default: 25. Most mail servers use port 25 for SMTP.

Validation Type Options

Validation Type Default - Default validation type for all emails. Choose from:
- regex - Fast format validation using regular expressions
- mx - DNS MX record lookup
- mx_blacklist - MX record blacklist checking
- smtp - Full SMTP server verification
Validation Type By Domain - Domain-specific validation types as an object. Override the default validation type for specific domains.

Example:
```
{
  "gmail.com": "smtp",
  "tempmail.com": "regex",
  "company.com": "mx"
}
```

Domain Whitelist/Blacklist Options

Whitelisted Domains - Array of domains to whitelist. These domains will be considered valid or given special treatment during validation.

Example:
```
["trusted-domain.com", "partner-company.com"]
```
Whitelist Validation - When enabled, only validate emails from whitelisted domains. Emails from non-whitelisted domains will automatically fail validation. Default: false.
Blacklisted Domains - Array of domains to blacklist. Emails from these domains will automatically fail validation.

Example:
```
["disposable-email.com", "temporary-mail.com", "spam-domain.com"]
```
Blacklisted Mx Ip Addresses - Array of MX IP addresses to blacklist. Emails whose MX records resolve to these IPs will fail validation.

Example:
```
["1.2.3.4", "5.6.7.8"]
```

Advanced Options

DNS - Custom DNS server address for MX lookups. Use a specific DNS server instead of the system default.
Not Rfc Mx Lookup Flow - When enabled, use non-RFC compliant MX lookup flow. This can help with certain non-standard mail server configurations. Default: false.
Smtp Fail Fast - When enabled, fail immediately on first SMTP error without retrying. Default: false. Use this for faster validation when you don't need retry logic.
Smtp Safe Check - When enabled, use safe SMTP checking to avoid triggering spam filters. This mode is less thorough but reduces the risk of being flagged by mail servers. Default: false.

How It Works

The Configuration node creates a validation configuration object that stores all your validation parameters. When executed:

Validates the verifier email address (required)
Processes all optional configuration parameters
Creates a configuration object with the truemail library
Stores the configuration in memory
Returns a unique Configuration ID

This Configuration ID is then passed to validation nodes, which use the stored configuration to perform email validation.

Requirements

A valid verifier email address
The verifier email should be from a domain you control for SMTP validation
For SMTP validation, ensure your server can make outbound connections on port 25 (or custom SMTP port)

Usage Examples

Basic Configuration

// Simple configuration with just verifier email
msg.verifierEmail = "verify@mycompany.com";

Advanced Configuration with Domain Rules

// Set verifier email
msg.verifierEmail = "verify@mycompany.com";

// Configure validation types by domain
msg.validation_type = {
  "gmail.com": "smtp",        // Full SMTP verification for Gmail
  "yahoo.com": "smtp",        // Full SMTP verification for Yahoo
  "tempmail.com": "regex"     // Quick regex check for known disposables
};

// Blacklist known disposable email domains
msg.black_domains = [
  "guerrillamail.com",
  "10minutemail.com",
  "mailinator.com"
];

Configuration for High-Volume Processing

// Fast configuration for bulk validation
msg.verifierEmail = "bulk-verify@mycompany.com";

// Shorter timeouts for faster processing
// Connection timeout: 1 second
// Response timeout: 1 second

// Enable fail fast
// Smtp Fail Fast: true

// Use MX validation as default (faster than SMTP)
msg.validationTypeDefault = "mx";

Whitelist-Only Validation

// Only validate emails from trusted domains
msg.verifierEmail = "verify@mycompany.com";

msg.white_domains = [
  "mycompany.com",
  "partner-company.com",
  "trusted-client.com"
];

// Enable whitelist validation
// Whitelist Validation: true

Error Handling

The Configuration node returns specific errors in these cases:

ErrInvalidArg - Verifier Email is empty or invalid
ErrInternal - Failed to retrieve configuration parameters
ErrRuntime - Failed to create configuration with the truemail library

Best Practices

Verifier Email Selection
- Use a real email address from a domain you control
- Avoid using personal or sensitive email addresses
- Consider creating a dedicated email for automation validation
Timeout Configuration
- Use shorter timeouts (1-2 seconds) for high-volume processing
- Use longer timeouts (3-5 seconds) for more reliable validation
- Adjust based on your network conditions and mail server response times
Validation Type Strategy
- Use regex for quick format checks
- Use mx for fast domain verification
- Use smtp for highest accuracy but slower performance
- Mix validation types using domain-specific rules for optimal balance
Domain Management
- Maintain a blacklist of known disposable email services
- Whitelist trusted partner domains when appropriate
- Regularly update blacklists based on validation results
Resource Management
- Create one configuration per validation workflow
- Reuse the same Configuration ID for batch processing
- The configuration is stored in memory during flow execution

Performance Tips

For bulk email validation, use MX validation instead of SMTP for faster processing
Enable SMTP Fail Fast when you don't need retry logic
Use shorter timeouts for faster validation at the cost of some accuracy
Blacklist known disposable domains to skip expensive validation
Use domain-specific validation types to balance speed and accuracy

Common Errors and Solutions

Error	Cause	Solution
"Verifier Email cannot be empty"	Required input not provided	Ensure Verifier Email input is set
"Failed to create configuration"	Invalid configuration parameters	Check that regex patterns are valid, timeouts are positive numbers
Configuration ID not found in validation nodes	Configuration not created or ID incorrect	Verify Configuration node executed successfully and ID is passed correctly

Security Considerations

Store verifier email in variables or vaults, not hardcoded
Be cautious with SMTP validation as it connects to external mail servers
Use SMTP Safe Check mode when validating from sensitive networks
Consider rate limiting to avoid being flagged as a spam source
Regularly rotate verifier email addresses if doing high-volume validation

Common Properties​

Input​

Output​

Options​

Basic Options​

Timeout & Connection Options​

Validation Type Options​

Domain Whitelist/Blacklist Options​

Advanced Options​

How It Works​

Requirements​

Usage Examples​

Basic Configuration​

Advanced Configuration with Domain Rules​

Configuration for High-Volume Processing​

Whitelist-Only Validation​

Error Handling​

Best Practices​

Performance Tips​

Common Errors and Solutions​

Security Considerations​