-
Notifications
You must be signed in to change notification settings - Fork 232
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
Fix HELO #65
Comments
A little late now, but you could use a rotating proxy, for example with TOR, changing your IP address every 100 (or whatever) tested accounts. |
Thanks , but I think the tor's IP have low quality and are banned by default. I only use TOR for low level websites not for microsoft or gmail. |
I have used rotating TOR IP's for performing security audits for big organisations. Never had an IP blocked because it was a TOR exit node (and if it would be, I'd just switch to a new IP). As TOR exit nodes are typically end users, I don't think you can consider them of low quality. But I don't intend to discuss this as it was only an example. You could obviously also use a VPN service, where you pay some money to get premium IP addresses (I would recommend to check if the VPN allows this) |
I had a similar issue so I made a pull request with an additional feature to pass an alternative hostname to SMTP HELO - #67 |
My IP has been blocked on spamhaus.com and abuseat.org.
The reason is:
"HELOs as 192.168.0.104. Not only is this a violation of RFC2821/5321 section 4.1.1.1, it's even more frequently a sign of infection."
Any idea to fix the HELO when checking the emails of my newsletter users?
The text was updated successfully, but these errors were encountered: