From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS11403 64.147.123.0/24 X-Spam-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id CBDEB1F4BD for ; Mon, 7 Oct 2019 22:14:09 +0000 (UTC) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 07512573 for ; Mon, 7 Oct 2019 18:14:08 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 07 Oct 2019 18:14:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alyssa.is; h= from:to:subject:date:message-id:mime-version:content-type; s= fm1; bh=6s1sXuQcNu+oJQ0vPBpYpRnQ1VgmT0njKM1JyRiT2qk=; b=Og0GKRpT Mblee+R08BSOnNWUY47G7D6/+mYdNZt7e2zfyyj0vpYh+25oRZiRYPp7WcNKI5al M1lIXi5vej9JgThGiToMd0dBUgzh+gB8Xo7LIO2Bt3RNE7bFXWt+euLlai5SQJ7f 337nE4jRKVn1T6TokoBoHViTDG5v9RQk0i+GU9vR8+pr3zdxUQnIHps7qTM2he6A urGLU5yy7sNIVZ5ViUKl/oEbgBbquZ9JkGOf02orBB1+8WAK9YzubwU+wggHU7sr SC/RQm0FLi5Rmvm4VL4YH6Mr781LYAga7yEHLnGQCinGAC1IjUKAM9eLvgmO37Z/ eo31ZGsVXye1ZA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=6s1sXuQcNu+oJQ0vPBpYpRnQ1VgmT 0njKM1JyRiT2qk=; b=RmAj9jaN8iPHiroZCSiD1Yf6cghqht5WEsGwoXqfPAiEo dlbIUIZ3JGzSyu7zLB1P6wlF6gJ/YeyzhSDvlyeYXVQcf/GObmZVC24KZQG/PxEO YjJ90r5bH+DMGS+RacM63y2Z5R+emmS0lwyIF5zklL0SsLxRCMeaXEAUVqo7iGNB mybNcGqmt5EUJEYSSaXbP8eAA3D6s3nvtQFLe6UESGeVey3RJsoRTXHspmtvqx2z PrTKg20xol4Rb4LG4WAiCjaV2I76QU+Fz+EnBH1fmXIohQ/763+5AZgGfEAo/jAC y66F3ndd1axTLPlJ0jDSrtC+2muJsYN30NftcIHXQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrheekgddtiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfggtgesghdtreertddttd enucfhrhhomheptehlhihsshgrucftohhsshcuoehhihesrghlhihsshgrrdhisheqnecu kfhppedujeeirdduvddruddtjedrudefvdenucfrrghrrghmpehmrghilhhfrhhomhephh hisegrlhihshhsrgdrihhsnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from localhost (unknown [176.12.107.132]) by mail.messagingengine.com (Postfix) with ESMTPA id C8A798005C for ; Mon, 7 Oct 2019 18:14:07 -0400 (EDT) From: Alyssa Ross To: meta@public-inbox.org Subject: Do I need multiple publicinbox..address values? Date: Mon, 07 Oct 2019 22:13:57 +0000 Message-ID: <87imp05hlm.fsf@alyssa.is> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" List-Id: --=-=-= Content-Type: text/plain Suppose I have a mailing list, foo-discuss@example.org, and a public-inbox set up, subscribed to that mailing list, that is subscribed to that list as public-inbox+foo-discuss@example.org, where my MTA delivers to public-inbox using public-inbox-mda. In this case, mail will be To: foo-discuss@example.org, but RCPT TO (and therefore ORIGINAL_RECIPIENT) public-inbox+foo-discuss@example.org. In my testing, public-inbox requires *both* the To: header and ORIGINAL_RECIPIENT to match publicinbox..address. But, public-inbox-config(7) has this to say for publicinbox..address: > The email address of the public-inbox. May be specified > more than once for merging multiple mailing lists (or migrating > to new addresses). Nothing in this suggests to me that I would need to set it more than once for my simple use case. So my question is, am I overcomplicating this -- should I be able to set a single value for publicinbox..address that will get my public-inbox to accept mail from the list? Or, alternatively, should a sentence be added to that description explaining that multiple addresses will also be required for the case where public-inbox is subscribed itself to a mailing list? --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEH9wgcxqlHM/ARR3h+dvtSFmyccAFAl2buKgACgkQ+dvtSFmy ccDjnBAApcJcO0rMIYtuoGgvWTNzzsmeRj5td5/puyLGix604RP2mJRkJZcPI6jY y3eOZBUn17bndTR6vopZZcrudRuLaobBTAeU4odUMNFbgPn1Th75PSBbof4Dxm6E 5hB11xmgJl7j/TMI7fXfZXTYsinIikMBQsodX9veWslEaNw3vntA4k9+T9HfXrJb +t86Ni6C4TXiHqKyXUKosQ6sjTqubta8a17bXaMRtDAL7fQjpF9uH+yEocbdmi2n EBH6R8gyLmRoQapJzCuqQhAj5pZ6vjdmPpVS3s36WPvIqLA3z+KBLPIT43eqcRj9 otg2s0UeGk4hRV3kljtMhcOHfAWfjbP18sm+uUutroL1YUrhU3lMPwabACGysxYQ 3OBm/3jnQdhwlpQ+uxSNTxfIn/O0WTJVrigzqBsn3SsHSJFtw1G1ZuqZUYtKvLoO vrwaQtlskxzbLdYrA/gQt0PYCFIKApaMmWUQXeYRi+XBvQNfPhKIt6vpQIeYddYI XFPDKteISMP0Nx2Cb0gNDe+3l3hwr/mw0qeckgHFqvqdW47VFixTGp9wdlhHwKca nSi8cWBMOjmvDB87Qy086QNXqOrvHzY/TIf14c0NdnuRF04tPix/obJAgQOFqtuR wXD8Ojfs4TsPzarettH4AkSdpgBVhEsujdJzjj7SFPF/GgfwoAg= =8HP6 -----END PGP SIGNATURE----- --=-=-=--