{"id":446,"date":"2014-02-17T10:01:00","date_gmt":"2014-02-17T09:01:00","guid":{"rendered":"http:\/\/issues2.edpnet.be\/?p=446"},"modified":"2015-02-13T09:34:11","modified_gmt":"2015-02-13T08:34:11","slug":"17-february-2014","status":"publish","type":"post","link":"https:\/\/issues.edpnet.nl\/?p=446","title":{"rendered":"17 February 2014"},"content":{"rendered":"
Update 18\/02\/2014 – 13h45<\/b>
While not responding to tickets or mails from our NOC team, Spamhaus did respond on one of our Tweets. We didn’t get an official confirmation via email from Spamhaus, but it seems that our range isn’t listed anymore. We can see that we had green light on http:\/\/www.spamhaus.org\/sbl\/latest\/<\/a> We will do some testings and we advize you to do this as well. It can take a couple of hours before the entire internet is up to date of the deblocking of our range. From the moment that Spamhaus confirmed to us officially, we will update our blog again.<\/p>\n

Update 18\/02\/2014 – 10h15<\/b><\/p>\n

1 listing remains which needs to be acknowledged by Spamhaus. (After acknowledgement Spamhaus will deblock our IP range as soon as they are willing to do so). As said before, Spamhaus blocks entire IP ranges of ISP, instead of 1 specific IP address or range of the spammer. This is a drastic decision, but as an independant organisation, they set their own rules and procedures. And in this way they often have internet service providers in an unwanted stranglehold. Nevertheless we always have good communication with Spamhaus. We are very sorry for the inconveniences. <\/div>\n

Update 17\/02\/2014 – 16h47<\/b>
12 individual spamhaus listings are blocked. 8 are acknowledged by Spamhaus. We are waiting for the last 4 listings remaining. After we surely hope Spamhaus can deblock our entire IP range.<\/p>\n

Dear customer,<\/p>\n

Spamhaus.org listed our IP ranges, due to 2 customers who seems to be spammers. Meanwhile our NOC team took the necessary steps to block these spammers, but you are unable to send mails to people who use spamhaus.org as a filter to receive e-mail.<\/p>\n

As we already communicated in the past, spamhaus.org always take extreme measurments by blocking entire IP ranges, instead of the one specific spamming IP address. <\/p>\n

As an ISP we do not do any filtering of traffic and we do allow fixed IP users to have their own mail servers, but we try to pro-actively scan as much traffic as we can for possible abuse. We already redefined our policy regarding traffic filtering to prevent such issues, but it seems now that we need to protect ourselves and our customers even more. <\/p>\n

We still believe that over the years we already took quite a lot of measurements to get the internet free from abuse and spam as we closed port 25 for all our dynamic IP users and we implemented a state of the art Cisco Iron Port mail system.
Nevertheless we still do not do any traffic filtering and we don’t want to.<\/p>\n

We are in contact with Spamhaus.org in order to delist our IP-ranges as soon as possible.<\/div>\n","protected":false},"excerpt":{"rendered":"

Update 18\/02\/2014 – 13h45While not responding to tickets or mails from our NOC team, Spamhaus did respond on one of our Tweets. We didn’t get an official confirmation via email from Spamhaus, but it seems that our range isn’t listed anymore. We can see that we had green light on http:\/\/www.spamhaus.org\/sbl\/latest\/ We will do some […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[24,25,40],"class_list":["post-446","post","type-post","status-publish","format-standard","hentry","tag-closed","tag-issue","tag-update"],"_links":{"self":[{"href":"https:\/\/issues.edpnet.nl\/index.php?rest_route=\/wp\/v2\/posts\/446","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/issues.edpnet.nl\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/issues.edpnet.nl\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/issues.edpnet.nl\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/issues.edpnet.nl\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=446"}],"version-history":[{"count":0,"href":"https:\/\/issues.edpnet.nl\/index.php?rest_route=\/wp\/v2\/posts\/446\/revisions"}],"wp:attachment":[{"href":"https:\/\/issues.edpnet.nl\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=446"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/issues.edpnet.nl\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=446"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/issues.edpnet.nl\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=446"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}