|author||intrigeri <email@example.com>||2016-05-24 21:21:18 +0000|
|committer||intrigeri <firstname.lastname@example.org>||2016-05-24 21:21:18 +0000|
Design doc: link to the relevant ticket.
Such content has a tendency to bitrot, so let's give the (future) reader a chance to check what the current status is. refs: #11215
1 files changed, 1 insertions, 1 deletions
diff --git a/wiki/src/contribute/design.mdwn b/wiki/src/contribute/design.mdwn
index 50e2572..3f472e6 100644
@@ -1032,7 +1032,7 @@ Icedove itself leaks a lot of data and makes DNS requests, for example by
retrieving mail server configurations from a remote server over an insecure
channel. This is prevented by the TorBirdy extension as well as by custom
patches for Icedove in Tails, which we are currently in the process of
+upstreaming ([[!tails_ticket 11215]]).
Icedove generates `Message-ID` headers using the hostname part of
the sender's email address, which does not leak usage of the PELD nor