-
Notifications
You must be signed in to change notification settings - Fork 159
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
Comments
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. |
How to use micro servers, can give me an example? @NexaVerse-AI |
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. |
@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 |
Speak with proxy providers to allow you access, LMK if you get someone allowing access to these ports. Since we are also looking for the same. Sent from my iPhoneOn Oct 27, 2024, at 9:43 AM, ashik-rafat-reea ***@***.***> wrote:
@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
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
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?
The text was updated successfully, but these errors were encountered: