From: "Warren Togami Jr." <wtogami@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Mailman incompatibility with DKIM ...
Date: Fri, 19 Jun 2015 00:10:25 -1000 [thread overview]
Message-ID: <CAEz79Pr4ug8zyJ5bibCG3m0YD8gkBiXysWJsZDThTiwXsgd7YQ@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP3vut8uYWeeynLdwvSM56eXZZdgidaEgcvg1FNMye6P9w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 2905 bytes --]
next prev parent reply other threads:[~2015-06-19 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 9:51 Warren Togami Jr.
2015-06-19 9:56 ` Mike Hearn
2015-06-19 10:10 ` Warren Togami Jr. [this message]
2015-06-19 10:24 ` Mike Hearn
2015-06-19 10:38 ` Warren Togami Jr.
2015-06-19 10:49 ` Mike Hearn
2015-06-19 19:47 ` Adam Weiss
2015-06-19 20:44 ` Jeff Garzik
2015-06-20 18:43 ` Adam Weiss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEz79Pr4ug8zyJ5bibCG3m0YD8gkBiXysWJsZDThTiwXsgd7YQ@mail.gmail.com \
--to=wtogami@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox