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 1ghgIJ-0002rY-6J for pgsql-www@arkaria.postgresql.org; Thu, 10 Jan 2019 19:47:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ghgIG-0000PY-V7 for pgsql-www@arkaria.postgresql.org; Thu, 10 Jan 2019 19:47:08 +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 1ghgIG-0000PQ-Je for pgsql-www@lists.postgresql.org; Thu, 10 Jan 2019 19:47:08 +0000 Received: from mail-lf1-x132.google.com ([2a00:1450:4864:20::132]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ghgI9-0007gt-CH for pgsql-www@lists.postgresql.org; Thu, 10 Jan 2019 19:47:07 +0000 Received: by mail-lf1-x132.google.com with SMTP id n18so9177463lfh.6 for ; Thu, 10 Jan 2019 11:47:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zyGPR/LTJ21I4yv+8F50PZz4k//gsJqlV4MsjgoehdM=; b=LrXlSrixjqg6d6MJ7n8pBJV/50mHijXnDo2iqMs5+dPY3+KsWT1bBzVYXkvKmf9vWH k14/NeuiQ4GNEV2YoGeKkMrQoS7vf+V2iDDRE359lJDgfsnCgMo3QPIERitmdU95gVvb 4/a/0kqJDIJPF6TY+s+0kGuJuFaE/7UfEiJMWdFvAjgOeybWYO8e1zrXG9aMM6cEbaeU 54wzyEx/RTKyBsOtpCAv3anoIjadMCfsWuRGCxM6HesEtXWQ7RPvYlJOu86f5rkfzA2u kITs+gSncJh3W0GrRSzMotTCZ/JuWJSpuen2fONb2JKV0UyF/7uBIVU+aMjS5PE5s3+O W52w== 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=zyGPR/LTJ21I4yv+8F50PZz4k//gsJqlV4MsjgoehdM=; b=XaNuIpVwWlIWMGQFGvW6vY3HG33OIhEyhwPkssNw8n3LL5PzJZIIeYqltiC9C2mjFV DA7vMtJxEkj5+3z3Z+B1A7Fpk6i14hn8K0gsic9URM7WB3lwk7xLO4mE4y/Dns2DG4Nx //fbTnUv2UkvuSiW6du4weRx/cGMIn4jSTV88Um0+lPkfGvSMGUzLhxJOq1P4Z0rli8x 7bCPm2j+3Vh3v4BGmEfqBLeGFJ6hAJr9IGoCEpz0DolGi2RyjQIn8cjDrNDyC8+D9tw0 wKSiBikSrpDlZ+p1kcx4WaKffZ8nMrRuFh4IPEs8Q0xXTsdQdUdhhfnfDtWJXyCEEUOI NlDA== X-Gm-Message-State: AJcUukeDAMb2Q7N1aKibE9EsgRyhsRQlQGLCk5ZV8NlL1ntjQGPM7WLs +e2ASUDu2IKSN4xd5WeOsNiJin6bSuyYw47j6jI= X-Google-Smtp-Source: ALg8bN65lDRAjgjDfg2n9pWv2LkUCUTu+BQc6HOvTus4OqZbv/hMAwIGUMPNUCAqwSSBneabY4enAFmJi1QEoiBR/Ws= X-Received: by 2002:a19:9508:: with SMTP id x8mr6777965lfd.112.1547149618134; Thu, 10 Jan 2019 11:46:58 -0800 (PST) MIME-Version: 1.0 References: <20190110171835.GP2528@tamriel.snowman.net> In-Reply-To: <20190110171835.GP2528@tamriel.snowman.net> From: Robert Haas Date: Thu, 10 Jan 2019 14:46:46 -0500 Message-ID: Subject: Re: Policy on cross-posting to multiple lists To: Stephen Frost Cc: Dean Rasheed , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, Jan 10, 2019 at 12:18 PM Stephen Frost wrote: > Are there concerns about the BCC restriction? One thing people sometimes do when something is posted to the wrong list is (1) reply, (2) explain in the reply that the message was posted to the wrong pace, (3) move the original list from Cc into Bcc, and (4) add the correct list into Cc. That has the advantage that people on the original list can see that someone replied (which avoids duplicate replies by different people) and know where to go to find the rest of the discussion if they want to see it. I think the idea of allowing 2 lists but not >2 is probably a good one. Also, it might be good to be more permissive for, say, people who have successfully posted at least 1000 emails to the lists. Such people presumably are less likely to do abusive things, and more likely to care about and heed any correction given to them. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company