-
-
Notifications
You must be signed in to change notification settings - Fork 64
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.
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
[FEATURE] Opt out of SMTP validation #48
Comments
Hello. @giovannibonetti! Thanks for your feedback. I will add default validation as configurable option in next release. At the moment you can run validation with parameter: Truemail.validate('email@domain', with: :mx) or configure not smtp validation for domain(s) that reject smtp validation Truemail.configure do |config|
config.validation_type_for = { 'somedomain.com' => :mx }
end |
Thanks for the quick response! 😀 |
@giovannibonetti, this feature is available in Truemail 1.1.0 🚀 Cheers! |
Thanks, @bestwebua! 😀 By the way, do you think it makes sense to make require 'truemail'
Truemail.configure do |config|
config.default_validation_type = :mx
end I tried to use it like that but it still requires a verifier_email.
I know I can just set a dummy value to |
Hi, @giovannibonetti! Thanks for your feedback. But what will happen if |
Ok, understood. Thanks for your time! |
You're welcome! |
New Issue Checklist
Feature request
Hi! I really like this library, but I'm wondering if there is any drawback to using the final SMTP validation. Is it possible that the my email domain (from
verifier_email
) might get an increase in its spam score since the verification sends a real SMTP request for each verified email address on behalf of it?What do you think about making SMTP validation optional and also disabling it by default if
verifier_email
is not set?The text was updated successfully, but these errors were encountered: