On Mon, Mar 13, 2017 at 2:04 AM, Michel Dänzer <mic...@daenzer.net> wrote: > On 03/03/17 11:53 AM, Michel Dänzer wrote: >> On 03/03/17 03:38 AM, Matt Turner wrote: >>> On Wed, Mar 1, 2017 at 7:44 PM, Michel Dänzer <mic...@daenzer.net> wrote: >>>> P.S. It would be better to put the mesa-announce list only in Bcc on >>>> this kind of e-mails, to prevent accidental followups there. Reply-to: >>>> mesa-dev seems useless for that. >>> >>> GMail seems to ignore Reply-to. >> >> That would be shocking, though not entirely surprising. Anyway, the >> issue with Reply-To isn't limited to gmail. Reply-To merely replaces the >> original message's From address in the followup, any mailer will still >> include other recipients (with reply-to-all or similar). >> >> >>> Putting mesa-announce@ in Bcc seems like the wrong thing to do. >> >> Why? > > Still curious why you think it's wrong.
Oh, sorry. I missed the reply. I don't think it should be necessary. I'm on multiple *-announce lists, and this is the only one that has this problem. I think it's a misconfiguration of mesa-announce@ to not be a moderated list. I think Bcc'ing also means my gmail filters wouldn't know it came from the announce list. >>> mesa-announce@ should just be moderated, like xorg-announce@ is. >> >> That probably makes sense. Adam, Daniel, is this implemented in >> xorg-announce via the "emergency" option, or something else? > > Since I haven't heard back, I've enabled this option for the > mesa-announce list. Let's see how it goes. Thank you! >> BTW, in that case it might be good to have more volunteers to process >> the moderation queue. It's really easy with the listadmin tool. > > Any takers? Yeah, I'm happy to help. What do I need to do to get started? _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
