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
The tool seems to give inconsistent results both on the website (entering the email in the input field), as well as running locally on rust.
For example, 2 hours ago, I checked an email on the reacher website, and it returned "is_reachable": "unknown",
And now, it returns "is_reachable": "safe",
It is definitely not a case of this mailbox receiving too many emails.
More critically, using rust, the status is returning as
"is_reachable": "invalid",
Which is totally wrong... Given that invalid is stated to be.... "We guarantee with a confidence of 99.99% that this email is not deliverable." I really don't think the app should be classifying emails as invalid when it is not actually certain.
The text was updated successfully, but these errors were encountered:
Hmm, yes, "unknown" can be understandable, but the "safe"/"invalid" one does look bad. Could you send me the email you used, to amaury@reacher.email? I'll do some debugging on my side.
This issue should be top on the priority list.
Note: if you want to debug it yourself, the best way would be to run with RUST_LOG=debug env variable, and check the SMTP commands and their responses.
@rxng with the latest #819, #822 and #825 fixes it should be much better now.
Also, consider the fact that the checking performed is nothing but a half-way delivery attempt. So results will really vary depending on the IP you're performing the check from and on from-email parameter, because SMTP servers considers rDNS records, SPF DNS records and IP reputation, where the last one especially changes over time.
So, to have good and consistent results, you should properly setup DNS stuff on the server you're performing checks from, and care about its reputation.
The tool seems to give inconsistent results both on the website (entering the email in the input field), as well as running locally on rust.
For example, 2 hours ago, I checked an email on the reacher website, and it returned
"is_reachable": "unknown",
And now, it returns
"is_reachable": "safe",
It is definitely not a case of this mailbox receiving too many emails.
More critically, using rust, the status is returning as
"is_reachable": "invalid",
Which is totally wrong... Given that invalid is stated to be.... "We guarantee with a confidence of 99.99% that this email is not deliverable." I really don't think the app should be classifying emails as invalid when it is not actually certain.
The text was updated successfully, but these errors were encountered: