--- /dev/null
+Return-Path: <tomi.ollila@iki.fi>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 8B94E431FC9\r
+ for <notmuch@notmuchmail.org>; Wed, 21 Jan 2015 23:26:21 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 2.438\r
+X-Spam-Level: **\r
+X-Spam-Status: No, score=2.438 tagged_above=-999 required=5\r
+ tests=[DNS_FROM_AHBL_RHSBL=2.438] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id ujX1dOUdWGHg for <notmuch@notmuchmail.org>;\r
+ Wed, 21 Jan 2015 23:26:11 -0800 (PST)\r
+Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])\r
+ by olra.theworths.org (Postfix) with ESMTP id 90975431FBC\r
+ for <notmuch@notmuchmail.org>; Wed, 21 Jan 2015 23:26:09 -0800 (PST)\r
+Received: from guru.guru-group.fi (localhost [IPv6:::1])\r
+ by guru.guru-group.fi (Postfix) with ESMTP id E839E1000E0;\r
+ Thu, 22 Jan 2015 09:25:39 +0200 (EET)\r
+From: Tomi Ollila <tomi.ollila@iki.fi>\r
+To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,\r
+ notmuch mailing list <notmuch@notmuchmail.org>\r
+Subject: Re: privacy problem: text/html parts pull in network resources\r
+In-Reply-To: <87ppa7q25w.fsf@alice.fifthhorseman.net>\r
+References: <87ppa7q25w.fsf@alice.fifthhorseman.net>\r
+User-Agent: Notmuch/0.19+29~g7367d27 (http://notmuchmail.org) Emacs/24.3.1\r
+ (x86_64-unknown-linux-gnu)\r
+X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL\r
+ $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F\r
+ !)g;OY^,BjTbr)Np:%c_o'jj,Z\r
+Date: Thu, 22 Jan 2015 09:25:39 +0200\r
+Message-ID: <m2sif3tgy4.fsf@guru.guru-group.fi>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Thu, 22 Jan 2015 07:26:21 -0000\r
+\r
+On Wed, Jan 21 2015, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:\r
+\r
+> If i send a message with a text/html part (either it's only text/html,\r
+> or all parts are rendered, or it's multipart/alternative with only a\r
+> text/html subpart) and that HTML has <img\r
+> src="http://example.org/test.png"/> in it, then notmuch will make a\r
+> network request for that image.\r
+\r
+I noticed the same a few days ago and first test to avoid that was \r
+\r
+(defun open-network-stream (&rest) nil)\r
+\r
+(but then I tried to send email and that failed ;/)\r
+\r
+next was M-x debug-on-entry RER open-network-stream RET\r
+\r
+... but I don,t remember how to manipulate how that continues.\r
+\r
+Latest I've been thinking defadvice around open-network-stream which\r
+asks whether to proceed to it or just return nil.\r
+\r
+I'd like to have buffer-local defadvices... ;) .. but there one could\r
+probably store original open-network-stream location and then flet (or\r
+was it letf) it there...\r
+\r
+Anyway, if there is better, more robust alternative I am (also) very\r
+interested of it...\r
+\r
+Tomi\r
+\r
+\r
+>\r
+> This is a privacy disaster, because it enables an e-mail sender to use\r
+> "web bugs" to tell when a given notmuch user has opened their e-mail.\r
+>\r
+> It's also a bit of a consistency/storage/indexing disaster because it\r
+> means that what you see when you open a given message will change\r
+> depending on the network environment you're in when you open it.\r
+>\r
+> It's also potentially a security problem because it means that anyone in\r
+> control of the remote server (or the network between you and the remote\r
+> server if the image isn't sourced over https) can feed arbitrary data\r
+> into whatever emacs image rendering library is being used. (granted,\r
+> this is not a unique problem because this can already be done by the\r
+> original message sender with a multipart/mixed message, but it's an\r
+> additional exposure of attack surface)\r
+>\r
+> I just raised this on #notmuch, and i don't have the time or the\r
+> knowledge to look into it now, but i think the defaults here need to be\r
+> to avoid network access entirely unless the user explicitly requests it.\r
+>\r
+> --dkg\r
+> _______________________________________________\r
+> notmuch mailing list\r
+> notmuch@notmuchmail.org\r
+> http://notmuchmail.org/mailman/listinfo/notmuch\r