Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FEATURE] SMTP error interpretation #19

Closed
AlexeyDemidov opened this issue Mar 26, 2019 · 1 comment
Closed

[FEATURE] SMTP error interpretation #19

AlexeyDemidov opened this issue Mar 26, 2019 · 1 comment
Assignees
@bestwebua
Labels
enhancement New feature or request

Comments

@AlexeyDemidov
Copy link

Error code 550 followed by user|account doesn't cover all possible error response which indicate that email doesn't exist. See an example of SMTP error parsing for userunknown status.
@bestwebua
Copy link
Member

bestwebua commented Mar 26, 2019 •
edited
Loading

Thanks for example. But this option for cases when SMTP server does not return an exact answer that the email does not exists.

@bestwebua bestwebua added the invalid This doesn't seem right label Mar 26, 2019
@bestwebua bestwebua added enhancement New feature or request and removed invalid This doesn't seem right labels May 10, 2019
@bestwebua bestwebua self-assigned this May 10, 2019
@bestwebua bestwebua mentioned this issue May 10, 2019
Merged
5 tasks
bestwebua added a commit that referenced this issue May 10, 2019
@bestwebua
Feature/configurable smtp error body, #19 (#37)
ef26feb 
* Implement Validate::Base#configuration
* Implement configurable smtp error body
* Update linter configuration
* Update tests
* Update readme
* Update gem version
@bestwebua bestwebua changed the title SMTP error interpretation [FEATURE] SMTP error interpretation Nov 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bestwebua bestwebua

Labels
enhancement New feature or request
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AlexeyDemidov @bestwebua