From owner-freebsd-chromium@freebsd.org  Mon Aug 17 17:04:00 2020
Return-Path: <owner-freebsd-chromium@freebsd.org>
Delivered-To: freebsd-chromium@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id CA5873B7552
 for <freebsd-chromium@mailman.nyi.freebsd.org>;
 Mon, 17 Aug 2020 17:04:00 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3])
 by mx1.freebsd.org (Postfix) with ESMTP id 4BVgPD528jz3xBj
 for <freebsd-chromium@freebsd.org>; Mon, 17 Aug 2020 17:04:00 +0000 (UTC)
 (envelope-from pi@freebsd.org)
Received: by mailman.nyi.freebsd.org (Postfix)
 id ACA883B75AD; Mon, 17 Aug 2020 17:04:00 +0000 (UTC)
Delivered-To: chromium@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id AC74C3B7783
 for <chromium@mailman.nyi.freebsd.org>; Mon, 17 Aug 2020 17:04:00 +0000 (UTC)
 (envelope-from pi@freebsd.org)
Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4BVgPD0CMWz3xwN;
 Mon, 17 Aug 2020 17:03:59 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from pi by fc.opsec.eu with local (Exim 4.94 (FreeBSD))
 (envelope-from <pi@freebsd.org>)
 id 1k7iY2-000EN3-If; Mon, 17 Aug 2020 19:03:50 +0200
Date: Mon, 17 Aug 2020 19:03:50 +0200
From: Kurt Jaeger <pi@freebsd.org>
To: Joseph Mingrone <jrm@freebsd.org>
Cc: Postmaster Team <postmaster@freebsd.org>, chromium@freebsd.org,
 rene@freebsd.org
Subject: Re: Is there a problem with chromium@
Message-ID: <20200817170350.GA1265@fc.opsec.eu>
Reply-To: Postmaster Team <postmaster@freebsd.org>
References: <86h7t1fd87.fsf@phe.ftfl.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <86h7t1fd87.fsf@phe.ftfl.ca>
X-Rspamd-Queue-Id: 4BVgPD0CMWz3xwN
X-Spamd-Bar: ----
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[];
 ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]
X-BeenThere: freebsd-chromium@freebsd.org
X-Mailman-Version: 2.1.33
Precedence: list
List-Id: FreeBSD-specific Chromium issues <freebsd-chromium.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-chromium>, 
 <mailto:freebsd-chromium-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-chromium/>
List-Post: <mailto:freebsd-chromium@freebsd.org>
List-Help: <mailto:freebsd-chromium-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-chromium>, 
 <mailto:freebsd-chromium-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2020 17:04:00 -0000

Hi!

> Hello postmaster team,
> 
> Is there a problem with chromium@?

The list is configured for generic non-member reject.

That means: If bugzilla sends a mail to chromium, and the sender
is not subscribed (which I guess, is the case), then the mail is
rejected.

bugzilla-noreply@freebsd.org is the sender, I just tested it.

So I added bugzilla-noreply@freebsd.org with no-mail, so that mails
from bugzilla will be distributed to the list.

-- 
pi@FreeBSD.org         +49 171 3101372                  Now what ?