Discuss mailing list

[JC <jc AT motorsports-x.com>]

maybe try sending from a different email address or 3.  the might have binned your email. 

On Tue, Dec 27, 2016 at 3:13 PM, Fusl Dash <opennic AT lists.dedilink.eu> wrote:

Short update:

A couple of days ago I sent Spamhaus an email (to notification AT spamhaus.org and sbl-removals AT spamhaus.org) explaining who we are and what we're doing, but as expected, no reply so far. Today I got another email from them:

> REMINDER: Malware DNS server at 185.121.177.177 [SBL325026]

> ------------------------------------------------------------------------
> This is an automated message from the Spamhaus Block List (SBL) database.
> Do not reply to this email directly. Please follow the 'Removal Procedure' shown on the SBL Advisory page (referenced below) instead.
> ------------------------------------------------------------------------
>
> Dear Sir or Madam
>
> On 2016-12-16, Spamhaus has sent you an SBL notification regarding a spam problem in your network:
>
> SBL Advisory: https://www.spamhaus.org/sbl/query/SBL325026
>
> Unfortunately we didn't received any response from you regarding this issue and as of today the spam issued described in the SBL Advisory still exists, threatening thousands of innocent internet users.
>
> We hereby kindly ask you to take a look at the described problem (see link to SBL Advisory page above) and take the appropriate action according to your ToS/AUP as soon as possible to prevent further abuse originating from your network.
>
> If you have alr
>  eady taken care of this problem you can send in a removal request as described in the SBL Advisory page referenced above (see section 'Removal Procedure'). Note that your email must tell us how the spam problem has been terminated (we need to know exactly how the issue has been dealt with and that this spam problem is fully terminated).
>
> SBL System Robot
> The Spamhaus Project
> http://www.spamhaus.org


On 2016-12-17 20:43, Theo B wrote:
> Hi -
>
> So, on thursday a big conversation took place on IRC about Spamhaus deciding to block Fusl's anycast DNS server IPs because a .bit domain was hosting malware. The conversation never really came to a conclusion, so I wanted to throw out some ideas that we talked about.
>
> Here are some of the options we talked about in IRC:
>
> 1. Just ignore Spamhaus and move along(This could be bad because some ISPs block the IPs that Spamhaus blocks)
> 2. Send them an email explaining what we do, and how we're not responsible for any of the content on .bit.. and then hope they remove it.
> 3. Drop .bit completely, and tell them that the content is no longer there.
>
> What do you people think about this?
>
> -Theo
>
>
>
>
> --------
> You are a member of the OpenNIC Discuss list.
> You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org
>

--
Best regards

Fusl - root AT meo.ws - http://meo.ws/