Feature/catchall #43
Open
Feature/catchall #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@syrusakbary Any changes of merging this in? (just editing to re-ask :) ) |
|
Please merge? |
1 similar comment
|
Please merge? |
carlosdauden
approved these changes
Dec 17, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Option 'cathcall' will not validate email addresses when they are on a catch-all domain :)
Sometimes this is handy ....
Enter email for validation: email_address@catchall.domain
Validate MX record? [yN] y
Try to contact server for address validation? [yN] y
Accept catch-all? [yN] y
Valid!
Enter email for validation: email_address@catchall.domain
Validate MX record? [yN] y
Try to contact server for address validation? [yN] y
Accept catch-all? [yN] n
Invalid!