You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version of check-if-email-exists (if running it yourself)
lastone
What happened?
Look please one issue, domain for example gaasd@we.de has MX record localhost
and all emails must be mark as invalid
but it's mark as unknown and "accepts_mail": true with is wrong.
I can confirm this issue for example@foo.com as well, it is categorized as unknown but should have been invalid: "is_reachable":"unknown","misc":{"is_disposable":false,"is_role_account":false,"gravatar_url":null,"haveibeenpwned":null},"mx":{"accepts_mail":true,"records":["0.0.0.0."]},"smtp":{"error":{"type":"SmtpError","message":"io: Connection refused (os error 111)"}}; 0.0.0.0. is not a valid record. So, there is currently an issue with the overall MX record validation.
Email to check
gaasd@we.de
From where did you run check-if-email-exists?
self hosted backend api
Version of check-if-email-exists (if running it yourself)
lastone
What happened?
Look please one issue, domain for example gaasd@we.de has MX record localhost
and all emails must be mark as invalid
but it's mark as unknown and "accepts_mail": true with is wrong.
Relevant log output
The text was updated successfully, but these errors were encountered: