[VoiceOps] [EXTERNAL] Re: Mailman 'Reply-To' munging (was: Re: 9-8-8 dialing [...])
David.Hiers at cdk.com
Wed Jul 20 10:56:18 EDT 2022
I’m not aware of any recent changes to the list config, but I’ll check.
The current “reply-to” behavior is the one generally recommended by the Mailman docs, which warn of weird email client behavior if you mess around with it. I’m not beyond messing around with it, just don’t want to make things worse.
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Carlos Alvarez via VoiceOps
Sent: Tuesday, July 19, 2022 4:30 PM
To: voiceops at voiceops.org
Subject: [EXTERNAL] Re: [VoiceOps] Mailman 'Reply-To' munging (was: Re: 9-8-8 dialing [...])
CAUTION: This email originated from outside of the CDK organization. Exercise caution when clicking links or opening attachments, especially from unknown senders.
If I do a reply on this list, it always puts the sender as the recipient, not the list. This is remarkably stupid. If I do a reply-all then it puts the list on CC and the sender in TO.
On Tue, Jul 19, 2022 at 1:03 AM Nathan Anderson via VoiceOps <voiceops at voiceops.org<mailto:voiceops at voiceops.org>> wrote:
Nathan Anderson wrote:
> (Quick off-topic note: did some setting on VoiceOps mailman get changed
> halfway through the morning? "From:" now shows voiceops list address
> instead of original sender's -- which I'm fine with -- but then
> "Reply-To" is getting added and set to sender. So I now have to add
> voiceops address to "To:" or "CC:" manually if I want my reply to go to
> the list. Not cool.)
Sounds to me like 'from_is_list' now == 'munged', and this is how Outlook
behaves in this situation.
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the VoiceOps