Skip to content
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

Some existing mailbox on domain without CatchAll are identified as unreachable #72

Open
plorgue opened this issue Jan 24, 2023 · 1 comment
Assignees
Labels
question Further information is requested

Comments

@plorgue
Copy link

plorgue commented Jan 24, 2023

Hi,

I tried SMTP check on personnal outlook.fr mailbox and it seems that mx record eur.olc.protection.outlook.com don't like consecutive RCPT TO requests.

On smtp.go, I moved the catchAll block code below the test of the real username and the username is correctly detected as deliverable with 250 smtp response code, however this time the RCPT TO request with random username is rejected by mx record with 452 response code.

This issue probably doesn't concern only outlook.fr.

More generally, it may be a good idea to add a feature "safe check" that check the smtp response code and if it is different to 450 the user’s mailbox was unavailable or similare code it doesn't qualified the mailbox as unreachable. I put this idea here but it may be a different issue.

Thanks for all your work

@plorgue plorgue changed the title Some existent mailbox on domain without CatchAll are identified as unreachable Some existing mailbox on domain without CatchAll are identified as unreachable Jan 24, 2023
@lryong lryong added the question Further information is requested label Feb 2, 2023
@lryong lryong self-assigned this Feb 2, 2023
@lryong
Copy link
Contributor

lryong commented Feb 2, 2023

@plorgue
Thanks for your feedback on this issue, it's a good one, the way we handled catchall before may be a bit rough and simple, I'll investigate if there's a better way to handle it. Of course, if you have good suggestions, please feel free to feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants