Mailman 'Reply-To' munging (was: Re: 9-8-8 dialing [...])
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.)
$%@#$%!#$ https://mail.python.org/pipermail/mailman-users/2014-August/077673.html Sounds to me like 'from_is_list' now == 'munged', and this is how Outlook behaves in this situation. Rrrrgh, -- Nathan
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> 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.)
$%@#$%!#$
https://mail.python.org/pipermail/mailman-users/2014-August/077673.html
Sounds to me like 'from_is_list' now == 'munged', and this is how Outlook behaves in this situation.
Rrrrgh,
-- Nathan
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Indeed. The default destination of a reply should be the list, which is accomplished by the following Mailman config options: from_is_list = 0 reply_goes_to_list = 1 ? Alex
On Jul 19, 2022, at 7:29 PM, Carlos Alvarez via VoiceOps <voiceops at voiceops.org> wrote:
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> 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.)
$%@#$%!#$
https://mail.python.org/pipermail/mailman-users/2014-August/077673.html
Sounds to me like 'from_is_list' now == 'munged', and this is how Outlook behaves in this situation.
Rrrrgh,
-- Nathan
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Hi, 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. Thanks, David 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.)
$%@#$%!#$ https://mail.python.org/pipermail/mailman-users/2014-August/077673.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.python.org_pipermail_mailman-2Dusers_2014-2DAugust_077673.html&d=DwMFaQ&c=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc&r=-GzOCp0ppLaBQPFaZ7lZ4bUUBQxpFBukitRP75oaRdQ&m=aDhfQpGytZSGJYtPCZjJvd1wPTHsG2CgTdUxzN12zZmLZYzmWoUAWvkPLFYUrZ9Q&s=dEfdgZvMsHphycL7e4mQ3Lhr6wDiFoxcz0GsXXqP8wU&e=> Sounds to me like 'from_is_list' now == 'munged', and this is how Outlook behaves in this situation. Rrrrgh, -- Nathan _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_voiceops&d=DwMFaQ&c=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc&r=-GzOCp0ppLaBQPFaZ7lZ4bUUBQxpFBukitRP75oaRdQ&m=aDhfQpGytZSGJYtPCZjJvd1wPTHsG2CgTdUxzN12zZmLZYzmWoUAWvkPLFYUrZ9Q&s=eIS5bzlf8JC5ieP7y0ivcKbRWWTiWVGjuXwWmneO42w&e=>
Odd recommendation. I've never been on a list with this behavior. (Or more precisely, not since the 90s when bandwidth mattered and everyone was trying to conserve it and reduce "fluff.) Since I'm on two other busy Mailman lists that have the reply-to-list behavior, I can say I've seen it work fine. And just now, I almost hit send before changing who I'm replying to. I'd appreciate the change. On Wed, Jul 20, 2022 at 7:56 AM Hiers, David <David.Hiers at cdk.com> wrote:
Hi,
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.
Thanks,
David
*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> 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.)
$%@#$%!#$
https://mail.python.org/pipermail/mailman-users/2014-August/077673.html <https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.python.org_piperma...>
Sounds to me like 'from_is_list' now == 'munged', and this is how Outlook behaves in this situation.
Rrrrgh,
-- Nathan
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops <https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman...>
Well, let?s give it a whirl and see what happens. I?ll let everyone know when the change has been made. Thanks, David From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Carlos Alvarez via VoiceOps Sent: Wednesday, July 20, 2022 8:32 AM To: voiceops at voiceops.org Subject: Re: [VoiceOps] [EXTERNAL] Re: Mailman 'Reply-To' munging (was: Re: 9-8-8 dialing [...]) Odd recommendation. I've never been on a list with this behavior. (Or more precisely, not since the 90s when bandwidth mattered and everyone was trying to conserve it and reduce "fluff.) Since I'm on two other busy Mailman lists that have the reply-to-list behavior, I can say I've seen it work fine. And just now, I almost hit send before changing who I'm replying to. I'd appreciate the change. On Wed, Jul 20, 2022 at 7:56 AM Hiers, David <David.Hiers at cdk.com<mailto:David.Hiers at cdk.com>> wrote: Hi, 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. Thanks, David From: VoiceOps <voiceops-bounces at voiceops.org<mailto: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<mailto: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.)
$%@#$%!#$ https://mail.python.org/pipermail/mailman-users/2014-August/077673.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.python.org_pipermail_mailman-2Dusers_2014-2DAugust_077673.html&d=DwMFaQ&c=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc&r=-GzOCp0ppLaBQPFaZ7lZ4bUUBQxpFBukitRP75oaRdQ&m=aDhfQpGytZSGJYtPCZjJvd1wPTHsG2CgTdUxzN12zZmLZYzmWoUAWvkPLFYUrZ9Q&s=dEfdgZvMsHphycL7e4mQ3Lhr6wDiFoxcz0GsXXqP8wU&e=> Sounds to me like 'from_is_list' now == 'munged', and this is how Outlook behaves in this situation. Rrrrgh, -- Nathan _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_voiceops&d=DwMFaQ&c=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc&r=-GzOCp0ppLaBQPFaZ7lZ4bUUBQxpFBukitRP75oaRdQ&m=aDhfQpGytZSGJYtPCZjJvd1wPTHsG2CgTdUxzN12zZmLZYzmWoUAWvkPLFYUrZ9Q&s=eIS5bzlf8JC5ieP7y0ivcKbRWWTiWVGjuXwWmneO42w&e=>
participants (4)
-
abalashov＠evaristesys.com -
caalvarez＠gmail.com -
David.Hiers＠cdk.com -
nathana＠fsr.com