From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D335C138334 for ; Mon, 24 Sep 2018 20:16:51 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B2702E088F; Mon, 24 Sep 2018 20:16:49 +0000 (UTC) Received: from mail-ed1-f46.google.com (mail-ed1-f46.google.com [209.85.208.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 433BBE086F for ; Mon, 24 Sep 2018 20:16:49 +0000 (UTC) Received: by mail-ed1-f46.google.com with SMTP id y21-v6so5135674edr.2 for ; Mon, 24 Sep 2018 13:16:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=gB9iuDpIFb1KwGmdI5BB7+70qbQprMFUnIxpPxaPaqc=; b=VkR8kSodoLef0Y5rckSC9oiBjSOeJLczw4i0RV3QaN+Zot43rR26s1Y3bUWZ4ZcOtO c9CPKiWoqMCiOe5rHtj3+ypDXB+h2/Coq0CmUAeRsHk9CnNAFTIxYTQGV5oKW8e+QT++ qv78iezwnMRZNl4VP2jO7h+PUU2Qobs3V10R8eYG61xpUN17GKJjeJfMDYMo2njjtMEv x2+hsh7ikbI7iAQ5vssWr0pWy5EI37KUiI0KGvRV2zGWgUyqw8XV9RZVxkrE44CGmk7v srggWTd5qkgrQ2YcbK6xMTBz6dUMHXw8MYvoHDM6s+H++7E3Lt0didU00qy2H7zmyVJB pdRw== X-Gm-Message-State: ABuFfohrXUE8Kp9QEeelsG6cOfsUbUI5Qot5Ilvh58wDYMXlTL79uK5s IiYFHTC0jNvSK/orB6fpOJXUUHk4Gf9vCr/MbRGsSA== X-Google-Smtp-Source: ANB0VdbtsgFbUg60TbkAKyDOkOkhkbLlpTtf7D3JbdE7dwKMgR4qO8vF7SZ5o0rHvkrM69A+9SSXB8S7u0mmHfuShjo= X-Received: by 2002:a50:d512:: with SMTP id u18-v6mr19919598edi.291.1537820207535; Mon, 24 Sep 2018 13:16:47 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 References: In-Reply-To: From: Alec Warner Date: Mon, 24 Sep 2018 16:16:36 -0400 Message-ID: Subject: [gentoo-project] Re: Gentoo-dev whitelisting To: Gentoo Dev , gentoo-project Content-Type: multipart/alternative; boundary="00000000000032e73b0576a3ab2a" X-Archives-Salt: f07ac989-bc5b-46e1-abac-1642ad3cc9ce X-Archives-Hash: 447a3a5477fa1f6442d8cda1a5f12b75 --00000000000032e73b0576a3ab2a Content-Type: text/plain; charset="UTF-8" On Sun, Jun 10, 2018 at 3:21 PM Alec Warner wrote: > The whitelisting of gentoo-dev is now enabled. > There was a bug (since inception) where emails that should have been denied were allowed due to loose rule enforcement. The enforcement is more precise now, so if folks had their messages accepted before, but find themselves unable to post, you may need to be whitelisted. To be whitelisted please find a developer to vouch for you; instructions for developers are at https://wiki.gentoo.org/wiki/Project:Infrastructure/Mailing_Lists#Managing_the_Gentoo-Dev_whitelist Thanks, and sorry for any confusion this bug caused. -A > -A > > On Sun, May 13, 2018 at 2:57 PM, Alec Warner wrote: > >> Dear Gentoo Community, >> >> Gentoo-dev whitelisting[1][2] is nearly ready for deployment. The new >> posting guidelines to post on gentoo-dev@lists.gentoo.org the following: >> >> - You must be a member of the list to post. >> - You must be on the whitelist to post. >> >> The whitelist automatically whitelists all @gentoo.org addresses. >> Additions of addresses to the whitelist can be made by any developer. To >> modify the whitelist, please read this wiki page for instructions: >> >> >> https://wiki.gentoo.org/wiki/Project:Infrastructure/Mailing_Lists#Managing_the_Gentoo-Dev_whitelist >> >> [1] https://bugs.gentoo.org/650964 >> [2] The whitelist is not yet live, but I wanted to give folks an >> opportunity to populate the whitelist before enabling it; so have at it. >> >> >> > --00000000000032e73b0576a3ab2a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Jun 10, 2018 at 3:21 PM Alec Warner <antarus@gentoo.org> wrote:
The whitelisting of gento= o-dev is now enabled.

There was a bug= (since inception) where emails that should have been denied were allowed d= ue to loose rule enforcement.
The enforcement is more precise now= , so if folks had their messages accepted before, but find themselves unabl= e to post, you may need to be whitelisted.
To be whitelisted plea= se find a developer to vouch for you; instructions for developers are at=C2= =A0https://wiki.gentoo.org/wiki/Projec= t:Infrastructure/Mailing_Lists#Managing_the_Gentoo-Dev_whitelist
<= div>=C2=A0
Thanks, and sorry for any confusion this bug caused.

-A


-A

On Sun, May 13, 201= 8 at 2:57 PM, Alec Warner <antarus@gentoo.org> wrote:
Dear Gentoo Community,

Gentoo-dev whitelis= ting[1][2] is nearly ready for deployment. The new posting guidelines to po= st on=C2=A0gentoo-dev@lists.gentoo.org=C2=A0the following:


The whitelist automatically whitelists all @gentoo.org= =C2=A0addresses. Additions of addresses to the whitelist c= an be made by any developer. To modify the whitelist, please read this wiki= page for instructions:


[2] The whitelist is not yet live, but I wanted to give folks= an opportunity to populate the whitelist before enabling it; so have at it= .



--00000000000032e73b0576a3ab2a--