Delivery-Date: Tue, 27 Jan 2015 03:02:02 -0500
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.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,UNPARSEABLE_RELAY,
	URIBL_BLOCKED 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 9DFF21E0CFF
	for <archiver@seul.org>; Tue, 27 Jan 2015 03:02:00 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 273BD32B24;
	Tue, 27 Jan 2015 08:01:57 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 62A5F32AF5
 for <tor-talk@lists.torproject.org>; Tue, 27 Jan 2015 08:01:54 +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 y0uwU0QMQixh for <tor-talk@lists.torproject.org>;
 Tue, 27 Jan 2015 08:01:54 +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 3D1FA32467
 for <tor-talk@lists.torproject.org>; Tue, 27 Jan 2015 08:01:51 +0000 (UTC)
Received: from plantcutter.riseup.net (plantcutter-pn.riseup.net [10.0.1.121])
 (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 A46DC40EA6
 for <tor-talk@lists.torproject.org>; Tue, 27 Jan 2015 08:01:48 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1422345708; bh=VCci9/y3Rbf9XAodRljQFuaTR2R/vVVfffa3QJmOGG4=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=K/x1wc1i4UbM6hLwSQhTxhHOPMxXLHwWs066e+fF4yTfE+1UnkIkidpPM/aTl7VJs
 TnzaNhK+Prb4k8qZ4ZsD2+dyRp26bgDMMKVV0FAmOgMRMiJN0pBxKjouvSOFwhymLi
 WysXL32Sy1ifFr6DQwhYFGmfcbMwnXxtd0fqXlGY=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: angyr) with ESMTPSA id E37642098E
Message-ID: <54C745E2.3070400@riseup.net>
Date: Tue, 27 Jan 2015 08:01:38 +0000
From: Formidable <formidable@riseup.net>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <1c5d656d493ac75cbe3cb229cf0abd38@openmailbox.org>
In-Reply-To: <1c5d656d493ac75cbe3cb229cf0abd38@openmailbox.org>
X-Virus-Scanned: clamav-milter 0.98.5 at mx1
X-Virus-Status: Clean
Subject: Re: [tor-talk] Torbirdy
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>

Why torbirdy is shit?
Only because it leave in header system's timezone?

spencerone@openmailbox.org:
> Cypher cypher at cpunk.us:
>>> A few months ago, I seem to remember the general advice being not to
>>> use Torbirdy. But I see the software was updated only a few months ago
>>> so I assume it's in active development. Can I assume Torbirdy is safe
>>> to use?
>>>
>>> Thanks!
>>> Cypher
>>>
> Jacob Appelbaum jacob at appelbaum.net:
>> Using TorBirdy is fine - the two time leaks are very small issues
>> compared to using Thunderbird without TorBirdy. This is especially so
>> for weak crypto, or a total lack of crypto, which may be possible
>> without TorBirdy.
>>
>> It isn't perfect but it is a whole lot better than plain old
>> SMTP/POP/IMAP, HTML email, etc, etc.
>>
>> Remember we're comparing Thunderbird without TorBirdy vs with
>> TorBirdy: it is strictly better, even if imperfect.
>>
>> All the best,
>> Jacob
> 
> In short, TorBirdy is the shit!
> 
> Wordlife,
> SpencerOne
> 
-- 
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

