From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z63A7-0001T6-VW for bitcoin-development@lists.sourceforge.net; Fri, 19 Jun 2015 20:45:19 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.218.53 as permitted sender) client-ip=209.85.218.53; envelope-from=jgarzik@bitpay.com; helo=mail-oi0-f53.google.com; Received: from mail-oi0-f53.google.com ([209.85.218.53]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z63A6-00073a-UA for bitcoin-development@lists.sourceforge.net; Fri, 19 Jun 2015 20:45:19 +0000 Received: by oigx81 with SMTP id x81so88223142oig.1 for ; Fri, 19 Jun 2015 13:45:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=HQUn6saSzQd0XD1bb0dUhe7KITMWFQ6vAky8yOYFtwA=; b=gj00Afyb8S6lT0J13grNGi8eubRcO1b7nIWshoBabePsV9nxgxs2omV03yOnoKnVgg s7yfT1iR3TqPS35GloInUhAReoFuPzybL1CoJjNYQbaKvhKWFeFB5gMvj7qAAThYsufC HTxde2kFo6jKb0MYA9zIdlLrpdtxF9XQ5GS/4uTrp3QhI8R3esgksF/lRBQmC4zsK/KV KCYltvLvhkm0Ka9KrEMq5cRaTP9hs/NjTXby9zRiWtUuHMuz6/vpuf4pyqAP+2YFXB2w pGl+yt2CPMzwn+zD16tVfA+68NDcfM6U32X5kTOlPsp43ee4Q5t+/sqqACI7QNbuS5Id vETw== X-Gm-Message-State: ALoCoQkZAlCqEDUZ3wAQ0x6jT4PoGnG4f1Z3vnKX8RvCbQtrfr059uOXfsVo/kn6wLa5OMamtE8e X-Received: by 10.202.55.7 with SMTP id e7mr14320501oia.56.1434746713440; Fri, 19 Jun 2015 13:45:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.108.149 with HTTP; Fri, 19 Jun 2015 13:44:52 -0700 (PDT) In-Reply-To: References: From: Jeff Garzik Date: Fri, 19 Jun 2015 13:44:52 -0700 Message-ID: To: Adam Weiss Content-Type: multipart/alternative; boundary=001a113cea2632ad940518e50036 X-Spam-Score: -0.5 (/) 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 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 0.1 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1Z63A6-00073a-UA Cc: Bitcoin Dev 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jun 2015 20:45:20 -0000 --001a113cea2632ad940518e50036 Content-Type: text/plain; charset=UTF-8 On Fri, Jun 19, 2015 at 12:47 PM, Adam Weiss 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/ --001a113cea2632ad940518e50036 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Fri, Jun 19, 2015 at 12:47 PM, Adam Weiss <adam@signal= 11.com> wrote:
Hi Warren,
<= br>
If you set dmarc_moderation_action to "Munge from",= the list will detect when someone posts from a domain that publishes a req= uest for strict signature checking for all mails originating from it (in DN= S) and rewrite the envelope-from to the list's address.=C2=A0 Reply-to = will be added and set to the original sender.

That seems to change Reply= behavior for those recipients?=C2=A0 It would seem to accidentally direct = mail intended to DKIM-user + list to DKIM-user.

<= /div>--
Jeff Garzik
Bitcoin core deve= loper and open source evangelist
BitPay, Inc. =C2=A0 =C2=A0 =C2=A0https://bitpay.com/
--001a113cea2632ad940518e50036--