Delivery-Date: Mon, 04 Aug 2014 03:16:16 -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 E857E1E0351;
	Mon,  4 Aug 2014 03:16:14 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id F2746304A8;
	Mon,  4 Aug 2014 07:16:07 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 2DC953048A
 for <tor-talk@lists.torproject.org>; Mon,  4 Aug 2014 07:16:04 +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 QTfEqZh4Jryy for <tor-talk@lists.torproject.org>;
 Mon,  4 Aug 2014 07:16:04 +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 095DB30103
 for <tor-talk@lists.torproject.org>; Mon,  4 Aug 2014 07:16:04 +0000 (UTC)
Received: from fulvetta.riseup.net (fulvetta-pn.riseup.net [10.0.1.75])
 (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 0E94E51A13
 for <tor-talk@lists.torproject.org>; Mon,  4 Aug 2014 00:16:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1407136561; bh=u0qDxDzFbagGDqT8QXedW/701qtGT0ATvLIDakdQ3dY=;
 h=Date:From:To:Subject:From;
 b=UeumqFWtaRiCEcUdF3rSDCVk+eb9seDqbpacanSS059XeBkuRqsP9JBVGa+0mfafV
 /q1RBEbf1GkhXZ+FOua+fkIXeme6XmP+nRryWT8L7FfMe11VLZ9hoXUEZngbVUQNIH
 DuAk9FWPBHSnckQJawEyoOIEjNtdeIWKNgyn+hvs=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: shmick@riseup.net) with ESMTPSA id 1DD8E329
Message-ID: <53DF3328.80702@riseup.net>
Date: Mon, 04 Aug 2014 17:15:52 +1000
From: "shmick@riseup.net" <shmick@riseup.net>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
X-Virus-Scanned: clamav-milter 0.98.1 at mx1
X-Virus-Status: Clean
Subject: [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>

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

