Delivery-Date: Thu, 07 Aug 2014 04:22:21 -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.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,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 E55501E033D;
	Thu,  7 Aug 2014 04:22:19 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id D254B2B995;
	Thu,  7 Aug 2014 08:22:15 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 376672C0D0
 for <tor-talk@lists.torproject.org>; Thu,  7 Aug 2014 08:22:12 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 WKW3poHhM9Ar for <tor-talk@lists.torproject.org>;
 Thu,  7 Aug 2014 08:22:12 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 15E3F27DD1
 for <tor-talk@lists.torproject.org>; Thu,  7 Aug 2014 08:22:12 +0000 (UTC)
Received: from fruiteater.riseup.net (fruiteater-pn.riseup.net [10.0.1.74])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (not verified))
 by mx1.riseup.net (Postfix) with ESMTPS id DEAC45315A
 for <tor-talk@lists.torproject.org>; Thu,  7 Aug 2014 01:22:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1407399729; bh=sdoaSaC2U7zrttoWXGvpu02Kykrasv2WNoVcHf3+u/E=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=rEO1ZddNo8bPHT7cAM1wJxe4uMVz9BiEl4GgJwgVZKufv1H1UTq6Xd+dFMlZx+5UV
 Rz+IoptlTJOhe2C94lmwQ6KZfJutOWC/WTXMjQreG0nqvJbinO8SELv8U6pEB1A1RG
 fBKLeHOTSl0IcBlVHGjhDetuO0+Oo1ALCQ58nW10=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: shmick@riseup.net) with ESMTPSA id 0A4D2E90
Message-ID: <53E33106.6050106@riseup.net>
Date: Thu, 07 Aug 2014 17:55:50 +1000
From: "shmick@riseup.net" <shmick@riseup.net>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <53DF3328.80702@riseup.net>
In-Reply-To: <53DF3328.80702@riseup.net>
X-Virus-Scanned: clamav-milter 0.98.1 at mx1
X-Virus-Status: Clean
Subject: Re: [tor-talk] using torbirdy + thunderbird: domains emailing with
 dmarc
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>

https://trac.torproject.org/projects/tor/ticket/12821


shmick@riseup.net wrote:
> im a little concerned about the following and still trying to figure it out:
> 
> if multiple parties are using torbirdy with thunderbird and lets say
> some domain owners have dmarc setup with reporting enabled
> 
> other dmarc capable domains (gmail, hotmail) will send back reports with
> the IP used for mail transmission & respond with fail or pass
> 
> essentially you'll see fail every time if you use torbirdy *and* your
> domain is configured with dmarc, and its going to leak the IP you sent
> email from (logged in with thunderbird to send) defeating the purpose of
> using torbirdy
> 
> the dmarc queries are going out in the usual clear dns
> 
> are there any other shortcomings here that are of concern?
> 
> is dmarc reporting too privacy invasive in this situation to bother
> implementing, and better left to business/companies ?
> 
-- 
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

