EmailVerify.NET v4.2 released: better greylisting detection and improved control flow
Published on Thursday, April 21, 2011
This minor release features a renewed temporary mailbox handling, with a more precise greylisting detection that supports many new SMTP servers: now every SMTP status code that reports a temporary unavailability of a mailbox will correctly map back to the MailboxTemporarilyUnavailable verification status.
Version 4.2 also includes an improvement to the email validation flow with regards to the way disposable email addresses (like @mailinator.com, @10minutemail.com, @despam.it, etc.) are handled: this kind of validation can now be configured to be non-fatal, and have EmailVerify.NET to keep validating upper validation levels (if requested) as well. This way, despite the fact many DEAs providers are known to be catch-all, you can force the component to validate mailboxes for them in any case.
We have added a new property named IsDisposableEmailAddress to the validation result, so that you can always check if a given email address has been detected as disposable (on the Disposable validation level) or not.
This release also includes a bugfix for a weird licensing issue that happened under certain ASP.NET impersonation scenarios and, of course, an updated reference guide that reflects the newest changes in the component.
Stay tuned! :)
--
Efran Cobisi
EmailVerify.NET lead developer
Version 4.2 also includes an improvement to the email validation flow with regards to the way disposable email addresses (like @mailinator.com, @10minutemail.com, @despam.it, etc.) are handled: this kind of validation can now be configured to be non-fatal, and have EmailVerify.NET to keep validating upper validation levels (if requested) as well. This way, despite the fact many DEAs providers are known to be catch-all, you can force the component to validate mailboxes for them in any case.
We have added a new property named IsDisposableEmailAddress to the validation result, so that you can always check if a given email address has been detected as disposable (on the Disposable validation level) or not.
This release also includes a bugfix for a weird licensing issue that happened under certain ASP.NET impersonation scenarios and, of course, an updated reference guide that reflects the newest changes in the component.
Stay tuned! :)
--
Efran Cobisi
EmailVerify.NET lead developer