Delivery-Date: Fri, 10 Apr 2015 15:13:28 -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=1.2 required=5.0 tests=BAYES_00,
	RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DNSWL_MED,RCVD_IN_SBL_CSS,RCVD_IN_SORBS_WEB,
	T_RP_MATCHES_RCVD autolearn=no 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 7C7B51E0A33
	for <archiver@seul.org>; Fri, 10 Apr 2015 15:13:23 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 69E5034EFF;
	Fri, 10 Apr 2015 19:13:19 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 6024334EF8
 for <tor-talk@lists.torproject.org>; Fri, 10 Apr 2015 19:13:16 +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 AUBA4zdEKoWt for <tor-talk@lists.torproject.org>;
 Fri, 10 Apr 2015 19:13:16 +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 2D60B34EF5
 for <tor-talk@lists.torproject.org>; Fri, 10 Apr 2015 19:13:16 +0000 (UTC)
Received: from 127.0.0.1 (unknown [187.95.34.3])
 by dd15500.kasserver.com (Postfix) with ESMTPSA id 32F285CE034A
 for <tor-talk@lists.torproject.org>; Fri, 10 Apr 2015 21:13:10 +0200 (CEST)
Message-ID: <552820C1.8050203@sophiehassfurther.com>
Date: Fri, 10 Apr 2015 19:13:05 +0000
From: Sophie Hassfurther <sophie@sophiehassfurther.com>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <5527BB80.8010708@sophiehassfurther.com>
 <20150410183853.GA32173@riseup.net>
In-Reply-To: <20150410183853.GA32173@riseup.net>
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>

Thanks Sukhbir Singh for clarifying, thanks justaguy for the suggestion!

My assumption was, that TorBirdy and Tor are connecting to the same exit
node. What I didn't make clear in my first mail, was that my fix
initially was to choose a new identity. And then things got complicated.

When choosing a new identity in TorBrowser, I thought I was also
choosing a new identity in TorBirdy. I was/am still receiving the alert
quite frequently, even right after clicking on "new identity" (it is
always the same IP that gets rejected, sending emails to various
recipients). So that is what caused my confusion. Do I have to "choose a
new identity" from within TorBirdy?

What I didn't mention before is, that refreshing my inbox worked at all
times. But that might have to do with my mail server, right?

Just had the same alert again when trying to send this email. Restarting
TorBrowser seemed to do the trick... but now I can't really replicate
this. Hm.

Thanks for your help, guys.
S.

Sukhbir Singh:
> * Sophie Hassfurther:
> 
>> "An error occurred while sending mail. The mail server responded: 5.7.1
>> Service unavailable; client (176.108.160.214) blocked using
>> mail.badip.de Please check the message recipient xxxxx@xxxxxxxxxx.com
>> and try again."
>>
>> So what I find strange, is that since two days TorBirdy seems to connect
>> to the same exit node whenever I login. When I check the Tor Browser
>> though, it says I am connected to Tor, showing a different (!) IP address.
> 
> The key here is "showing a different IP address", which means that
> TorBirdy is not connecting to the same exit node. The error message
> seems to indicate that trying a different exit may fix the problem
> (since you are using Tor Browser, click the "New Identity" button.)
> 
> Let us know if it works (or doesn't).
> 
-- 
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

