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

SMTP Catch-all detection Response 5.7.1 Service unavailable #126

Open
liuyihan opened this issue Sep 8, 2024 · 4 comments
Open

SMTP Catch-all detection Response 5.7.1 Service unavailable #126

liuyihan opened this issue Sep 8, 2024 · 4 comments

Comments

@liuyihan
Copy link

liuyihan commented Sep 8, 2024

I have deployed this project locally and am conducting SMTP catch-all monitoring, but I encountered an error message: "5.7.1 Service unavailable, Client host [xxx] blocked using Spamhaus." How can I prevent this issue from occurring?

@NexaVerse-AI
Copy link

Try using proxy networks for rotating IP address, however with that you will encounter another issue - that some email services require PTR records for sender.

This can be manageable with using micro servers for those hosts.

@liuyihan
Copy link
Author

liuyihan commented Sep 8, 2024

micro servers

How to use micro servers, can give me an example? @NexaVerse-AI

@NexaVerse-AI
Copy link

NexaVerse-AI commented Sep 8, 2024

Setup small servers, setup PTR and other email config, best approach would be to run postfix or similar so you have valid mail records for your domain.

Then you can run SMTP verification.

You would need several small servers to accomplish and also prevent rate limit, and blacklisting by Spamhaus.
Rotate the IP of your server say every X verifications to be sure you are able to maintain clean IP.

@ashik-rafat-reea
Copy link

@NexaVerse-AI can you provide some tutorial how to implement this? The proxy server i have used, all have blocked 25, 465 and 587 port

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

No branches or pull requests

3 participants