Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gsUQ5-0004W2-2K for pgsql-www@arkaria.postgresql.org; Sat, 09 Feb 2019 15:19:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gsUQ3-0001wJ-HD for pgsql-www@arkaria.postgresql.org; Sat, 09 Feb 2019 15:19:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gsUQ3-0001wC-8f for pgsql-www@lists.postgresql.org; Sat, 09 Feb 2019 15:19:51 +0000 Received: from tamriel.snowman.net ([96.255.250.162]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gsUPw-0000GO-9L; Sat, 09 Feb 2019 15:19:49 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 52D995F79E; Sat, 9 Feb 2019 10:19:43 -0500 (EST) Date: Sat, 9 Feb 2019 10:19:43 -0500 From: Stephen Frost To: Magnus Hagander Cc: Alvaro Herrera , Tom Lane , Dimitri Fontaine , Andres Freund , "Jonathan S. Katz" , PostgreSQL WWW Subject: Re: mailing list redirect for bug numbers? Message-ID: <20190209151942.GJ6197@tamriel.snowman.net> References: <20190119144923.GQ2528@tamriel.snowman.net> <20190206164106.GA23132@alvherre.pgsql> <20190207114507.GD6197@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3CAnR4CLEnEWqRMR" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --3CAnR4CLEnEWqRMR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Magnus Hagander (magnus@hagander.net) wrote: > On Thu, Feb 7, 2019 at 12:45 PM Stephen Frost wrote: > > One thing I really don't want to do is make the moderators of some list > > like this the ones who have to make the decision about if a report is > > really a bug or not. For one thing, it's at least sometimes useful to > > have the question asked and answered for the archives, whatever it is, > > even if it isn't a bug. >=20 > Right, but that's a problem we *already* have. >=20 > We will have to keep assigning those bug ids. The idea is we need to block > pure spam. Just like moderators of the bug form and of the docs form have > to do that *today*. Except it's likely going ot be more if it is a public > email address. Sure, I don't have any issue with having a new system go through moderation in the same way that the webform submissions go through moderation today, to just filter out pure spam. Not sure why you think it'll be more spam than the amount we get to our other lists, but it doesn't seem like that matters all that much either way, it'll be whatever it ends up being. > The reason being that once we resend it from *our* address, it will > otherwise bypass all spam filters, and *our* addresses will start getting > penalized for the spam. Given that for this to work we have to change the > sender/from to be noreply@postgresql.org (or similar), like we do with do= cs > and bugs today. Right, we'd definitely need to have moderation in place to avoid having our servers sending out spam and getting penalized for it (I don't know that this is really all that different from the existing situation with our lists, since it's our servers and most email providers care a lot more about the server sending the spam than about what the From: address in the spam is...). Anyway, I think we agree here that we'd want this to be moderated, to avoid having our systems send out spam, either way, so the rest is likely moot. Thanks! Stephen --3CAnR4CLEnEWqRMR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJcXu+OAAoJEO1sijiDR2RV3y8P/R+CekqgjhJ2Xa+wjMpTRaux VvvFsmqp9ggQR8VmWTUq+e6v66AZrnPm2XHnHg5vnprKYwp4BrIQ1xKqRcjzDgbg xA95YaMxOWfUKUIUzupQiPFdiCpCbi0B3YKzsEAv9WqqUUoLGT2GzaxrnWYljfcr c2A1JjFLIVFYrCa7zIY5TDRbgsk6OMuf/Fe08R7onViWnoLhtD/1gJGaJfptoe6o vki4tVc2dYawXN38JOVvd6DeO9mmpfWg8sUHKL0v2LGwODaBmvCA+gGeiKX/ryu1 8NIViOmcObrAnt/Ik218C+WU+EsDbsGgsY1+VwkX+s/0Qf8EBHHLFj37/4GyBMkD c3DpHCzIIdJtBYzjr0spn7gug8D6BoreZGFO9zrFdAVNHpW+9GVcmK2e6Lx6QOzf YSKHXjmVsXj3ZM20f4sgKjY931CkbTOqI0fXP5batkyeWw3YLq6RivIkgUmPOvXv QUtgjAWnj6dU7J0TrzesqTx+KQFRYeygGxPjmQ+Qq1QsrFHYJ+MUqI1XGD3D/fDm ft2pAiXB5q3ZboVe9SEhGcggQD18q7gb9EQLAdImllZL8AL4yY32LkZICwPdCTrS tas1Z2oYm3LyV3znMxCDlsOfZ4ObiOD19hUewuN6tBqI3P+gLyGwhLcQF4s0awaV E8sXdXvSJfuKrxZ6WpKY =30lR -----END PGP SIGNATURE----- --3CAnR4CLEnEWqRMR--