Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1juHnb-000516-66 for pgsql-www@arkaria.postgresql.org; Sat, 11 Jul 2020 15:52:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1juHnZ-00033k-Up for pgsql-www@arkaria.postgresql.org; Sat, 11 Jul 2020 15:52:21 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1juHnZ-0002wp-JH for pgsql-www@lists.postgresql.org; Sat, 11 Jul 2020 15:52:21 +0000 Received: from mail-lj1-x231.google.com ([2a00:1450:4864:20::231]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1juHnS-000539-1P for pgsql-www@lists.postgresql.org; Sat, 11 Jul 2020 15:52:19 +0000 Received: by mail-lj1-x231.google.com with SMTP id e4so9851646ljn.4 for ; Sat, 11 Jul 2020 08:52:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NHiZDgOAGR/ZCtu1ARqcFUbUdHIEEOoo82pgcriEmAA=; b=Lj8ENP9R5x3EwGyL0bNTj5864bJ2kpjszXEe6xsI6ThXZ+PWd7Tkh54I0czVfuiDJi 7LYGgR5pnfkTPYw1CQeRFcH1W6vr3hYfu9RQ47aEB2jmtV0upn4luYi97ITpJh/OS4hw FN2ryjN6Oh3tZdzAepzsKZ0R0XCndUhZ7nlHtihq5K10pNhM5jSDilUDcT2qcuIjykFs qqa4XsqKPAadDJyFqSvULkx/cM3Oj4nBFbVKs6YuThsZaVf/51aPgFG3VKRhfe4us8cB un+mmtcvWpZl1SBRHg+THpzSSr6lAJSnof4d8JvGtqgWMkaMkt3lPD1qfS6DpUgNGjW0 4c1g== 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:cc; bh=NHiZDgOAGR/ZCtu1ARqcFUbUdHIEEOoo82pgcriEmAA=; b=pl/3QNt/ukxOrPE13bQjtuJbXXro+H6hY2mg2Wuyjo8nEmOBLHvjnEUmIFjb0h6IiP U5DaOnrMI79Nf7bJaR+/ycKbxSVobRorWNcAJJ+SEN9rurVOuAjFyhBz0egtUJulrtoB XhwPR/aEFBusHPja2rgPdI2XsvuLRhWJAzAsMBprY3zz4tQCA1yWTZDdJUjP7Sd1FdrJ D5JIOHv98SyeoAVYFyqLOhOM/qevNVgS7/VYtHU0hA9bjar2rb9sV2RVRl7fuf0MyKGF tf9dTOVxsiPueCJZ4RmJ6/vQx5erKLLQL0F2lZmQUWb05L8wK8pa8m99Y0vOsuwWC/Im LOVA== X-Gm-Message-State: AOAM532VHRjozmd8jp7veZWcABj5niWZXMH73pjhMmwZa71XE3EyRn0L Xb8lwNyIWLsspsHLvVz8w3sLKtm5KuXCtrszlJOmNw== X-Google-Smtp-Source: ABdhPJyDEngr7A91k1ci1lzltXyopLeHLnuxRYW1sF+SEUjBa+PzD1YSls97iZ0LcSZDsPG0aywktScpoPMdAEGRwzs= X-Received: by 2002:a2e:2e07:: with SMTP id u7mr11714460lju.195.1594482731326; Sat, 11 Jul 2020 08:52:11 -0700 (PDT) MIME-Version: 1.0 References: <201901111833.hj64gsinrug7@alvherre.pgsql> <30749.1547241061@sss.pgh.pa.us> <20200522174838.GT3418@tamriel.snowman.net> <5006.1590174250@sss.pgh.pa.us> In-Reply-To: <5006.1590174250@sss.pgh.pa.us> From: Magnus Hagander Date: Sat, 11 Jul 2020 17:51:59 +0200 Message-ID: Subject: Re: Policy on cross-posting to multiple lists To: Tom Lane Cc: Stephen Frost , Alvaro Herrera , Andres Freund , Tatsuo Ishii , Dave Page , Dean Rasheed , PostgreSQL WWW Content-Type: multipart/alternative; boundary="000000000000cd34f205aa2c704d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000cd34f205aa2c704d Content-Type: text/plain; charset="UTF-8" On Fri, May 22, 2020 at 9:04 PM Tom Lane wrote: > Stephen Frost writes: > > At this point, I'd suggest we start moderating such cross-posts, letting > > moderators know that they should reject ones that aren't done with any > > thought to it with a request to the submitter to please pick a list > > instead of spamming them all. > > +1 ... the problem does seem to be getting worse lately. > > regards, tom lane > I finally managed to get around to pushing code into pglister that allows a "moderate" policy to be configured for CC handling on lists, and not just discard (it was originally decided we would never want this, but it's pretty clear the ideas around this has changed). We have a few internal lists set to discard at this point. And to be clear of the differences: * Allow -- any number of CCs are allowed * Moderate -- if more than one list is in to or cc, email gets moderated and sender gets a notice (with option to withdraw) * Discard -- if more than one list in to or cc, email gets discarded, and sender gets a notice If an email is cced between a list that's moderate and one that's discard, it gets discarded from the one list and moderated on the other one, and the sender gets two separate notices. If it's cced between two lists that are both in moderate, the sender gets one moderation notice for each of them. If it's only cced between lists with discard policy, sender gets a single notice. I haven't (yet) reconfigured any lists. But right now all our general lists have policy "allow". Should we more or less change all our public lists to be "moderate"? -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --000000000000cd34f205aa2c704d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, May 22, 2020 at 9:04 PM Tom L= ane <tgl@sss.pgh.pa.us> wrot= e:
Stephen Frost= <sfrost@snowman= .net> writes:
> At this point, I'd suggest we start moderating such cross-posts, l= etting
> moderators know that they should reject ones that aren't done with= any
> thought to it with a request to the submitter to please pick a list > instead of spamming them all.

+1 ... the problem does seem to be getting worse lately.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 regards, tom lane

I finally managed to get around to pushin= g code into pglister that allows a "moderate" policy to be config= ured for CC handling on lists, and not just discard (it was originally deci= ded we would never want this, but it's pretty clear the ideas around=C2= =A0this has changed).

We have a few internal lists set t= o discard at this point. And to be clear of the differences:
= * Allow -- any number of CCs are allowed
* Moderate -- if more th= an one list is in to or cc, email gets moderated and sender gets a notice (= with option to withdraw)
* Discard -- if more than one list in to= or cc, email gets discarded, and sender gets a notice

<= /div>
If an email is cced between a list that's moderate and one th= at's discard, it gets discarded from the one list and moderated on the = other one, and the sender gets two separate notices. If it's cced betwe= en two lists that are both in moderate, the sender gets one moderation noti= ce for each of them. If it's only cced between lists with discard polic= y, sender gets a single notice.

I haven't= (yet) reconfigured any lists. But right now all our general lists have pol= icy "allow". Should we more or less change all our public lists t= o be "moderate"?

--
=C2=A0Magnus H= agander
=C2=A0Me: https://www.hagander.net/
=C2=A0Work: https://www.redpill-linpro.com/
--000000000000cd34f205aa2c704d--