Delivery-Date: Thu, 26 Jun 2014 09:57:03 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 382571E0445
	for <archiver@seul.org>; Thu, 26 Jun 2014 09:57:02 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id AF86A2F62B;
	Thu, 26 Jun 2014 13:56:56 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C10902F63C
 for <tor-talk@lists.torproject.org>; Thu, 26 Jun 2014 13:46:07 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id OLWLxpncSAcQ for <tor-talk@lists.torproject.org>;
 Thu, 26 Jun 2014 13:46:07 +0000 (UTC)
X-Greylist: delayed 1871 seconds by postgrey-1.34 at eugeni;
 Thu, 26 Jun 2014 13:46:07 UTC
Received: from smtp1.hushmail.com (smtp1.hushmail.com [65.39.178.135])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.hushmail.com", Issuer "Self-signed" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 979762F570
 for <tor-talk@lists.torproject.org>; Thu, 26 Jun 2014 13:46:07 +0000 (UTC)
Received: from smtp1.hushmail.com (localhost [127.0.0.1])
 by smtp1.hushmail.com (Postfix) with SMTP id 72D38402ED
 for <tor-talk@lists.torproject.org>; Thu, 26 Jun 2014 13:14:53 +0000 (UTC)
X-hush-tls-connected: 1
Received: from smtp.hushmail.com (w5.hushmail.com [65.39.178.80])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by smtp1.hushmail.com (Postfix) with ESMTPS
 for <tor-talk@lists.torproject.org>; Thu, 26 Jun 2014 13:14:53 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id F0911205A9; Thu, 26 Jun 2014 13:14:52 +0000 (UTC)
MIME-Version: 1.0
Date: Thu, 26 Jun 2014 09:14:52 -0400
To: tor-talk@lists.torproject.org
From: "cbritt@hush.com" <cbritt@hush.com>
In-Reply-To: <CAKjBsQi7059N8Doqtg0YsD9t_N2mAMg5_4rgW09RvVbvYvkqxg@mail.gmail.com>
Message-Id: <20140626131452.F0911205A9@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] unregister exit relay - how to
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

This is why it is recommended that you not commingle the tor exit
relay data and your personal traffic on the same IP.

Do you have a static or dynamic IP address? Please also consider the
possible consequences of running an exit relay from your house...
On 06/26/2014 at 4:01 AM, "Luca"  wrote:Hi to all,

Few days ago I have tried to setup an exit relay on my home laptop ..
with great success :)

The bad part is after seeing my external ip address published to the
world on atlas or globe I have discovered I cannot access anymore to
some site with my payed premium login credential because the sites
policy don't allow  access from the tor network even if I don't use a
tor client to browse the net. :(

For this reason I stopped my exit relay, but to solve the problem I
need to unregister my external ip from the public list as well.

How can I do that?

The relay id is: relisys

Someone can help me please?

thanks
Luca

--
P Please consider the environment before printing this e-mail
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

