Re: Anyone else blacklisted this morning by rbl.iprange.net?

Alas, these RBLs are often hard-coded into firewalls. Non-sophisticated users just think they have a check box saying "block spam". Fixing those IS hard. I believe there are cases where people have made it hard, but there are limits on how much I believe in protecting people from the consequen

Re: Anyone else blacklisted this morning by rbl.iprange.net?

Alas, these RBLs are often hard-coded into firewalls. Non-sophisticated users just think they have a check box saying "block spam". Fixing those IS hard. -mel > On Jan 4, 2018, at 4:45 PM, John Levine wrote: > > In article > you > write: >> If you're going to run a DNSBL to advertise your

Re: Anyone else blacklisted this morning by rbl.iprange.net?

In article you write: >If you're going to run a DNSBL to advertise your mail software, >perhaps do so in a way that doesn't flip the bird at everyone using it. On the other hand if you're going to use DNSBLs, you really should do the tests in RFC 5782 every once in a while so you stop using BLs

Re: Anyone else blacklisted this morning by rbl.iprange.net?

But what other people have rightfully pointed out is that his behavior is stupid and against the RFC that covers DNSBLs. And it's not simply MX admins here. You have firewalls that are also affected. If you're going to run a DNSBL to advertise your mail software, perhaps do so in a way that does

Re: Anyone else blacklisted this morning by rbl.iprange.net?

I did finally reach someone at realtimeblacklist.com. They've just today shut down the bogus DNS RBL and said they realize now it was a terrible idea. They read and now understand the RBL RFC and promised not to do it again. I appreciate them taking the time to respond, and hopefully they'll als

Re: Anyone else blacklisted this morning by rbl.iprange.net?

As the message said, they use this to force mx admins to remove their entry to stop hammering. I remember other lists did the same. Contact the remote mx admin in order to get this fixed. > Op 2 jan. 2018 om 17:57 heeft Dann Schuler het > volgende geschreven: > > We had a Charter IP address w

Re: Anyone else blacklisted this morning by rbl.iprange.net?

LOL! Apparently Level3 (my upstream) at least has blacklisted their IP, way before it gets anywhere near the Netherlands! traceroute rbl.iprange.net traceroute to rbl.iprange.net (80.127.112.180), 64 hops max, 40 byte packets 1 router1.sb.becknet.com (206.83.0.1) 0.862 ms 0.415 ms 0.365 ms

Re: Anyone else blacklisted this morning by rbl.iprange.net?

Apparently they're widely used by firewall-based anti spam, as we seem to be getting blocked a lot by Juniper, Sonicwall, and Palo Alto firewalls. The outfit is listed in https://en.m.wikipedia.org/wiki/Comparison_of_DNS_blacklists, but seem to have very poor communication options (e.g., WhoIs

Re: Anyone else blacklisted this morning by rbl.iprange.net?

On Tue, 2 Jan 2018, Mel Beckman wrote: I woke up this morning to a barrage of complaints from users that our mail servers' outbound emails are bouncing due to a blacklisting. Sure enough, mxtoolbox.com reports that rbl.iprange.net has blacklisted u

Re: Anyone else blacklisted this morning by rbl.iprange.net?

On Tue, Jan 02, 2018 at 04:46:02PM +, Mel Beckman quoted: > "rbl.iprange.net will mark every ip address as listed to force removal of > this server." Apparently they didn't read section 3.4 of RFC 6471: https://tools.ietf.org/html/rfc6471#page-15 Given this behavior on their part, i

RE: Anyone else blacklisted this morning by rbl.iprange.net?

We had a Charter IP address we don’t actually send email from (it is a backup line that would only send mail if our primary line was down) Blacklisted by these guys at 10:50am EST on 1/1/18, then removed at 3:34pm EST on 1/1/18. MXToolBox alerted us to it, I ran a manual check on their portal, w