Delivery-Date: Wed, 29 Apr 2015 17:26:08 -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,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 8AAED1E0AC4
	for <archiver@seul.org>; Wed, 29 Apr 2015 17:26:02 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9111420E3E;
	Wed, 29 Apr 2015 21:26:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 4026720DF0
 for <tor-talk@lists.torproject.org>; Wed, 29 Apr 2015 21:25:57 +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 9DcaYvpYg51z for <tor-talk@lists.torproject.org>;
 Wed, 29 Apr 2015 21:25:57 +0000 (UTC)
Received: from dd15500.kasserver.com (dd15500.kasserver.com [85.13.136.184])
 (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 0E80020B0D
 for <tor-talk@lists.torproject.org>; Wed, 29 Apr 2015 21:25:57 +0000 (UTC)
Received: from 127.0.0.1 (tor-exit-node.as6724.net [85.214.11.209])
 by dd15500.kasserver.com (Postfix) with ESMTPSA id E8EA95CE075F
 for <tor-talk@lists.torproject.org>; Wed, 29 Apr 2015 23:25:52 +0200 (CEST)
Message-ID: <55414C5F.20408@sophiehassfurther.com>
Date: Wed, 29 Apr 2015 21:25:51 +0000
From: Sophie Hassfurther <sophie@sophiehassfurther.com>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <20150416215238.37FBBC03DD@smtp.hushmail.com>
 <55315DC9.50802@sophiehassfurther.com>
 <20150424000609.73C53E04DA@smtp.hushmail.com>
 <5539FE14.8040503@sophiehassfurther.com>
 <20150425174822.BA18A40C08@smtp.hushmail.com>
 <553C1337.8070109@sophiehassfurther.com>
 <20150427202424.49EEF412BA@smtp.hushmail.com>
In-Reply-To: <20150427202424.49EEF412BA@smtp.hushmail.com>
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 Leeroy,

Wow, that is one detailed explanation!

You have been a great help in the course of my Tor adventures, thanks
for all the support!

Cheers
Sophie



l.m:
> Hi Sophie,
> 
>> If I would like to suggest to add a warning to the "Before 
>> using TorBirdy", where would be the right place to do so?
> 
> If you would like to submit the feature request what you would first
> do is connect to Tor's bug tracker [0]. From there you can either
> register for your own account or use the credentials listed in the
> 'Welcome' text on the first page. Select 'New Ticket' and fill in the
> ticket. Choose 'enhancement' for type and 'TorBirdy' for the
> component. If you wish to reference the discussion here on tor-talk
> you can use the links available in the archives [1].
> 
> [0]https://trac.torproject.org
> [1]https://lists.torproject.org/pipermail/tor-talk/2015-April/037455.html
> 
>> Would you define failure to use an exit as a) not being
>> able to send emails over this exit and therefore 
>> establishing a connection to a new exit or as b) when I 
>> get a warning saying "blocked using mail.badip.de"?
>> Because from how I understand this, and please correct 
>> if I am wrong,TorBirdy might connect to a different exit, 
>> when the current exit doesn't support the port I am using.
> 
> Tricky. A failure could be both. Tor tries to guess if an exit will
> allow your exiting traffic but it's not a guarantee. In which case,
> you're correct, a new exit is chosen. Perhaps from existing circuits
> or by building a new circuit if needed. This would also occur if the
> connection to the mail server is refused. A response 'blocked' is not
> be a failure in the usual sense. The connection succeeds in a manner
> of speaking but is closed before sending data. Thanks for pointing
> that out.
> 
> --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

