Oddbean new post about | logout
▲ ▼
Alex Gleason 🐍🚬 | 1 months ago (raw) | export | reply | flag +11 
 Here is a list of IPs I have blocked associated with spam on my relay. Since I haven't solved the root of the problem yet, I've just been playing a cat and mouse game.

54.82.2.237
3.90.13.144
18.215.247.200
52.87.211.14
▲ ▼
Crossroad [HUN] | 1 months ago (raw) | root | parent | reply | flag 
 Dynamic IP's are fun to block. Did you noticed thereply guy in this thread?
▲ ▼
sudocarlos | 1 months ago (raw) | root | parent | reply | flag +1 
 Surprised they're not behind vpn
▲ ▼
nicodemus | 1 months ago (raw) | root | parent | reply | flag 
 Those are AWS IPs. No need for a vpn. They can (programmatically) recycle them faster than anyone can block them.
▲ ▼
sudocarlos | 1 months ago (raw) | root | parent | reply | flag +1 
 For free?
▲ ▼
nicodemus | 1 months ago (raw) | root | parent | reply | flag +1 
 Yeah. They don’t have to be elastic IPs.
▲ ▼
semisol | 1 months ago (raw) | root | parent | reply | flag 
 AWS Lambda is something you can easily abuse for a lot of IPs…
▲ ▼
nicodemus | 1 months ago (raw) | root | parent | reply | flag 
 Maybe temporarily block all AWS: https://docs.aws.amazon.com/vpc/latest/userguide/aws-ip-ranges.html

You may be blocking some good relays, but not all of them. And certainly not clients. 

You could then whitelist specific relays. Eh?