We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 smtp hosts have a strict connection limit (10 per second or less) and sslscan --starttls-smtp returns multiple socket errors:
sslscan --starttls-smtp
ERROR: The host mx1.cesactivationprod.iphmx.com on port 25 did not appear to be an SMTP service. ERROR: Could not connect.
Instead of the original smtp message:
421 #4.4.5 Too many connections from your host.
This can be reproduced using the Cisco CES servers:
sslscan --starttls-smtp mx1.cesactivationprod.iphmx.com
It would be great if you add rate limit warning and stop the test when the 421 code appears.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Some smtp hosts have a strict connection limit (10 per second or less) and
sslscan --starttls-smtp
returns multiple socket errors:Instead of the original smtp message:
This can be reproduced using the Cisco CES servers:
It would be great if you add rate limit warning and stop the test when the 421 code appears.
The text was updated successfully, but these errors were encountered: