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
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <wtogami@gmail.com>) id 1Z5tFo-00049m-NC
for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 10:10:32 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.54 as permitted sender)
client-ip=209.85.220.54; envelope-from=wtogami@gmail.com;
helo=mail-pa0-f54.google.com;
Received: from mail-pa0-f54.google.com ([209.85.220.54])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z5tFm-000514-Vz
for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 10:10:32 +0000
Received: by padev16 with SMTP id ev16so82478110pad.0
for <bitcoin-development@lists.sourceforge.net>;
Fri, 19 Jun 2015 03:10:25 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.66.118.166 with SMTP id kn6mr30042982pab.93.1434708625331;
Fri, 19 Jun 2015 03:10:25 -0700 (PDT)
Received: by 10.70.93.72 with HTTP; Fri, 19 Jun 2015 03:10:25 -0700 (PDT)
In-Reply-To: <CANEZrP3vut8uYWeeynLdwvSM56eXZZdgidaEgcvg1FNMye6P9w@mail.gmail.com>
References: <CAEz79PoDn+-aDkqSfPeQFUjYDEDEhSrJ2mFYcbitHBf4oADBSg@mail.gmail.com>
<CANEZrP3vut8uYWeeynLdwvSM56eXZZdgidaEgcvg1FNMye6P9w@mail.gmail.com>
Date: Fri, 19 Jun 2015 00:10:25 -1000
Message-ID: <CAEz79Pr4ug8zyJ5bibCG3m0YD8gkBiXysWJsZDThTiwXsgd7YQ@mail.gmail.com>
From: "Warren Togami Jr." <wtogami@gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=e89a8ffbaba7f81a6a0518dc216d
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: 1Z5tFm-000514-Vz
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [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 10:10:32 -0000
--e89a8ffbaba7f81a6a0518dc216d
Content-Type: text/plain; charset=UTF-8
On Thu, Jun 18, 2015 at 11:56 PM, Mike Hearn <mike@plan99.net> wrote:
> 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 still see footers being added to this list by SourceForge?
>
The new list currently has footers removed during testing. I am not
pleased with the need to remove the subject tag and footer to be more
compatible with DKIM users.
>
>
>> Opinions?
>>
>
> I've asked Jeff to not use his @bitpay.com account for now.
>
>
I'm guessing DKIM enforcement is not very common because of issues like
this?
It seems that Sourceforge silently drops DKIM enforced mail like
jgarzik's. LF seems to pass along their mail but mangles the header/body
and makes DKIM verification fail, which causes gmail to toss it into the
spam folder. I think this behavior is slightly worse than Sourceforge
because it makes the poster think their message was successfully sent (it
is in the archive), but many subscribers never see it due to the spam
binning.
I don't see any good solution to this except an auto-reject for DKIM
enforced domain postings. Yes this is rather terrible, but the instant
rejection is vastly better than Sourceforge silently dropping the post or
LF getting stuck in spam filters.
We should also auto-reject any other reason for mail getting stuck in the
moderation queue like including non-subscribers. I considered
auto-rejecting spam too, but that could go horribly wrong as a false From
address could make the Mailman server into a spammer itself. We may have
no choice but to silently drop spam for that reason.
Warren
--e89a8ffbaba7f81a6a0518dc216d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Jun 18, 2015 at 11:56 PM, Mike Hearn <span dir=3D"ltr"><<a href=3D"m=
ailto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>></span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_=
extra"><div class=3D"gmail_quote"><span class=3D""><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"><div dir=3D"ltr">We already removed the footer because it was incomp=
atible with DKIM signing.=C2=A0 Keeping the "[Bitcoin-dev] " prep=
end tag in subject is compatible with DKIM header signing only if the poste=
r manually prepends it in their subject header.</div></blockquote><div><br>=
</div></span><div>I still see footers being added to this list by SourceFor=
ge?</div></div></div></div></blockquote><div><br></div><div>The new list cu=
rrently has footers removed during testing.=C2=A0 I am not pleased with the=
need to remove the subject tag and footer to be more compatible with DKIM =
users.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr=
"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div>=C2=A0</div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Opinions?<br></div></div=
></blockquote><div><br></div><div>I've asked Jeff to not use his @<a hr=
ef=3D"http://bitpay.com" target=3D"_blank">bitpay.com</a> account for now.<=
/div><div><br></div></div></div></div></blockquote><div><br></div><div>I=
9;m guessing DKIM enforcement is not very common because of issues like thi=
s?</div><div><br></div><div>It seems that Sourceforge silently drops DKIM e=
nforced mail like jgarzik's.=C2=A0 LF seems to pass along their mail bu=
t mangles the header/body and makes DKIM verification fail, which causes gm=
ail to toss it into the spam folder.=C2=A0 I think this behavior is slightl=
y worse than Sourceforge because it makes the poster think their message wa=
s successfully sent (it is in the archive), but many subscribers never see =
it due to the spam binning.</div><div><br></div><div>I don't see any go=
od solution to this except an auto-reject for DKIM enforced domain postings=
.=C2=A0 Yes this is rather terrible, but the instant rejection is vastly be=
tter than Sourceforge silently dropping the post or LF getting stuck in spa=
m filters.</div><div><br></div><div>We should also auto-reject any other re=
ason for mail getting stuck in the moderation queue like including non-subs=
cribers.=C2=A0 I considered auto-rejecting spam too, but that could go horr=
ibly wrong as a false From address could make the Mailman server into a spa=
mmer itself.=C2=A0 We may have no choice but to silently drop spam for that=
reason.</div><div><br></div><div>Warren</div></div></div></div>
--e89a8ffbaba7f81a6a0518dc216d--
|
