Mark, this list member lives in the UK, & it's late there now, but hopefully he'll do as I request & post w/his phone to the list at his earliest convenience. I do suspect it is something w/the phone reply-to: header, though I can't say I understand precisely what at this point. Seems as though we arrived at the same conclusion independently lol. Talk about a head-banger! Kind of interesting, though. I'm not familiar w/k-9--is this a user agent you've seen? It'll be interesting to see if this is an isolated event due to a misconfigured reply-to: header or if there are others who are experiencing anything remotely similar.
I had looked at Ubuntu & couldn't find anything more recent than the version I already have. But I'm not entirely certain that a later version would address something like this anyway. I'd have installed it from source if I thought it would've, truth be told. On 7/19/16, Mark Sapiro <[email protected]> wrote: > I hadn't seen > https://bugs.launchpad.net/mailman/+bug/1604181/comments/11 when I wrote > https://bugs.launchpad.net/mailman/+bug/1604181/comments/12, but I'm now > certain it's something in the Reply-To: header from the phone. > > -- > 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
