From: Adam Weiss <adam@signal11•com>
To: Jeff Garzik <jgarzik@bitpay•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Mailman incompatibility with DKIM ...
Date: Sat, 20 Jun 2015 14:43:31 -0400 [thread overview]
Message-ID: <CAFVoEQRtSSUYROxTHCBXam08D5rTUW-mrtrr7L4jx4rMQSOLGw@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0OSNh3pJV6q7zkaiG=0Vg8qacvo1x8tdpXXnk5Je=9fyQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]
It changes the mechanics at least. A quick glance at RFC(2)822 makes it
clear that this is a pretty weakly specified behavior and is somewhat of an
edge case. However, rewriting the envelopes has become somewhat prevalent
since strict DMARC has been adopted and I suspect that most recent MUAs
will handle it well. I know that at least with gmail it works as I would
expect. (Makes sense considering that this is how Google Groups handles
the problem.)
In any event, I really think it's worth a shot since having the subject and
footer tags is valuable. If it turns out to be problematic, it's not the
end of the world and things could be easily switched to go the lkml route...
--adam
On Fri, Jun 19, 2015 at 4:44 PM, Jeff Garzik <jgarzik@bitpay•com> wrote:
> On Fri, Jun 19, 2015 at 12:47 PM, Adam Weiss <adam@signal11•com> wrote:
>
>> Hi Warren,
>>
>> If you set dmarc_moderation_action to "Munge from", the list will detect
>> when someone posts from a domain that publishes a request for strict
>> signature checking for all mails originating from it (in DNS) and rewrite
>> the envelope-from to the list's address. Reply-to will be added and set to
>> the original sender.
>>
>
> That seems to change Reply behavior for those recipients? It would seem
> to accidentally direct mail intended to DKIM-user + list to DKIM-user.
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
[-- Attachment #2: Type: text/html, Size: 2378 bytes --]
prev parent reply other threads:[~2015-06-20 18:43 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.
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 [this message]
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=CAFVoEQRtSSUYROxTHCBXam08D5rTUW-mrtrr7L4jx4rMQSOLGw@mail.gmail.com \
--to=adam@signal11$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@bitpay$(echo .)com \
/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