Delivery-Date: Fri, 10 Apr 2015 14:37:46 -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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY
	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 60FA71E0B07
	for <archiver@seul.org>; Fri, 10 Apr 2015 14:37:41 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 3D0CF33FBE;
	Fri, 10 Apr 2015 18:37:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 0291A33F3F
 for <tor-talk@lists.torproject.org>; Fri, 10 Apr 2015 18:37:33 +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 D2sDEBSxY5E3 for <tor-talk@lists.torproject.org>;
 Fri, 10 Apr 2015 18:37:32 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id D25A433F0A
 for <tor-talk@lists.torproject.org>; Fri, 10 Apr 2015 18:37:32 +0000 (UTC)
Received: from berryeater.riseup.net (berryeater-pn.riseup.net [10.0.1.120])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id 2DFAC410CB
 for <tor-talk@lists.torproject.org>; Fri, 10 Apr 2015 18:37:30 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1428691050; bh=tDp2kYyOuvpq5KMBVfR8b8dQN702fOXtQ2NWW0AQi10=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=ZoLr26UzMRxP8lxhN0xBoQjtLUv0qU1JF/j3mijYLaf8wrCne/PfAvOEvHX1nlbUA
 UhT4yyE3mnvrrTCV1jffEjiyI1u+URwlYyQuLfPVwl1SYfkhW3jLEX3sN7y1lwczcd
 e/Dn7rNAHOXyeBeWSNS9b0Uz8TzdytBBdE9Zxf3E=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: azadi) with ESMTPSA id 73618400D1
Date: Fri, 10 Apr 2015 14:38:53 -0400
From: Sukhbir Singh <azadi@riseup.net>
To: tor-talk@lists.torproject.org
Message-ID: <20150410183853.GA32173@riseup.net>
Mail-Followup-To: tor-talk@lists.torproject.org
References: <5527BB80.8010708@sophiehassfurther.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <5527BB80.8010708@sophiehassfurther.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Virus-Scanned: clamav-milter 0.98.6 at mx1
X-Virus-Status: Clean
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>

* 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

