The only issue against the "dirty" IP address is for a little over a year, I had no problems with this RBL. My problem now is I keep clearing the block, and it gets reset.
This particular RBL has a few complaints about false positives. In fact, for dictionary searches. However the most recent being two years ago. If I really had a problem with the server, you would think a few other RBLs would be tripped. Regarding my web server, I run Nginx. I don't have PHP. I have no CMS. In fact, I don't even allow "put" in the list of commands. I just serve static pages. I read the error log from Nginx. I investigate any hacking activity. What I see is minor league stuff such as attempts to log into WordPress or php admin, neither of which I have. Further, I look up the IP of the hacker. If from a VPS, data center, or anything that isn't an ISP, I block the entire address space associated with the hacker. If the IP goes to an ISP, I handle it on a case by case basis. I don't block edu, though I have in the case of UC Berkeley asked their researches not to fuzz my server. Original Message From: Ralf Hildebrandt Sent: Sunday, July 3, 2016 10:03 AM To: postfix-users@postfix.org Subject: Re: Spamrl.com RBL problem * Matthew McGehrin <drinking.cof...@gmail.com>: > Hello. > > Your assuming that port 25 needs to be open on the local side to send > mail. this is not the case. There are two possibilities here. > > 1. A dirty IP was assigned to your server, and that the previous owner > had a spam issue. Give the shortages of ipv4 addresses, this is often the case -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
