-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
Email dns validation passes if domain has no mx record #34092
Comments
I don't think a warning is a valid reason to fail this rule. We depend on the boolean return. |
@driesvints @taylorotwell What is the intended use case for the dns validation? The laravel documentation does not state what the dns validation should do. But with the actual implementation the dns check does not verify that the host has mx dns records so the recipient is reachable. Unreachable hosts pass the validation. |
@tpetry it's best to reference the docs for the underlying email validator library for that. |
indique le répertoire à suivre je ne sais pas ou est ce que je doit effectuer la modification |
Description:
The email dns validation passes emails as correct even if they have no mx record and you really can't send a mail to the domain.
Steps To Reproduce:
Reason for the Result:
Laravel is using
DNSCheckValidation
ofegulias/email-validator
. But their implementation is a little bit tricky:The provided domain passes the dns validation because the domain has an
A record
but a warning is saved that no mx-record was found. So laravel would have to correctly fail theemail:dns
validation if this warning is present as the email recipient is not reachable. At the moment it's just looking at the boolean return value.The text was updated successfully, but these errors were encountered: