From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from bedivere.hansenpartnership.com (bedivere.hansenpartnership.com [66.63.167.143]) by mx.groups.io with SMTP id smtpd.web09.12290.1578672284425719561 for ; Fri, 10 Jan 2020 08:04:44 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@hansenpartnership.com header.s=20151216 header.b=aUq8FhDE; spf=pass (domain: hansenpartnership.com, ip: 66.63.167.143, mailfrom: james.bottomley@hansenpartnership.com) Received: from localhost (localhost [127.0.0.1]) by bedivere.hansenpartnership.com (Postfix) with ESMTP id 8D9C08EE0F5; Fri, 10 Jan 2020 08:04:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hansenpartnership.com; s=20151216; t=1578672280; bh=K2mfvNb1M7JAlsdXvg0PokIsH7H8Qx4qLzbYoWPAlkI=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=aUq8FhDEZgTaN8VNfpNca5n+hsmGk3ujRxUujJHRaU2dVkPUogCetun4Lxd3y5gAL bzPEXVKgo1gmGo+7MMVJ1lu0iUgCd9e4z4Jpo40AFmAzw/6gQbEizhh1WFMlWx3j8U a5AguzyqQ5yWzQtolcNz4XBm9Y8NYQbwA2c8Ad7k= Received: from bedivere.hansenpartnership.com ([127.0.0.1]) by localhost (bedivere.hansenpartnership.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3RediQul42iP; Fri, 10 Jan 2020 08:04:27 -0800 (PST) Received: from jarvis.lan (unknown [50.35.76.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bedivere.hansenpartnership.com (Postfix) with ESMTPSA id 4AFFF8EE0D2; Fri, 10 Jan 2020 08:04:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hansenpartnership.com; s=20151216; t=1578672262; bh=K2mfvNb1M7JAlsdXvg0PokIsH7H8Qx4qLzbYoWPAlkI=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=Q+4c+ZAWkeJwz+lQ1OBk3EhvMpGFh/I1yUwJ16rmxou50AGC/4cSthHFwnpYGgF30 iTeHuEWe0dHys8JPm+J5O+rHRWUW7r8b+ak4idFPJFdxZR8K4HeASM5eTw9Tpix0Yc BsitbLzKL5HTHmT1pd95pa24+tNdlo8rOt1QEYNc= Message-ID: <1578672256.3012.6.camel@HansenPartnership.com> Subject: Re: [edk2-devel] Interpretation of specification From: James Bottomley To: Laszlo Ersek , devel@edk2.groups.io Cc: ekhoruzhenko@absolute.com, Paulo Henrique Lacerda de Amorim Date: Fri, 10 Jan 2020 08:04:16 -0800 In-Reply-To: References: <6038.1578420793574513591@groups.io> <1578510817.3260.73.camel@HansenPartnership.com> <0353cfad-68cf-d5c6-3f36-b57e3bc6ff0a@redhat.com> <1578590422.3526.6.camel@HansenPartnership.com> X-Mailer: Evolution 3.26.6 Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Fri, 2020-01-10 at 11:55 +0100, Laszlo Ersek wrote: > Right, that's my understanding too -- fully open lists are not > supported on groups.io (and at least in the edk2 community, most > participants don't like fully open posting -- I happen to be a fan of > open posting, FWIW). Worse, for non-subscribers, the best that > groups.io offers is white-listing per *message*, and not per > *sender*. Yes, that's the most annoying feature of groups.io It can be worked around though: I've got an auto-reply on the moderator email using procmail that auto-approves every message held for moderation ... although I'm not sure that would work well on a higher traffic list. > > I also think the group rejected this out of hand because it's not > > in the moderation queue, but I think I've found the flag that holds > > non-member posts for moderation and thus allows them to be posted > > instead of rejected. > > Ugh, I didn't know that just holding messages for moderation took a > separate setting! Yes, apparently ... I remember having the same trouble with the openssl-tpm2-engine group. James