Delivery-Date: Mon, 13 Apr 2015 12:21:41 -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.2 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,T_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 AB97A1E0315
	for <archiver@seul.org>; Mon, 13 Apr 2015 12:21:39 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 18AE133667;
	Mon, 13 Apr 2015 16:21:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C946B33667
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 16:21:32 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
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 hsFnyEGHK7Yl for <tor-talk@lists.torproject.org>;
 Mon, 13 Apr 2015 16:21:32 +0000 (UTC)
Received: from smtp10.hushmail.com (smtp10.hushmail.com [65.39.178.143])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.hushmail.com", Issuer "smtp.hushmail.com" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 95F7E33074
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 16:21:32 +0000 (UTC)
Received: from smtp10.hushmail.com (localhost [127.0.0.1])
 by smtp10.hushmail.com (Postfix) with SMTP id A9D36C0277
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 16:21:29 +0000 (UTC)
Received: from smtp.hushmail.com (w8.hushmail.com [65.39.178.52])
 by smtp10.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 16:21:29 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id 5039CE0432; Mon, 13 Apr 2015 16:21:29 +0000 (UTC)
MIME-Version: 1.0
Date: Mon, 13 Apr 2015 12:21:29 -0400
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <5528C834.7020305@sophiehassfurther.com>
References: <5527BB80.8010708@sophiehassfurther.com>
 <20150410183853.GA32173@riseup.net> <552820C1.8050203@sophiehassfurther.com>
 <20150410215018.F057CC0D3A@smtp.hushmail.com>
 <5528C834.7020305@sophiehassfurther.com> 
Message-Id: <20150413162129.5039CE0432@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] TorBirdy seems to connect to the same exit node
	again and again
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>

Hi Sophie,

"Sophie Hassfurther"  wrote:
>[...] so far choosing a new
>identity in Tor did not work for me, but restarting the 
>Tor Browser worked. So maybe some circuits did not 
>close?
>
>Just a general question: is it normal to get connected to 
>the same exit node almost all the time, when I start my 
>mail program?

It would be highly unusual to be connected to the same exit if your
mail servers use standard ports. If I'm not mistaken the port you're
using for outgoing mail (25) is currently only allowed in the exit
policy of 3 exits. This hurts your anonymity, and makes the problem
more apparent. You should try to identify an alternative port for your
outgoing mail server as-soon-as-possible. Note that Tor will, by
design, reuse known good exits. So if the other two exits that handle
port 25 are overloaded this may also contribute to the problem.

You mentioned that restarting Tor Browser worked. A new Tor instance
would have a chance to try (and bias towards) one of the other 2 exits
allowing port 25.

Other things, included for completeness, to try include checking for
torrc modifications:

1a. open the Tor Browser install folder
2a. navigate through the folders Browser, TorBrowser, Data, Tor
3a. make sure torrc is empty (default)
4a. make sure torrc-defaults is original with a date of 12/31/1999
(19:00 or 7:00PM)

-and-

1b. close Thunderbird completely
2b. use new identity in Tor Browser
3b. reopen mail. 

If the problem is indeed a persistent connection holding a circuit
open this action should at least force TorBirdy to use a new circuit
(and exit). Note that a/b will be more effective if you *first* deal
with the problem of the port used by your mail server. If you would
prefer to troubleshoot this without adding any software you can also
connect to the Tor process using Telnet to gather information. Please
indicate which operating system do you use.
--leeroy
-- 
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

