diff options
author | Jeff Garzik <jgarzik@bitpay.com> | 2015-06-19 13:44:52 -0700 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2015-06-19 20:45:19 +0000 |
commit | bf7b02929467599477415b1e4ad7073f60c70025 (patch) | |
tree | d02471612bec6de2f9f8d760afb10ad01b5f08c9 | |
parent | c7f51deefa95f6796fc52d964c993607e8f52583 (diff) | |
download | pi-bitcoindev-bf7b02929467599477415b1e4ad7073f60c70025.tar.gz pi-bitcoindev-bf7b02929467599477415b1e4ad7073f60c70025.zip |
Re: [Bitcoin-development] Mailman incompatibility with DKIM ...
-rw-r--r-- | 9a/dc55cf076d188e176c6bfaaeca0199af22274f | 122 |
1 files changed, 122 insertions, 0 deletions
diff --git a/9a/dc55cf076d188e176c6bfaaeca0199af22274f b/9a/dc55cf076d188e176c6bfaaeca0199af22274f new file mode 100644 index 000000000..75e228bb9 --- /dev/null +++ b/9a/dc55cf076d188e176c6bfaaeca0199af22274f @@ -0,0 +1,122 @@ +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 <jgarzik@bitpay.com>) 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 <bitcoin-development@lists.sourceforge.net>; + 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: <CAFVoEQQF2TLTMpm0DvdXJV-mG3OA6ZU0=vbX1jZdKQ53=xwuOg@mail.gmail.com> +References: <CAEz79PoDn+-aDkqSfPeQFUjYDEDEhSrJ2mFYcbitHBf4oADBSg@mail.gmail.com> + <CANEZrP3vut8uYWeeynLdwvSM56eXZZdgidaEgcvg1FNMye6P9w@mail.gmail.com> + <CAEz79Pr4ug8zyJ5bibCG3m0YD8gkBiXysWJsZDThTiwXsgd7YQ@mail.gmail.com> + <CANEZrP1T3r=VDRBTM_jrm_g0BkQy_NZA40BPcZtVDq_0au6TKw@mail.gmail.com> + <CAEz79PriNzD18Es60=2Nkz5U6G=Ocrm9ezJmK0P1DirdP-vPkw@mail.gmail.com> + <CAFVoEQQF2TLTMpm0DvdXJV-mG3OA6ZU0=vbX1jZdKQ53=xwuOg@mail.gmail.com> +From: Jeff Garzik <jgarzik@bitpay.com> +Date: Fri, 19 Jun 2015 13:44:52 -0700 +Message-ID: <CAJHLa0OSNh3pJV6q7zkaiG=0Vg8qacvo1x8tdpXXnk5Je=9fyQ@mail.gmail.com> +To: Adam Weiss <adam@signal11.com> +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 <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 20:45:20 -0000 + +--001a113cea2632ad940518e50036 +Content-Type: text/plain; charset=UTF-8 + +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/ + +--001a113cea2632ad940518e50036 +Content-Type: text/html; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +<div dir=3D"ltr">On Fri, Jun 19, 2015 at 12:47 PM, Adam Weiss <span dir=3D"= +ltr"><<a href=3D"mailto:adam@signal11.com" target=3D"_blank">adam@signal= +11.com</a>></span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gm= +ail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor= +der-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Hi Warren,<div><= +br></div><div>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.</div><div></div></div></block= +quote></div><div class=3D"gmail_extra"><br></div>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.<br clear=3D"all"><div><br><= +/div>-- <br><div class=3D"gmail_signature">Jeff Garzik<br>Bitcoin core deve= +loper and open source evangelist<br>BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a hre= +f=3D"https://bitpay.com/" target=3D"_blank">https://bitpay.com/</a></div> +</div></div> + +--001a113cea2632ad940518e50036-- + + |