Hi, Mark. Thanks for the private email. I promise I won't abuse it. Here is the header. Note particularly the reply-to:Reply-To: [email protected], [email protected], Phil Muir <[email protected]> This was a direct copy-paste, & it's weird that the [email protected] address contains an uppercase letter. Do you have any idea what is occurring?
https://mail.google.com/mail/u/0/h/rzsloxyya12s/?th=156001d8e1dccb49v=om Delivered-To: [email protected] Received: by 10.37.22.2 with SMTP id 2csp1271120ybw; Mon, 18 Jul 2016 15:25:52 -0700 (PDT) X-Received: by 10.66.144.200 with SMTP id so8mr10577521pab.94.1468880752243; Mon, 18 Jul 2016 15:25:52 -0700 (PDT) Return-Path: <[email protected]> Received: from mailman.midimag-xt.org (mailman.midimag-xt.org. [107.170.199.86]) by mx.google.com with ESMTP id ro7si28933425pab.251.2016.07.18.15.25.51; Mon, 18 Jul 2016 15:25:52 -0700 (PDT) Received-SPF: pass (google.com: domain of [email protected] designates 107.170.199.86 as permitted sender) client-ip=107.170.199.86; Authentication-Results: mx.google.com; dkim=fail [email protected]; spf=pass (google.com: domain of [email protected] designates 107.170.199.86 as permitted sender) [email protected] Received: from mailman.midimag-xt.org (localhost [127.0.0.1]) by mailman.midimag-xt.org (Postfix) with ESMTP id 14E1412403B; Mon, 18 Jul 2016 15:25:51 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailman.midimag-xt.org; s=mailman; t=1468880751; bh=LWN5eghNrqijU7VjrNrEV2Wej3+KA03rqZ77M+Cv4+Y=; h=In-Reply-To:References:Date:To:Subject:From:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Sender:From; b=Qb2gdCszjPsfJU8z/Qy48U+sXvRUY6RetxvxhAlCa73r0XRKsH6S97bdXA+//He6w B9lYmU7pHWP5W32Mserx2bMFzrNYh1HzFFsJhvwzwaNtpDqe3ovPjsInb7/YKcQ3xI De0WpTiAar0u/+qEKajU3ZuwSSv2nfPR6aH5O0js= X-Original-To: [email protected] Delivered-To: [email protected] Received: from outbound44.dataflame.com (outbound44.dataflame.com [91.103.219.62]) by mailman.midimag-xt.org (Postfix) with ESMTPS id 726BF12402A for <[email protected]>; Mon, 18 Jul 2016 15:25:40 -0700 (MST) X-Virus-Scanned: by SpamTitan at dataflame.co.uk Received: from [2.216.153.142] (port=60675 helo=android-6c0a3f0408928b1b) by primrose.dataflame.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-SHA:256) (Exim 4.87) (envelope-from <[email protected]>) id 1bPGyg-002oKs-Lc for [email protected]; Mon, 18 Jul 2016 23:25:32 +0100 User-Agent: K-9 Mail for Android In-Reply-To: <CACiOLt=Z3Ys6kVp-CHhjt3yK-ViN-SbE3_vyeMxs8YsK6LeL=q...@mail.gmail.com> References: <cam+q2c6phm8da1txnkcyn2fy_ifbddh7gwvrnjm78mbdvfj...@mail.gmail.com> <CACiOLt=Z3Ys6kVp-CHhjt3yK-ViN-SbE3_vyeMxs8YsK6LeL=q...@mail.gmail.com> MIME-Version: 1.0 Date: Mon, 18 Jul 2016 23:25:31 +0100 To: [email protected] Message-ID: <[email protected]> X-OutGoing-Spam-Status: No, score=-2.6 X-Content-Filtered-By: Mailman/MimeDel 2.1.16 Subject: Re: [Midimag-ex] 1 last experiment X-BeenThere: [email protected] X-Mailman-Version: 2.1.16 Precedence: list From: Phil Muir via Midimag-ex <[email protected]> Reply-To: [email protected], [email protected], Phil Muir <[email protected]> List-Id: <midimag-ex.mailman.midimag-xt.org> List-Unsubscribe: <http://mailman.midimag-xt.org/cgi-bin/mailman/options/midimag-ex>, <mailto:[email protected]?subject=unsubscribe> List-Archive: <http://mailman.midimag-xt.org/cgi-bin/mailman/private/midimag-ex/> List-Post: <mailto:[email protected]> List-Help: <mailto:[email protected]?subject=help> List-Subscribe: <http://mailman.midimag-xt.org/cgi-bin/mailman/listinfo/midimag-ex>, <mailto:[email protected]?subject=subscribe> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Errors-To: [email protected] Sender: "Midimag-ex" <[email protected]> R290IHRoaXMgdGhyZWFkIGhlcmUgZnJvbSB0aGUgbGlzdC4gIEhpdCByZXBseS4KCk9uIDE4IEp1 bHkgMjAxNiAyMzoxNjo1MyBCU1QsIEtlaXRoIEhpbnRvbiB2aWEgTWlkaW1hZy1leCA8bWlkaW1h Zy1leEBtYWlsbWFuLm1pZGltYWcteHQub3JnPiB3cm90ZToKPk9rYXksIHJlc3BvbmRpbmcgdG8g dGhpcyB0byBzZWUgd2hhdCB5b3UgYWxsIGdldC4KPgo+SGF2ZSBmdW4sCj5LZWl0aAo+Cj5Qcy4K PkkgZGlkIG5vdCBoaXQgcmVwbHkgdG8gYWxsLCBzbyBsZXQncyBzZSBpZiBldmVyeWJvZHkgc2Vl cyB0aGlzIHJhbmRvbQo+bWVzc2FnZSBibG9iIHRoaW5neS4KPgo+T24gNy8xOC8xNiwgSmFja2ll IE1jQnJpZGUgdmlhIE1pZGltYWctZXgKPjxtaWRpbWFnLWV4QG1haWxtYW4ubWlkaW1hZy14dC5v cmc+IHdyb3RlOgo+PiBXZWxsIGxldCdzIHNlZSB3aGF0IHRoaXMgZG9lcy4KPj4KPj4gLS0KPj4g SmFja2llIE1jQnJpZGUKPj4gV2Vic2l0ZSBIb3N0aW5nLCBSZXBhaXIsICYgRGV2ZWxvcG1lbnQK Pj4gQXV0aG9yIG9mIHRoZSBVcGNvbWluZyBCb29rCj4+ICJNeSBTaXRlJ3MgQmVlbiBIYWNrZWQs IE5vdyB3aGF0PzogQSBHdWlkZSB0byBQcmV2ZW50aW5nIGFuZCBGaXhpbmcgYQo+PiBDb21wcm9t aXNlZCBXZWJzaXRlIgo+PiB3d3cuYnJpZ2h0ZXItdmlzaW9uLmNvbSBXaGVyZSBWaXNpb25hcmll cyAmIFRlY2hub2xvZ3kgVW5pdGUgZm9yIEdvb2QKPj4gX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX18KPj4gTWlkaW1hZy1leCBtYWlsaW5nIGxpc3QKPj4gTWlk aW1hZy1leEBtYWlsbWFuLm1pZGltYWcteHQub3JnCj4+IGh0dHA6Ly9tYWlsbWFuLm1pZGltYWct eHQub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taWRpbWFnLWV4Cj4+Cj5fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+TWlkaW1hZy1leCBtYWlsaW5n IGxpc3QKPk1pZGltYWctZXhAbWFpbG1hbi5taWRpbWFnLXh0Lm9yZwo+aHR0cDovL21haWxtYW4u bWlkaW1hZy14dC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pZGltYWctZXgKCi0tIApS ZWdhcmRzLApBY2Nlc3NpYmlsaXR5IFRyYWluaW5nClRlbGVwaG9uZTogVUsgKzQ0LTE3NDctMjI4 LTQ1OQpNb2JpbGU6IFVLICs0NC03OTY4LTEzNi0yNDYKRS1tYWlsOgppbmZvQGFjY2Vzc2liaWxp dHl0cmFpbmluZy5jby51awpVUkw6Cmh0dHA6Ly93d3cuYWNjZXNzaWJpbGl0eXRyYWluaW5nLmNv LnVrCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pZGlt YWctZXggbWFpbGluZyBsaXN0Ck1pZGltYWctZXhAbWFpbG1hbi5taWRpbWFnLXh0Lm9yZwpodHRw Oi8vbWFpbG1hbi5taWRpbWFnLXh0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlkaW1h Zy1leAo= On 7/18/16, Mark Sapiro <[email protected]> wrote: > I note you are telling me two different things in Comments #2 and #3. > > Comment #2 says > In addition to the list address & his address, the address that appears in > the email header as well is: > Accessibility at mailman dot midimag dash xt dot org > which is a thoroughly bogus address. > > which says there are 3 addresses in (I assume) Reply-To: of the post > from Mailman. > > Comment #3 says > the reply-to: header contains the list address &, instead of his email > address, there's an address Accessibility at mailman dot midimag dash xt dot > org instead of his actual email address. > > which says there are only 2 addresses in Reply-To: of the post from > Mailman. > > I'd like to see the raw headers of the mail from the list. If you don't > want to post them here, you can mail them to [email protected]. > > Here's an example of full headers of a mail to a list: > > >From [email protected] Mon Jul 18 22:57:00 2016 > Date: Mon, 18 Jul 2016 22:57:00 -0700 > From: Mark Sapiro <[email protected]> > To: [email protected] > Subject: Test mail > Message-ID: <[email protected]> > Reply-To: [email protected] > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > User-Agent: Mutt/1.5.24 (2015-08-30) > Status: RO > Content-Length: 147 > Lines: 4 > > > And the headers of the mail from the list > > >From [email protected] Mon Jul 18 22:57:14 2016 > Return-Path: <[email protected]> > X-Original-To: [email protected] > Delivered-To: [email protected] > Received: from [127.0.1.1] (localhost [127.0.0.1]) > by msapiro.net (Postfix) with ESMTP id E6AC234028D > for <[email protected]>; Mon, 18 Jul 2016 22:57:10 -0700 (PDT) > X-Original-To: [email protected] > Delivered-To: [email protected] > Received: by msapiro.net (Postfix, from userid 1000) > id DEC133402D7; Mon, 18 Jul 2016 22:57:00 -0700 (PDT) > Date: Mon, 18 Jul 2016 22:57:00 -0700 > To: [email protected] > Message-ID: <[email protected]> > MIME-Version: 1.0 > Content-Disposition: inline > User-Agent: Mutt/1.5.24 (2015-08-30) > X-msapiro-MailScanner: Found to be clean > X-msapiro-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, > score=0, > required 6, autolearn=not spam, > NO_RELAYS -0.00, URIBL_BLOCKED 0.00) > X-Spam-Status: No > Subject: [List1] Test mail > X-BeenThere: [email protected] > X-Mailman-Version: 2.1.22 > Precedence: list > List-Id: My List one <list1.msapiro.net> > List-Unsubscribe: <http://msapiro.net/mailman/options/list1>, > <mailto:[email protected]?subject=unsubscribe> > List-Archive: <http://msapiro.net/pipermail/list1/> > List-Post: <mailto:[email protected]> > List-Help: <mailto:[email protected]?subject=help> > List-Subscribe: <http://msapiro.net/mailman/listinfo/list1>, > <mailto:[email protected]?subject=subscribe> > From: Mark Sapiro via List1 <[email protected]> > Reply-To: [email protected], My List one <[email protected]> > Cc: Mark Sapiro <[email protected]> > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > Errors-To: [email protected] > Sender: List1 <[email protected]> > X-msapiro-MailScanner-ID: E6AC234028D.AFCF3 > X-msapiro-MailScanner: Found to be clean > X-msapiro-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, > score=-0.999, required 6, autolearn=not spam, ALL_TRUSTED -1.00, > URIBL_BLOCKED 0.00) > X-msapiro-MailScanner-From: [email protected] > X-Spam-Status: No > Status: O > Content-Length: 275 > Lines: 9 > > This is Mailman 2.1.22+, but I think the only difference from 2.1.16 is > the original From: would be added to Reply-To: instead of Cc: except the > address is already there because of the original Reply-To: and > first_strip_reply_to = No so it wouldn't be added a second time. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1604181 > > Title: > mangled reply-to: header when a reply-to: header exists > > Status in GNU Mailman: > Incomplete > > Bug description: > I'm trying to set my list up such that folks reply to the list, but can > also view a poster's email in order to reply personally if they desire. I've > set 'Reply-to:' to list, & I didn't strip the first 'reply-to:' header. When > someone has a reply-to: address set, I get 3 addresses--the list address, > the poster's address, & a mangled address that consists of the poster's > address prior to the @ sign & the fqdn of the list following it. So if my > list address is [email protected], & my poster w/the reply-to: > setting's email is [email protected], I'd get addresses as: > [email protected] > [email protected] (which there is no such address) & > [email protected]. > > I'm running Mailman 2.1.16. Has this perchance been fixed in > subsequent versions? > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions > -- Jackie McBride Website Hosting, Repair, & Development Author of the Upcoming Book "My Site's Been Hacked, Now what?: A Guide to Preventing and Fixing a Compromised Website" www.brighter-vision.com Where Visionaries & Technology Unite for Good -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions _______________________________________________ Mailman-coders mailing list [email protected] https://mail.python.org/mailman/listinfo/mailman-coders
