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 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
