Can it ban the IP after x tries?
As every measure it can cause colateral damage but also as every measure one should know what one is doing anyway when it comes to blocking and locking out.That’s not something I’d like to add as IP’s can be reassigned and at some point be valid, or they are using a public WiFi.
Maybe a timeout so they stop bombarding.
I did block a bunch of very nasty ones via .htaccess, sometimes even whole IP ranges. No big deal for me as my userbase is pretty regional. So it would be really handy to have some sort of mechanism to make use of those IP addresses. In a perfect world they would be automatically fed to .htaccess for a couple of weeks, in a less perfect one one could export them in a more comfortable way than c+p.Block unwanted IP’s at the server level or with Cloudflare
Had one today. Bounced email because the email address was incorrect. This was definitely someone trying to sign up as the bounced email was the activation email.not.com is a valid domain that belongs to "Next Online Technologies":
It also has a valid DNS entry for the mx:
$ dig -t mx not.com
; <<>> DiG 9.10.6 <<>> -t mx not.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55124
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;not.com. IN MX
;; ANSWER SECTION:
not.com. 300 IN MX 75 isaac.mx.cloudflare.net.
not.com. 300 IN MX 94 linda.mx.cloudflare.net.
not.com. 300 IN MX 30 amir.mx.cloudflare.net.
So the domain exists, the mx entry exists but the mailbox for the localpart of the address does not exist, thus you get a bounce. Completely different story from what you wrote in your last post.
Anyone can use any mailaddress during registration and as long as there's an mx entry for the domain the server will try to deliver the registrasion mail (as it does and can not know if the mailbox/mailaddress exists). A "mailfilter" whatever that may be cannot circumvent that - how should it do that?
First thing you should find out is wether the mails you get are caused by registration attemps or by the contact form. Should not be too difficult. If they come in masses it is probably automated and then the according spaminator variant could probably help.
After three months the counter has risen to slightly more than 22.000 registration attempts (despite haven blocked some very nasty IPs via .htaccess in the meantime). A dramatic rise over the last weeks.Short update on how it is going nine days after the installation according to the logs:
- the registration spaminator has caught
• 82 registration attempts
This counter is at ~9.500 at the moment.- the login spaminator has caught
• 107 login attempts
1300 so far for meThis addon has now "blocked" (we're invite-only so they couldn't register without a code anyway) 22,806 spam registration attempts on my site. If my site was open and I didn't have this addon I'd probably have abandoned being a forum owner by now due to these spam registrations and the extra work dealing with them.
This should be on everyone's essential addons buy list
I bought this 5 years ago for a ridiculously low price (it is still ridiculously low now) when my site was an open site. The first 3 years it maybe caught 6,000 in total (I was disappointed1300 so far for me
It was so many I had to truncate the log.
Requested by the author
Ozzy is singlehandely demonstrating the need for a better content delivery system so people don't miss anything...Yoooo what??
We use essential cookies to make this site work, and optional cookies to enhance your experience.