Delivery-Date: Mon, 13 Apr 2015 15:55:35 -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 7E0EC1E0315
	for <archiver@seul.org>; Mon, 13 Apr 2015 15:55:33 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 6C1A833FAC;
	Mon, 13 Apr 2015 19:55:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 38BE533F3F
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 19:55:28 +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 yggFg965GXiv for <tor-talk@lists.torproject.org>;
 Mon, 13 Apr 2015 19:55:28 +0000 (UTC)
Received: from smtp3.hushmail.com (smtp3.hushmail.com [65.39.178.200])
 (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 ED28933DEC
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 19:55:27 +0000 (UTC)
Received: from smtp3.hushmail.com (localhost [127.0.0.1])
 by smtp3.hushmail.com (Postfix) with SMTP id 47915E019D
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 19:55:25 +0000 (UTC)
Received: from smtp.hushmail.com (w8.hushmail.com [65.39.178.52])
 by smtp3.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 19:55:25 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id 18C96E0432; Mon, 13 Apr 2015 19:55:25 +0000 (UTC)
MIME-Version: 1.0
Date: Mon, 13 Apr 2015 15:55:24 -0400
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <552C1A33.20206@rawbw.com>
References: <5527BB80.8010708@sophiehassfurther.com>
 <20150410183853.GA32173@riseup.net> <552820C1.8050203@sophiehassfurther.com>
 <20150410215018.F057CC0D3A@smtp.hushmail.com>
 <5528C834.7020305@sophiehassfurther.com> <552AFCCA.6040609@rawbw.com>
 <20150413171551.E4E4BE042D@smtp.hushmail.com> <552C1189.2050501@rawbw.com>
 <20150413191331.9AF42E0433@smtp.hushmail.com> <552C1A33.20206@rawbw.com> 
Message-Id: <20150413195525.18C96E0432@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 Yuri,

I, er, don't think what you're proposing is the answer to the OP's
problem.

If they're using a port which is only supported by 3 exits they'll
still have the problem. If one exit is blocked and they choose that
one the mail server will see further attempts as possibly malicious.
At least one factor is the need to avoid the blacklisted exits in the
first place. That's hard to do if they've been using the same handful
of exits. Someone may be attempting to break into their account and
the blacklist of the exit may be warranted.

Furthermore, it hasn't been identified that the problem is a
connection which is remaining open across new identities. That's just
a behavior observed for arbitrary traffic in the wild. It's should be
highly unlikely for email traffic alone to cause this behavior. It
would require their imap/smtp traffic to coincide with some webmail
traffic across exits where one is blocked. It was me who mentioned it.
That was before noticing the port number and it's rarity at exit
policies.

I've only ever seen the problem described as circuits held open (with
TorBirdy) under very specific circumstances. It cannot yet be the
cause of the OP's problem. Not enough troubleshooting done. It's
actually more likely to be the port.

Anyway, telnet isn't hard, you could just ask tor-talk. The hardest
part is getting the right format of cookie for (default)
authentication. It's harder to get Vidalia working.
--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

