1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <wtogami@gmail.com>) id 1Z5sxp-0002y9-Nj
for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 09:51:57 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.175 as permitted sender)
client-ip=209.85.192.175; envelope-from=wtogami@gmail.com;
helo=mail-pd0-f175.google.com;
Received: from mail-pd0-f175.google.com ([209.85.192.175])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z5sxo-0002Jh-Jl
for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 09:51:57 +0000
Received: by pdbci14 with SMTP id ci14so28953309pdb.2
for <bitcoin-development@lists.sourceforge.net>;
Fri, 19 Jun 2015 02:51:51 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.70.134.198 with SMTP id pm6mr30377273pdb.17.1434707510945;
Fri, 19 Jun 2015 02:51:50 -0700 (PDT)
Received: by 10.70.93.72 with HTTP; Fri, 19 Jun 2015 02:51:50 -0700 (PDT)
Date: Thu, 18 Jun 2015 23:51:50 -1000
Message-ID: <CAEz79PoDn+-aDkqSfPeQFUjYDEDEhSrJ2mFYcbitHBf4oADBSg@mail.gmail.com>
From: "Warren Togami Jr." <wtogami@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11346bb08bed380518dbdfe0
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(wtogami[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Z5sxo-0002Jh-Jl
Subject: [Bitcoin-development] Mailman incompatibility with DKIM ...
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 19 Jun 2015 09:51:57 -0000
--001a11346bb08bed380518dbdfe0
Content-Type: text/plain; charset=UTF-8
Both you and jgarzik experienced mail getting tossed into gmail's spam
folder thanks to DKIM... I am concerned that DKIM is too fragile and not
very compatible with mailing lists.
We already removed the footer because it was incompatible with DKIM
signing. Keeping the "[Bitcoin-dev] " prepend tag in subject is compatible
with DKIM header signing only if the poster manually prepends it in their
subject header.
I am already concerned that the lack of the Mailman footer will make it
hard to identify where exactly subscribers need to go to unsubscribe or
look at archives. Removing the subject tag might make DKIM enforcement
work a lot better, but I can easily see our obtuse subscribers as being
extra confused by this.
Opinions?
Warren
On Thu, Jun 18, 2015 at 11:38 PM, Arthur <arthur@powaaa.com> wrote:
> warren | bad_duck: try manually adding "[Bitcoin-dev] " to the beginning
> of the subject
>
> --
> Arthur
>
--001a11346bb08bed380518dbdfe0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Both you and jgarzik experienced mail getting tossed =
into gmail's spam folder thanks to DKIM... I am concerned that DKIM is =
too fragile and not very compatible with mailing lists.<br></div><div><br><=
/div>We already removed the footer because it was incompatible with DKIM si=
gning.=C2=A0 Keeping the "[Bitcoin-dev] " prepend tag in subject =
is compatible with DKIM header signing only if the poster manually prepends=
it in their subject header.<div><br></div><div>I am already concerned that=
the lack of the Mailman footer will make it hard to identify where exactly=
subscribers need to go to unsubscribe or look at archives.=C2=A0 Removing =
the subject tag might make DKIM enforcement work a lot better, but I can ea=
sily see our obtuse subscribers as being extra confused by this.</div><div>=
<br></div><div>Opinions?</div><div><br></div><div>Warren</div><div class=3D=
"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Jun 18, 2015 at 11:38 =
PM, Arthur <span dir=3D"ltr"><<a href=3D"mailto:arthur@powaaa.com" targe=
t=3D"_blank">arthur@powaaa.com</a>></span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><u></u><div><div style=3D"font-family:arial,sans-serif;font-s=
ize:13px">warren | bad_duck: try manually adding "[Bitcoin-dev] "=
to the beginning of the subject<br><br>--<br>Arthur</div></div>
</blockquote></div><br></div></div>
--001a11346bb08bed380518dbdfe0--
|
