[Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists

[Jackie McBride]

Mark, if he just emails me, the header looks like:

Delivered-To: abletec at gmail.com
Received: by 10.37.22.2 with SMTP id 2csp1699972ybw;
        Tue, 19 Jul 2016 11:05:45 -0700 (PDT)
X-Received: by 10.28.138.18 with SMTP id m18mr6127346wmd.63.1468951545029;
        Tue, 19 Jul 2016 11:05:45 -0700 (PDT)
Return-Path: <info at accessibilitytraining.co.uk>
Received: from outbound37.dataflame.com (outbound37.dataflame.com.
[91.103.219.55])
        by mx.google.com with ESMTPS id
c184si21512657wmd.123.2016.07.19.11.05.44
        for <abletec at gmail.com>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Tue, 19 Jul 2016 11:05:44 -0700 (PDT)
Received-SPF: softfail (google.com: domain of transitioning
info at accessibilitytraining.co.uk does not designate 91.103.219.55 as
permitted sender) client-ip=91.103.219.55;
Authentication-Results: mx.google.com;
       spf=softfail (google.com: domain of transitioning
info at accessibilitytraining.co.uk does not designate 91.103.219.55 as
permitted sender) smtp.mailfrom=info at accessibilitytraining.co.uk
X-Virus-Scanned: by SpamTitan at dataflame.co.uk
Received: from [2.216.153.142] (port=65112 helo=phils15inchmac)
	by primrose.dataflame.com with esmtpa (Exim 4.87)
	(envelope-from <info at accessibilitytraining.co.uk>)
	id 1bPZOg-000i3A-OZ
	for abletec at gmail.com; Tue, 19 Jul 2016 19:05:37 +0100
Reply-To: <info at accessibilitytraining.co.uk>
From: "Phil Muir" <info at accessibilitytraining.co.uk>
To: "'Jackie McBride'" <abletec at gmail.com>
References: <CAM+Q2c6sDMhBJV5ZLkQ2aUO2d90AQUMMsEzSf4-hJafzdGDs+Q at mail.gmail.com>
In-Reply-To: <CAM+Q2c6sDMhBJV5ZLkQ2aUO2d90AQUMMsEzSf4-hJafzdGDs+Q at mail.gmail.com>
Subject: RE: mailman & midimag
Date: Tue, 19 Jul 2016 19:05:35 +0100
Organization: P J Muir Productions
Message-ID: <90AAC4C3777C4759866B77EAC830392C at phils15inchmac>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AdHh55cmAQuwq+ZrRRCmrWPI1V6WCgAAGE0g
X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17609
X-OutGoing-Spam-Status: No, score=-2.9

On 7/19/16, Jackie McBride <abletec at gmail.com> wrote:
> Hi, Mark.
> "Have you tried first_strip_reply_to = Yes?"
> Yes. But what it also does in most cases is to strip the poster's
> address, which is not what I want.
>
> "Is this a distribution package Mailman (if so, which one)?"
> Ubuntu.
>
> I'll ask him to bcc me & send it along. I'm going to test to see if I
> can duplicate this w/other reply-to: settings.
>
> On 7/19/16, Mark Sapiro <mark at msapiro.net> wrote:
>> Does this occur only with posts from this one person? Do you know what's
>> in his original Reply-To: (ask him to Bcc: you on his next post)?
>>
>> Have you tried first_strip_reply_to = Yes?
>>
>> Is this a distribution package Mailman (if so, which one)?
>>
>> If Mailman is installed from source, I recommend upgrading to 2.1.22 or
>> later.
>>
>> --
>> 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 mylist at mysub.domain.org, & my poster w/the reply-to:
>> setting's email is poster at somedomain.com, I'd get addresses as:
>>   mylist at mysub.domain.org
>>   poster at mysub.domain.org (which there is no such address) &
>>   poster at somedomain.com.
>>
>>   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
>


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