EmailVerify.NET

• Advanced syntax verification, according to IETF standards (RFC 1123, RFC 2821, RFC 2822, RFC 3490, RFC 3696, RFC 4291, RFC 5321, RFC 5322 and RFC 5336), with support for quoted words, domain literals, non-ASCII domain names (IDNA) and mailboxes, and comments
• DNS validations, including MX record(s) lookup
• Disposable and temporary email address detection
• SMTP connection and availability checking
• Mailbox existence checking, with greylisting and temporary unavailability support
• Catch-all testing

It is completely written in managed code (C#) and is compliant with Common Language Specification (CLS), so it can be used with any other .NET language too, including Visual Basic (VB.NET), C++/CLI, J#, IronPython, IronRuby, F# and PowerShell.

Why choose

Easy to Use

Designed from the ground up to make the developer's life easier, EmailVerify.NET's whole architecture lets you perform a full e-mail validation with just a single method call, whether the job is as simple as a syntax check or as complex as a mailbox existence test.

Here is, for example, what it takes to validate an email address using the default settings for the component:

            var verifier = new EmailVerifier();
            var result = verifier.Verify("john@example.com", VerificationLevel.Mailbox);

            if (result.IsSuccess)
            {
                // TODO: Show a message box with the great news
            }
        

Powerful and Completely Configurable

With a very stable and mature code base, EmailVerify.NET supports six different e-mail address verification depths and allows you to configure every possible aspect of the validation process, including adherence to IETF standards preferences, network-related settings, and timeouts for multi-threaded activities.

In the following snippet, for example, EmailVerify.NET is configured not to allow domain literals in e-mail addresses, while allowing comments and quoted strings. Furthermore, the component is set to use a particular DNS server (instead of a system-configured server) for its lookups:

            verifier.AllowDomainLiterals = false;
            verifier.AllowComments = true;
            verifier.AllowQuotedStrings = true;

            // The component will use just the provided DNS server for its lookups

            verifier.DnsServers.Clear();
            verifier.DnsServers.Add(IPAddress.Parse("10.0.1.18"));
        

            verifier.VerificationTaskProgressChanged += (sender, args) =>
            {
                Console.WriteLine("The address {0} reached level {1}",
                    args.Task.EmailAddress,
                    args.CurrentLevel);
            };
        

High Performance

EmailVerify.NET internally employs a very fast, multi-threaded e-mail address validation engine capable of processing hundreds of items at once using asynchronous-based processing logic and different optimization algorithms. Furthermore, the component exposes dedicated methods and structures to track down and configure each verification activity that may take place in every asynchronous scenario at optimal performance.

            var group = new VerificationTaskGroup();

            // Add some entries to the verification group

            group += new VerificationTask("alice@example.com", VerificationLevel.Dns);
            group += new VerificationTask("bob@example.net", VerificationLevel.Syntax);
            group += new VerificationTask("mike@example.org", VerificationLevel.Smtp);

            // Start the validation of the whole group, asynchronously

            verifier.VerifyAsync(group);
        

            verifier.VerificationTaskGroupProgressChanged += (sender, args) =>
            {
                Console.WriteLine("Group percent processed: {0}%",
                    args.ProgressPercentage);
            };

            verifier.VerificationTaskGroupCompleted += (sender, args) =>
            {
                Console.WriteLine("Whole group completed!");
                Console.WriteLine("{0} items processed.",
                    args.TaskGroup.Count);
            };