Open alexanderoskin opened 1 year ago
mail.ru emails are classified as risky, because they are catch-all:
telnet mxs.mail.ru 25
Trying 94.100.180.31...
Connected to mxs.mail.ru.
Escape character is '^]'.
220 mxs.mail.ru ESMTP ready
HELO mail.example.com
250 mxs.mail.ru
MAIL FROM: <robot@example.com>
250 2.0.0 OK
RCPT TO: <daflkjdsfkhewqdsaklfhldashf123@mail.ru> # Or any random address
250 Go ahead
I haven't found a reliable way to detect valid mail.ru emails. Maybe there is an API endpoint, like the one I linked in https://github.com/reacherhq/check-if-email-exists/issues/937 ? I also didn't fully try that though.
I see. Ok, I will do research, maybe will find any suitable method.
I think you can close the issue now
I prefer to keep it open. I would like to try if https://github.com/megadose/holehe/blob/master/holehe/modules/mails/mail_ru.py works.
Is someone willing to try and maybe create a PR?
@amaurym would look into it this weekend
hey @amaury1729, will take a look at it!
Email Provider
mail.ru
What happened?
Related to this issue https://github.com/reacherhq/check-if-email-exists/issues/771
All mail.ru emails are marked as risky. Telnet output shows email address as valid.
Docker backend mark email ya.jeam@mail.ru as risky. Reacher API (https://api.reacher.email/v0/check_email) mark email ya.jeam@mail.ru as risky.
Relevant log output
No response