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

[Jackie McBride]

Hey Mark, I may have found something. It appears that when this poster
sends email via Outlook, everything is fine. But when he uses k-9 on
his Android, it's not. I've asked him to post again w/his phone to
confirm this. That could prove interesting--& perhaps even helpful.
I'll get back.

On 7/19/16, Jackie McBride <abletec at gmail.com> wrote:
> So far, I think it's this 1 person's, Mark, but I really need to do
> some more thorough checking. As mentioned in the last post, it's a
> Ubuntu distribution of Mailman.
>
> On 7/19/16, Mark Sapiro <mark at msapiro.net> wrote:
>> Again, is this only with posts from this one person or from everyone?
>>
>> In Mailman 2.1.16 with from_is_list = Mung From, first_strip_reply_to =
>> Yes and reply_to_list = This list, the posters original From: should be
>> added to Reply-To: (in the latest versions, it will be added to Cc: in
>> this case).
>>
>> And is this a distro's Mailman package, and if so, which?
>>
>> --
>> 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