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@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@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@voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops > _______________________________________________ > VoiceOps mailing list > VoiceOps@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/ _______________________________________________ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops